Yesterday I was tinkering with my new install of mojoPortal.  I added a blog to the home page, after adding a couple other modules, making a few other changes, and having gotten the jquery-ui skin how I liked it thanks to some help in the skin forum.  I have no idea what I did wrong, but suddenly I kept getting the generic asp.net error page.  I went into web.config and switched customerrors off, and got in.  But with customerrors off, the site works fine.  It gives me no indication of what the error is.  Switching it back to RemoteOnly, instead of the generic asp.net error page, I now get GoDaddy's generic error page.

I'm no web developer, so when it comes to web development, I may as well be lost in a wet paper bag, but I figured at least turning customerrors off it would give me an error that I could look up, but no, the site works fine.  Should I leave it this way, or is there a problem with that?  But that doesn't solve the underlying problem.

But then after that, another problem cropped up.  The sign out link stopped working.  Just quit.  Click it and it brings me back to the home page still logged in.  =/

New web site, still in the tinkering mode, still has the site closed message up, so I deleted the database, created new, and reinstalled the mojoPortal.  You'd think that might help.  Nope.  The link problem is solved now, but if I set customerrors to RemoteOnly, I still get the GoDaddy generic error page.  Not the error page that it is told to redirect to, but GoDaddy's error page.

Should I worry about it?

Thanks, Joe. 

When the problem started, I hadn't touched the web.config in more than a day.  So since I couldn't log into the site, I commented out the customerrors as follows:

<!--
      <customErrors mode="RemoteOnly"> <defaultRedirect="Error.htm">
       <error statusCode="413" redirect="~/NeatUpload/Error413.aspx" />
      </customErrors>
-->  
      <customErrors mode="Off"/>

That allowed me to log into the site.

Now I've followed your suggestion with the log.  First I cleared it, then commented out my customErrors off and uncommented the RemoteOnly, which caused the error, and then replaced the comments as above.  Here is the log that I got when I went back in:

2012-11-15 07:15:15,830 INFO
2012-11-15 08:17:03,897 ERROR
2012-11-15 08:17:03,944 INFO
2012-11-15 08:24:11,772 INFO
2012-11-15 07:12:49,301 INFO
2012-11-15 08:23:08,597 INFO
2012-11-15 08:23:13,168 INFO
2012-11-15 08:23:13,761 INFO
2012-11-15 08:23:13,823 INFO
2012-11-15 08:23:13,885 INFO
2012-11-15 08:23:13,979 INFO
2012-11-15 08:23:14,073 INFO
2012-11-15 08:23:14,166 INFO
2012-11-15 08:23:14,229 INFO
2012-11-15 08:23:14,338 INFO
2012-11-15 08:24:13,277 INFO

I have no idea what the 897 means, nor why the wo times are out of sequence.  The times out of sequence are really puzzling to me...  Since the server is in AZ (if I understand right), the correct time should be the 0800 sequences.  I'm in EST and did this during the 1000 hour.  BTW, after I cleared the log, I did refresh to be sure that it was actually cleared before running this test, so those two timestamps that show more than an hour before did actually happen in that 8:15-8:25 range.