Logs and troubleshooting

In the examples, svm123 is your username and SERVER_IP is your server address — both are on the Access tab of your SVM in the console.

All your logs are in ~/logs and are rotated automatically:

tail -f ~/logs/nginx-error.log ~/logs/php-error.log
systemctl --user status              # everything you run
journalctl --user -u myapp -f        # one service's output

• “Website is not responding” means your nginx is stopped or its config is broken: run svm-nginx-test, then systemctl --user restart svm-nginx.
• Out of memory or disk? The Usage tab shows memory, disk, files and processes against your plan. Upgrade from the Change plan tab.
• The PHP & Node.js tab has one-click restarts for nginx, PHP or everything.