Self-Hosted Main

The docs are pretty straightforward

https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/

​

Here's a barebones of what my nginx.conf looks like to do a reverse proxy

worker_processes 1;

error_log nginx_error.log;

events { worker_connections 1024; }

http { server { server_name mydomain.com www.mydomain.com; location / { proxy_pass http://localhost:9000; } listen 80; }

​

but if you're running nginx inside a docker container you also need to expose the port in the container with -p flag. So your run command is something like docker run ... -p 80:80

Forward Hostname: 10.11.0.1
Forward Port: 7676

Since you mention that both NPM and nginx are in the same Docker network, you need to point NPM to the internal port of nginx. Not the mapped port which is only for the Docker host machine. I would assume your default internal nginx port is 80 and you map that for manual access to 7676. But NPM needs to be pointed at the 80.

In addition you should only use the containernames as hostnames with Docker networking. The 10.11.0.1 is probably your Docker host IP, not the IP of the nginx container itself. And those are dynamic by default.

So change your NPM settings to:

Forward Hostname: nginx
Forward Port: 80

Very basic reverse proxy and Docker network stuff. Btw, /r/Docker and /r/NginxProxyManager both exist.

Also, I tried getting an SSL certificate but was met with an error, and now it looks like I've hit the hourly limit on that...

Cant say anything about the SSL cert error without any details at all. But hitting the hourly Lets Encrypt limit is easily avoidable by simply using the staging CA instead of the live CA, which is the recommended way for doing fresh setups and youre unsure of how it works. Using the LE staging CA you can mess with settings and try stuff out, without getting limited. Once you have everything working, you switch it over to the live CA and then you get a valid cert.