Hey folks! I'm a newbie to Docker and I'm diving deeper into homelabbing. I've been able to set up Pi-hole on a Raspberry Pi, and now I'm trying to get a Docker container running on my Ubuntu VM hosted with Proxmox. My plan is to run Nginx Proxy Manager, along with Portainer, Pi-hole, and Lancache, acting as the DNS server for my home network.
I've set up my Docker desktop environment and composed a .yaml file with the necessary service configurations for Nginx Proxy Manager. However, when I attempt to run the container, it fails immediately with the error indicating a permission issue for port 443. It seems that something called `docker-proxy` is already using this port. I'm at a loss about how to move past this problem, as most guides I've seen don't run into issues like mine. Any insights would be greatly appreciated!
3 Answers
Definitely sounds like a port conflict to me. The solution could be straightforward: just change the port mapping in your Docker configuration so it doesn't conflict with what’s running on the Ubuntu host. Make sure to test if the Nginx Proxy Manager works on another port before finalizing anything.
It looks like your Ubuntu VM is running a web server that’s already using port 443. This is causing a conflict since your Docker container also wants to use that port. You have a few options: either stop the existing web server or change the port mapping in your Docker compose file so it doesn’t try to use 443. You could also move your Docker setup to a different port entirely.
Totally agree with you! Make sure that you run your Docker commands as root to avoid permissions issues with the ports. Also, if you've ever run your container in daemon mode, make sure to stop that instance first to free up the ports.
It seems your host is already running a web server on port 443, which would block the container from binding to that port. You need to either move your host server to a different port or disable it to let the container use port 443. Check the running services on your VM to see what's occupying that port.
You might want to check which services are running on your VM. If there's a web server that's not necessary for your setup, shutting it down could free up port 443 for your container. Just remember, only a reverse proxy should occupy ports 80 and 443 to avoid conflicts.