Troubleshooting nopCommerce
nopCommerce runs as a .NET service behind nginx. Most problems fall into one of three categories: the application service is not running, Nginx cannot reach it (502), or it cannot connect to SQL Server. This page shows where the logs are and how to work through the common failures.
Where to find the logs
nopCommerce is a managed systemd user service, so its console output goes to the journal rather than a flat file. Combine the journal with Nginx logs and the application's own logging.
Also check the host's Health tab for CPU/memory/disk and service state, and recent deploys in History.
Tip
Add -f to the journal command (journalctl --user -u application.service -f) to watch logs live while you reproduce a problem or restart the service.
Common issues
A troubleshooting workflow
- Check Health - confirm the host is up and the application service is running, and look for CPU/memory/disk pressure.
- Read the relevant log - start with
journalctl --user -u application.servicefor a 502 or a crash. Check the Nginx error log if the journal shows the app is healthy. Check Admin > System > Log for application-level errors. - Check the last deploy in History - if a recent change broke the store, revert and re-publish from Publishing.
- Verify services are running - confirm the nopCommerce service is active (
systemctl --user status application.service), Nginx is up, and SQL Server is reachable. Restart any service that is down.
Getting help
If you are still stuck, see the general platform troubleshooting guide or contact Support with the relevant journal and Nginx log excerpts.