Troubleshooting Guide

THE ERROR PAGE IS SHOWN WHAT SHOULD I DO? - VERSION 4.0 and above

When the error page is shown this means that there is some error and you need to know what the error is before fixing it. You have two options:

1. Open the administration by navigating to YourStoreName.com/admin and then go to System -> Log.
   The Log contains all the errors and warnings in your store. Most of the time you should be looking for the most recent error. The error details contain all the information you need to investigate and fix the problem.
2. If you can't access the administration you have to turn on your site log, so that your errors are logged in a .txt file. To do so, modify your Web.config file by setting stdoutLogEnabled to true:

  <aspNetCore requestTimeout="00:07:00" processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" forwardWindowsAuthToken="false"
stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />

change to:

  <aspNetCore requestTimeout="00:07:00" processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" forwardWindowsAuthToken="false"
stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />

Once you got the error you will get a log .txt file generated in ~/Logs folder (~/Presentation/Nop.Web/Logs for Source version of nopCommerce). If you, however, cannot understand what is wrong you can Send us a Ticket or Open a Thread in our Forums with the attached log file.

The Error page is shown what should I do? - version 3.9 or below

When the error page is shown this means that there is some error and you need to know what the error is before fixing it. You have two options:

1. Open the administration by navigating to YourStoreName.com/admin and then go to System -> Log.
   The Log contains all the errors and warnings in your store. Most of the time you should be looking for the most recent error. The error details contain all the information you need to investigate and fix the problem.
2. If you can't access the administration you have to turn off the custom errors, so that you are not navigated to the Error Page. To do so, modify your Web.config file by replacing RemoteOnly with Off:

<customErrors defaultRedirect="errorpage.htm" mode="RemoteOnly">

change to:

<customErrors defaultRedirect="errorpage.htm" mode="Off">

Once you got the error it is much easier to know what is wrong and to fix it. If you, however, cannot understand what is wrong you can Send us a Ticket or Open a Thread in our Forums.