You can troubleshoot your ASP.NET Core application by enabling stdout logging in the NopCommerce web.config. Simply locate the following line and set stdoutLogEnabled=true.<aspNetCore requestTimeout="00:07:00" processPath=".\Nop.Web.exe" arguments="" forwardWindowsAuthToken="false" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
When you are done, the line should look like:
<aspNetCore requestTimeout="00:07:00" processPath=".\Nop.Web.exe" arguments="" forwardWindowsAuthToken="false" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />
Reload your website and give the application enough time to restart. Wait until the page is fully loaded and stops spinning. When that's done, navigate to your file structure in your control panel or FTP and look inside the Logs folder in the 'httpdocs' directory. Open the log file and look for lines that mention fail: This will give you an indication of why the application is failing to start properly and you can work on resolving.
IMPORTANT: Do not forget to disable stdout logging when you are done troubleshooting as the application will run very slowly as additional debugging routines are used. Also, clean up any old stdout log files so you keep a clean workspace for the next time you use this feature.
Looking for reliable Windows hosting with Award Winning Customer Support?
Grab your hosting today with a 20% discount. All plans come with our 60 Money Back Guarantee!
Check out our plans & promotions on our website -- https://www.peopleshost.com/
