Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 884
  • Last Modified:

ASP.NET CustomErrors = RemoteOnly not working

ASP.NET V2
IIS6

Turned custom errors to RemoteOnly, when im on the local box, it shows me the generic YSOD.

Even when i turn customerrors='off' it still gives me generic YSOD. How can i see my errors!?
0
HADDADD3
Asked:
HADDADD3
  • 4
  • 2
1 Solution
 
joshbulaCommented:
<system.web>
  <customErrors mode="On" defaultRedirect="~/ErrorPage.aspx" />
</system.web>
0
 
joshbulaCommented:
Oh... sorry... misunderstood the question.  oops.
0
 
joshbulaCommented:
In the <compilation...> tag, do you have debug="true" ?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
HADDADD3Author Commented:
Yes Debug is true.

I;m trying to get "remoteOnly" to work.

I think the issue is that server is behind a firewall....

So when i go to(on the local box)
www.mysite.com
it is first connecting to firewall, then passing through the firewall, to the local address 192.168.1.2, and "thinks" that it is a remote connection....

Is that right? Is there a work-around?
0
 
joshbulaCommented:
Ok, that makes sense.  Instead of going to www.mysite.com, go to http://localhost/
0
 
HADDADD3Author Commented:
I cant because i use host headers, any work around?

Editing the hosts file maybe?
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now