Nginx Proxy Manager Settings

version: ‘3’
services:
app:
image: ‘2691432189/nginx-proxy-manager-monitor-zh’
restart: always
ports:
- ‘1180:80’
- ‘1181:81’
- ‘1443:443’
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
The above are the ports for Nginx Proxy Manager;


This is the proxy configuration; the target server is a website that is accessible. demo.zimbar.us.kg
Is this correct or incorrect? I currently cannot access demo.zimbar.us.kg using my domain name.

ports:
- ‘1180:80’
- ‘1181:81’
- ‘1443:443’

This means that ports 1180, 1181, and 1443 on the host are mapped to corresponding ports inside the container. Therefore, when configuring inside the container, you should use 80, 81, and 443 for your configuration, and then access the service via ports 1180, 1181, and 1443 on the host.


Is this correct? However, the domain www.laosix.com still cannot be accessed.

Isn’t this working now? You need to add the port.

404 Not Found (laosix.com)

400 The plain HTTP request was sent to HTTPS port (laosix.com)

But my target address is not local, but another site: demo.zimbar.us.kg
This is the correct one.

I’ll have to look into how to use this nginx-proxy-manager-monitor. I’ve never used it before, so I’m not sure.

The network is now working correctly.

I want to use laosix.com to proxy traffic to access demo.zimbar.us.kg;
That is, laosix.com resolves to Server A, while the demo.zimbar.us.kg site resolves to Server B.
When you access laosix.com, the request is first relayed through Server A to reach the target address — demo.zimbar.us.kg.

This is because the IP address of the web server for demo.zimbar.us.kg is blocked by the Great Firewall.

If you want to access directly via a domain name, you should set the container to directly map port 80 to 80 and 443 to 443, and avoid using ports like 1180 and 1443.

If you directly map port 80 to 80 and port 443 to 443 for your container, this will affect nginx, right? Doesn’t nginx on the server already occupy these two ports?

There is already Nginx on the server, so why not directly use Nginx as a reverse proxy instead of running this nginx-proxy-manager-monitor?

I’m looking into how to get this working :smiling_face_with_horns: to see if there’s a way to run multiple sites using CF optimized domains. Currently, CF optimized domains only support a single origin address.

Then just have Nginx reverse proxy nginx-proxy-manager-monitor again, it’s a nesting doll (Matryoshka) setup.