How to track down logs / sources of problems?

I’m getting some “502 Bad Gateway (openresty)” error that I’m not able to yet track down.

I assume that I should be using docker logs --follow nginx-proxy-manager or docker exec -it nginx-proxy-manager bash and track them in /var/log… but I’m not seeing any error via these methods when I hit the 502 error.

Where do I look to find such errors? I don’t think the error would be coming from elsewhere due to the openresty message and nothing else behind it is using this, but I’d sure like to understand how to see everything flowing through with as high of a degree of transparency as possible in order to understand what errors are happening from whatever cause, etc.

Could you please clarify this to me in terms of troubleshooting and what you’d do to track such details down @jc21?

[jc21]

For 502 errors they should show in the Nginx error log, inside the container this is /data/logs/error.log but since you should also be mounting this data folder from outside of the container you can access it without having to enter the container.

[chaptergy]

I don’t think you should use 127.0.0.1 or localhost as the forward ip / hostname as this will forward the request inside the NPM docker container, where it does not find anything. You will need to use the IP in your local network. So localhost or 127.0.0.1 is NOT your host machine in NPM, it is the NPM docker container itself.

But this is a little off topic for this issue, as it is about how to debug errors.