nginx-proxy-manager: bind() to 0.0.0.0:80 failed (98: Address in use)

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you’re not using someone else’s docker image?

Yes

If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?

I think its not a Lets Encrypt Issue

Describe the bug

A clear and concise description of what the bug is.

While starting the docker-compose file the nginx proxy manager is not able to bind the address. No other container uses the allocated ports. I also tried to change the port, but the isse is the same. When I start it, it puts out endless error log contianing this:

nginx: [warn] low address bits of 192.168.1.1/24 are meaningless in /data/nginx/proxy_host/23.conf:62
nginx: [warn] low address bits of 192.168.5.1/24 are meaningless in /data/nginx/proxy_host/23.conf:63
nginx: [warn] low address bits of 192.168.1.1/24 are meaningless in /data/nginx/proxy_host/7.conf:65
nginx: [warn] low address bits of 192.168.5.1/24 are meaningless in /data/nginx/proxy_host/7.conf:66
nginx: [warn] low address bits of 192.168.1.1/24 are meaningless in /data/nginx/proxy_host/8.conf:63
nginx: [warn] low address bits of 192.168.5.1/24 are meaningless in /data/nginx/proxy_host/8.conf:64
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address in use)
nginx: [emerg] still could not bind
finish: applet not found

What version of Nginx Proxy Manager is reported on the login page?

not able to see the login page.

Operating System

Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error.

Ubuntu Server 20.04 LTS with docker snap installed

Can you help me in any way?

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 23

Most upvoted comments

I think I made a stream host entry to forward port 80 to a different one. Could that be the issue? How can I revert this? Maybe this is the issue?

It was the issue. I renamed the config for the stream host to a .bakcup file and after startup it worked.

This problem still without a solution, did anyone figure out how to solve?