Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How to access nginx logs
See original GitHub issueI’ve been getting 500 Internal Server Error
Nothing shows up in the mup logs. How do I access the nginx logs?
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
NGINX Access Logs and Error Logs - DigitalOcean
The NGINX logs the activities of all the visitors to your site in the access logs. Here you can find which files are...
Read more >Configuring Logging | NGINX Plus
NGINX writes information about client requests in the access log right after the request is processed. By default, the access log is located...
Read more >How to View and Configure NGINX Access & Error Logs
The NGINX access Log should be enabled by default. However, if this is not the case, you can enable it manually in the...
Read more >How do I view Nginx logs? - Linux Hint
All activities related to site visitors are recorded in the access logs. In this type of log, you can find those files which...
Read more >Where can I find the error logs of nginx, using FastCGI and ...
Nginx is usually set up in /usr/local or /etc/ . The server could be configured to dump logs to /var/log as well. If...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For anyone trying this: I created a new
.deploydirectory and a new instance with exactly the same config. Now it works, and the nginx-config doesn’t have those weirdreturn 500;entries… Seems like a bug in MUP to me.nginx container for let’s encrypt:
docker logs <appname>-nginx-proxynginx container for custom ssl certificates:
docker logs <appname>-frontendRun the command on the server.