![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Runtime Error. An application error occurred on the server.
I KEEP GETTING THESE ERRORS. DON'T KNOW HOW TO FIX, ANY SUGGESTIONS? THANKS.
Server Error in '/' Application. Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<configuration>
<system.web> <customErrors mode="Off"/> </system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<configuration>
<system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web>
</configuration>
ALSO GETTING THESE ERRORS:
Server Error in '/' Application. The wait operation timed out Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ComponentModel.Win32Exception: The wait operation timed out
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web> <compilation debug="true"/> </system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Všetky odpovede (2)
Hi
That is a problem with the server on that specific website and that needs to be fixed on their side, so you would have to try again some times later (the server may have to be rebooted). There is usually nothing that you can do about it apart from basic first steps to try (clear cookies and cache) in case that there is a problem on your side.
Clear the cache and remove the cookies from websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).
"Clear the cache":
- Firefox/Options/Preferences -> Advanced -> Network -> Cached Web Content: "Clear Now"
"Remove the cookies" from websites that cause problems.
- Firefox/Options/Preferences -> Privacy -> "Use custom settings for history" -> Cookies: "Show Cookies"
Thanks for quick reply. Still have same problem and today I tried to open another email and got this:
Oops! Something went wrong! The Browser version is not currently supported. Please use the latest version of Internet Explorer, Google Chrome or Microsoft Edge.
But I'm using Firefox 53.0.3 (32-bit). Since when isn't Firefox a current browser to use?