starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #834] bind() to 0.0.0.0:80 failed (98: Address in use) #706

New issue
Closed
opened 2026-02-26 06:34:03 +03:00 by kerem · 28 comments
kerem commented 2026-02-26 06:34:03 +03:00
Owner
Copy link

Originally created by @clemone210 on GitHub (Jan 21, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/834

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?

Originally created by @clemone210 on GitHub (Jan 21, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/834 ### **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?**
kerem 2026-02-26 06:34:03 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 06:34:04 +03:00
Author
Owner
Copy link

@clemone210 commented on GitHub (Jan 21, 2021):

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?

<!-- gh-comment-id:764552436 --> @clemone210 commented on GitHub (Jan 21, 2021): 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?
kerem commented 2026-02-26 06:34:04 +03:00
Author
Owner
Copy link

@clemone210 commented on GitHub (Jan 21, 2021):

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.

<!-- gh-comment-id:764659230 --> @clemone210 commented on GitHub (Jan 21, 2021): > 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.
kerem commented 2026-02-26 06:34:04 +03:00
Author
Owner
Copy link

@techc0de commented on GitHub (Feb 10, 2021):

Hi,
I having the same issue whenever restart the NPM container or recreate it in Portainer.
Any idea why ?

Docker Logs 
  ❯ /etc/nginx/conf.d/include/force-ssl.conf,
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf,
  ❯ /etc/nginx/conf.d/include/assets.conf,
  ❯ /etc/nginx/conf.d/include/resolvers.conf,
  ❯ /etc/nginx/conf.d/default.conf,
❯ Enabling IPV6 in hosts: /data/nginx,
  ❯ /data/nginx/proxy_host/2.conf,
  ❯ /data/nginx/proxy_host/3.conf,
  ❯ /data/nginx/proxy_host/1.conf,
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] bind() to 0.0.0.0:443 failed (98: Address in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address in use),
[2/10/2021] [10:59:08 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6,
[2/10/2021] [10:59:08 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized,
[2/10/2021] [10:59:08 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/10/2021] [10:59:08 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized,
Uncaught Error: listen EADDRINUSE: address already in use :::3000,
,
FROM,
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] bind() to 0.0.0.0:443 failed (98: Address in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address in use),
./run: line 18:  4031 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js,
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] bind() to 0.0.0.0:443 failed (98: Address in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address in use),
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] bind() to 0.0.0.0:443 failed (98: Address in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address in use),
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] bind() to 0.0.0.0:443 failed (98: Address in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address in use),
nginx: [emerg] still could not bind(),
finish: applet not found,
❯ Enabling IPV6 in hosts: /etc/nginx/conf.d,
  ❯ /etc/nginx/conf.d/production.conf,
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf,
  ❯ /etc/nginx/conf.d/include/proxy.conf,
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf,
  ❯ /etc/nginx/conf.d/include/block-exploits.conf,
  ❯ /etc/nginx/conf.d/include/force-ssl.conf,
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf,
  ❯ /etc/nginx/conf.d/include/assets.conf,
  ❯ /etc/nginx/conf.d/include/resolvers.conf,
  ❯ /etc/nginx/conf.d/default.conf,
❯ Enabling IPV6 in hosts: /data/nginx,
  ❯ /data/nginx/proxy_host/2.conf,
  ❯ /data/nginx/proxy_host/3.conf,
  ❯ /data/nginx/proxy_host/1.conf,
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] bind() to 0.0.0.0:443 failed (98: Address in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address in use),
[2/10/2021] [10:59:11 PM] [Migrate  ] › ℹ  info      Current database version: 20201014143841,
[2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...,
[2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json,
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] bind() to 0.0.0.0:443 failed (98: Address in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address in use),
[2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4,
[2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6,
[2/10/2021] [10:59:11 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized,
[2/10/2021] [10:59:11 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized,
Uncaught Error: listen EADDRINUSE: address already in use :::3000,
,
FROM,
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] bind() to 0.0.0.0:443 failed (98: Address in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address in use),
./run: line 18:  4087 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js,

npm db:

2021-02-10 22:59:47 134 [Warning] Aborted connection 134 to db: 'npm' user: 'npm' host: '172.18.0.2' (Got an error reading communication packets)
<!-- gh-comment-id:777092378 --> @techc0de commented on GitHub (Feb 10, 2021): Hi, I having the same issue whenever restart the NPM container or recreate it in Portainer. Any idea why ? <details><summary>Docker Logs</summary> ``` ❯ /etc/nginx/conf.d/include/force-ssl.conf, ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf, ❯ /etc/nginx/conf.d/include/assets.conf, ❯ /etc/nginx/conf.d/include/resolvers.conf, ❯ /etc/nginx/conf.d/default.conf, ❯ Enabling IPV6 in hosts: /data/nginx, ❯ /data/nginx/proxy_host/2.conf, ❯ /data/nginx/proxy_host/3.conf, ❯ /data/nginx/proxy_host/1.conf, 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] bind() to 0.0.0.0:443 failed (98: Address in use), nginx: [emerg] bind() to [::]:443 failed (98: Address in use), nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use), nginx: [emerg] bind() to [::]:81 failed (98: Address in use), [2/10/2021] [10:59:08 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6, [2/10/2021] [10:59:08 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized, [2/10/2021] [10:59:08 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry..., [2/10/2021] [10:59:08 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized, Uncaught Error: listen EADDRINUSE: address already in use :::3000, , FROM, 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] bind() to 0.0.0.0:443 failed (98: Address in use), nginx: [emerg] bind() to [::]:443 failed (98: Address in use), nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use), nginx: [emerg] bind() to [::]:81 failed (98: Address in use), ./run: line 18: 4031 Illegal instruction (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js, 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] bind() to 0.0.0.0:443 failed (98: Address in use), nginx: [emerg] bind() to [::]:443 failed (98: Address in use), nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use), nginx: [emerg] bind() to [::]:81 failed (98: Address in use), 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] bind() to 0.0.0.0:443 failed (98: Address in use), nginx: [emerg] bind() to [::]:443 failed (98: Address in use), nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use), nginx: [emerg] bind() to [::]:81 failed (98: Address in use), 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] bind() to 0.0.0.0:443 failed (98: Address in use), nginx: [emerg] bind() to [::]:443 failed (98: Address in use), nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use), nginx: [emerg] bind() to [::]:81 failed (98: Address in use), nginx: [emerg] still could not bind(), finish: applet not found, ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d, ❯ /etc/nginx/conf.d/production.conf, ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf, ❯ /etc/nginx/conf.d/include/proxy.conf, ❯ /etc/nginx/conf.d/include/ip_ranges.conf, ❯ /etc/nginx/conf.d/include/block-exploits.conf, ❯ /etc/nginx/conf.d/include/force-ssl.conf, ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf, ❯ /etc/nginx/conf.d/include/assets.conf, ❯ /etc/nginx/conf.d/include/resolvers.conf, ❯ /etc/nginx/conf.d/default.conf, ❯ Enabling IPV6 in hosts: /data/nginx, ❯ /data/nginx/proxy_host/2.conf, ❯ /data/nginx/proxy_host/3.conf, ❯ /data/nginx/proxy_host/1.conf, 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] bind() to 0.0.0.0:443 failed (98: Address in use), nginx: [emerg] bind() to [::]:443 failed (98: Address in use), nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use), nginx: [emerg] bind() to [::]:81 failed (98: Address in use), [2/10/2021] [10:59:11 PM] [Migrate ] › ℹ info Current database version: 20201014143841, [2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services..., [2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json, 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] bind() to 0.0.0.0:443 failed (98: Address in use), nginx: [emerg] bind() to [::]:443 failed (98: Address in use), nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use), nginx: [emerg] bind() to [::]:81 failed (98: Address in use), [2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4, [2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6, [2/10/2021] [10:59:11 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized, [2/10/2021] [10:59:11 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry..., [2/10/2021] [10:59:11 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized, Uncaught Error: listen EADDRINUSE: address already in use :::3000, , FROM, 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] bind() to 0.0.0.0:443 failed (98: Address in use), nginx: [emerg] bind() to [::]:443 failed (98: Address in use), nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address in use), nginx: [emerg] bind() to [::]:81 failed (98: Address in use), ./run: line 18: 4087 Illegal instruction (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js, ``` </details> npm db: ``` 2021-02-10 22:59:47 134 [Warning] Aborted connection 134 to db: 'npm' user: 'npm' host: '172.18.0.2' (Got an error reading communication packets) ```
kerem commented 2026-02-26 06:34:04 +03:00
Author
Owner
Copy link

@virse commented on GitHub (Feb 16, 2021):

Hi,
I having the same issue whenever restart the NPM container or recreate it in Portainer.
Any idea why ?

Same here on my site.

After upgrade to 2.8.0 without any changes in the config I receive the same "Addres in use" messages. Recreate the container or a restart did not solved the problem.

Any help is appreciated.

mike

<!-- gh-comment-id:779698306 --> @virse commented on GitHub (Feb 16, 2021): > Hi, > I having the same issue whenever restart the NPM container or recreate it in Portainer. > Any idea why ? Same here on my site. After upgrade to 2.8.0 without any changes in the config I receive the same "Addres in use" messages. Recreate the container or a restart did not solved the problem. Any help is appreciated. mike
kerem commented 2026-02-26 06:34:04 +03:00
Author
Owner
Copy link

@niklasschroetler commented on GitHub (Feb 19, 2021):

Unfortunately, same here...

<!-- gh-comment-id:782453885 --> @niklasschroetler commented on GitHub (Feb 19, 2021): Unfortunately, same here...
kerem commented 2026-02-26 06:34:04 +03:00
Author
Owner
Copy link

@MohamedElashri commented on GitHub (Apr 9, 2021):

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

<!-- gh-comment-id:816462531 --> @MohamedElashri commented on GitHub (Apr 9, 2021): This problem still without a solution, did anyone figure out how to solve?
kerem commented 2026-02-26 06:34:04 +03:00
Author
Owner
Copy link

@lachlan334 commented on GitHub (Jun 23, 2021):

I am also having this exact issue.

<!-- gh-comment-id:866778510 --> @lachlan334 commented on GitHub (Jun 23, 2021): I am also having this exact issue.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@Sperryfreak01 commented on GitHub (Dec 27, 2021):

I was previously using the :2 tag, and when I updated to :latest I started having this issue. Rolled back to the :2 tag and it started working great again.

<!-- gh-comment-id:1001739142 --> @Sperryfreak01 commented on GitHub (Dec 27, 2021): I was previously using the :2 tag, and when I updated to :latest I started having this issue. Rolled back to the :2 tag and it started working great again.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Dec 29, 2021):

Theoretically :2 and :latest should currently point to the same version.

So for all of you you haven't created stream hosts for any of the standard ports 80, 443 or 81? Then please check which process is claiming these ports by running

apt update && apt install net-tools -y
netstat -tulpn

(Only the output of the second line is relevant)

<!-- gh-comment-id:1002667179 --> @chaptergy commented on GitHub (Dec 29, 2021): Theoretically `:2` and `:latest` should currently point to the same version. So for all of you you haven't created stream hosts for any of the standard ports `80`, `443` or `81`? Then please check which process is claiming these ports by running ```commandline apt update && apt install net-tools -y netstat -tulpn ``` (Only the output of the second line is relevant)
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@fabifri commented on GitHub (Dec 31, 2021):

Unfortunately i am having the same issue; prior to starting the npm-container, i checked on used ports (bindings) with netstat -tulpn and i got nothing. Nothing was claiming 80, 443 or 81. After starting the npm-container, everything seems to work, webinterface as well as the proxy hosts. However my logfile is being constantly spammed full with error messages:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use),
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use),
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use),
nginx: [emerg] bind() to [::]:443 failed (98: Address already in use),
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use),
nginx: [emerg] bind() to [::]:81 failed (98: Address already in use),
nginx: [emerg] still could not bind(),

and besides from that, there is also a mysterious port 3000 involved now:

[12/31/2021] [1:08:43 AM] [SSL ] › ℹ️ info Let's Encrypt Renewal Timer initialized,
[12/31/2021] [1:08:43 AM] [SSL ] › ℹ️ info Renewing SSL certs close to expiry...,
Uncaught Error: listen EADDRINUSE: address already in use :::3000,
,
FROM,
./run: line 19: 1123 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js,

only issue this is creating at the moment is, that for currently it is not possible to renew any letsencrypt certificates.
when the time for my certificates runs out, in the end, i probably need to completely reinstall npm and create my proxy hosts from scratch.

<!-- gh-comment-id:1003231787 --> @fabifri commented on GitHub (Dec 31, 2021): Unfortunately i am having the same issue; prior to starting the npm-container, i checked on used ports (bindings) with `netstat -tulpn `and i got nothing. Nothing was claiming 80, 443 or 81. After starting the npm-container, everything seems to work, webinterface as well as the proxy hosts. However my logfile is being constantly spammed full with error messages: > nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use), > nginx: [emerg] bind() to [::]:80 failed (98: Address already in use), > nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use), > nginx: [emerg] bind() to [::]:443 failed (98: Address already in use), > nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use), > nginx: [emerg] bind() to [::]:81 failed (98: Address already in use), > nginx: [emerg] still could not bind(), and besides from that, there is also a mysterious port 3000 involved now: > [12/31/2021] [1:08:43 AM] [SSL ] › ℹ️ info Let's Encrypt Renewal Timer initialized, > [12/31/2021] [1:08:43 AM] [SSL ] › ℹ️ info Renewing SSL certs close to expiry..., > Uncaught Error: listen EADDRINUSE: address already in use :::3000, > , > FROM, > ./run: line 19: 1123 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js, only issue this is creating at the moment is, that for currently it is not possible to renew any letsencrypt certificates. when the time for my certificates runs out, in the end, i probably need to completely reinstall npm and create my proxy hosts from scratch.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@Sperryfreak01 commented on GitHub (Dec 31, 2021):

I have no stream clients set up. Before switching from the latest to the 2 label I ran netstat looking for what running on the ports... nothing was holding the ports.

<!-- gh-comment-id:1003245709 --> @Sperryfreak01 commented on GitHub (Dec 31, 2021): I have no stream clients set up. Before switching from the latest to the 2 label I ran netstat looking for what running on the ports... nothing was holding the ports.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@Go2Engle commented on GitHub (Jan 6, 2022):

Im also getting the same thing with those ports not in use. =[

<!-- gh-comment-id:1006909457 --> @Go2Engle commented on GitHub (Jan 6, 2022): Im also getting the same thing with those ports not in use. =[
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@iambdud commented on GitHub (Feb 5, 2022):

I am also getting this same error. Strange thing is that NPM still seems to be working fine?

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:81 failed (98: Address already in use)
nginx: [emerg] still could not bind()

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:45067         0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1352/nginx: worker  
tcp        0      0 0.0.0.0:81              0.0.0.0:*               LISTEN      1352/nginx: worker  
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      1352/nginx: worker  
tcp        0      0 0.0.0.0:9001            0.0.0.0:*               LISTEN      -                   
tcp6       0      0 :::80                   :::*                    LISTEN      1352/nginx: worker  
tcp6       0      0 :::81                   :::*                    LISTEN      1352/nginx: worker  
tcp6       0      0 :::22                   :::*                    LISTEN      -                   
tcp6       0      0 :::3000                 :::*                    LISTEN      239/node            
tcp6       0      0 ::1:25                  :::*                    LISTEN      -                   
tcp6       0      0 :::443                  :::*                    LISTEN      1352/nginx: worker  
tcp6       0      0 :::9001                 :::*                    LISTEN      - ```
<!-- gh-comment-id:1030669589 --> @iambdud commented on GitHub (Feb 5, 2022): I am also getting this same error. Strange thing is that NPM still seems to be working fine? ``` nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) nginx: [emerg] bind() to [::]:81 failed (98: Address already in use) nginx: [emerg] still could not bind() ``` ```[root@docker-proxy:/app]# netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:45067 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1352/nginx: worker tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 1352/nginx: worker tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1352/nginx: worker tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN - tcp6 0 0 :::80 :::* LISTEN 1352/nginx: worker tcp6 0 0 :::81 :::* LISTEN 1352/nginx: worker tcp6 0 0 :::22 :::* LISTEN - tcp6 0 0 :::3000 :::* LISTEN 239/node tcp6 0 0 ::1:25 :::* LISTEN - tcp6 0 0 :::443 :::* LISTEN 1352/nginx: worker tcp6 0 0 :::9001 :::* LISTEN - ```
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@Go2Engle commented on GitHub (Feb 5, 2022):

I ended up just wiping out my NPM and starting fresh and haven't had any issues since.

<!-- gh-comment-id:1030669880 --> @Go2Engle commented on GitHub (Feb 5, 2022): I ended up just wiping out my NPM and starting fresh and haven't had any issues since.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@iambdud commented on GitHub (Feb 5, 2022):

I ended up just wiping out my NPM and starting fresh and haven't had any issues since.

I did the same, and it was fine for a little while and then started with the errors again. I only have proxy hosts configured.

FWIW, I was using the --net=host option. I changed it and i'm specifying the ports now. No errors so far... we'll see how it goes.

<!-- gh-comment-id:1030670291 --> @iambdud commented on GitHub (Feb 5, 2022): > I ended up just wiping out my NPM and starting fresh and haven't had any issues since. I did the same, and it was fine for a little while and then started with the errors again. I only have proxy hosts configured. FWIW, I was using the --net=host option. I changed it and i'm specifying the ports now. No errors so far... we'll see how it goes.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@Go2Engle commented on GitHub (Feb 5, 2022):

I ended up just wiping out my NPM and starting fresh and haven't had any issues since.

I did the same, and it was fine for a little while and then started with the errors again. I only have proxy hosts configured.

FWIW, I was using the --net=host option. I changed it and i'm specifying the ports now. No errors so far... we'll see how it goes.

Hmmm ok I'll keep an eye out!

<!-- gh-comment-id:1030695512 --> @Go2Engle commented on GitHub (Feb 5, 2022): > > I ended up just wiping out my NPM and starting fresh and haven't had any issues since. > > > > I did the same, and it was fine for a little while and then started with the errors again. I only have proxy hosts configured. > > > > FWIW, I was using the --net=host option. I changed it and i'm specifying the ports now. No errors so far... we'll see how it goes. Hmmm ok I'll keep an eye out!
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@iambdud commented on GitHub (Feb 6, 2022):

I ended up just wiping out my NPM and starting fresh and haven't had any issues since.

I did the same, and it was fine for a little while and then started with the errors again. I only have proxy hosts configured.
FWIW, I was using the --net=host option. I changed it and i'm specifying the ports now. No errors so far... we'll see how it goes.

Hmmm ok I'll keep an eye out!

Same thing happening today even using the -p options. Here is the netstat output on the host without the container running:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:45067         0.0.0.0:*               LISTEN      127/containerd      
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      3623821/systemd-res 
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      482/master          
tcp        0      0 0.0.0.0:9001            0.0.0.0:*               LISTEN      869903/docker-proxy 
tcp6       0      0 :::22                   :::*                    LISTEN      1/init              
tcp6       0      0 ::1:25                  :::*                    LISTEN      482/master          
tcp6       0      0 :::9001                 :::*                    LISTEN      869908/docker-proxy

Here it is after the container is started:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:45067         0.0.0.0:*               LISTEN      127/containerd      
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3625484/docker-prox 
tcp        0      0 0.0.0.0:81              0.0.0.0:*               LISTEN      3625466/docker-prox 
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      3623821/systemd-res 
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      482/master          
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      3625448/docker-prox 
tcp        0      0 0.0.0.0:9001            0.0.0.0:*               LISTEN      869903/docker-proxy 
tcp6       0      0 :::80                   :::*                    LISTEN      3625489/docker-prox 
tcp6       0      0 :::81                   :::*                    LISTEN      3625471/docker-prox 
tcp6       0      0 :::22                   :::*                    LISTEN      1/init              
tcp6       0      0 ::1:25                  :::*                    LISTEN      482/master          
tcp6       0      0 :::443                  :::*                    LISTEN      3625453/docker-prox 
tcp6       0      0 :::9001                 :::*                    LISTEN      869908/docker-proxy

Should I open a new issue?

<!-- gh-comment-id:1030890791 --> @iambdud commented on GitHub (Feb 6, 2022): > > > I ended up just wiping out my NPM and starting fresh and haven't had any issues since. > > > > > > I did the same, and it was fine for a little while and then started with the errors again. I only have proxy hosts configured. > > FWIW, I was using the --net=host option. I changed it and i'm specifying the ports now. No errors so far... we'll see how it goes. > > Hmmm ok I'll keep an eye out! Same thing happening today even using the -p options. Here is the netstat output on the host without the container running: ``` Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:45067 0.0.0.0:* LISTEN 127/containerd tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 3623821/systemd-res tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 482/master tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 869903/docker-proxy tcp6 0 0 :::22 :::* LISTEN 1/init tcp6 0 0 ::1:25 :::* LISTEN 482/master tcp6 0 0 :::9001 :::* LISTEN 869908/docker-proxy ``` Here it is after the container is started: ``` Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:45067 0.0.0.0:* LISTEN 127/containerd tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3625484/docker-prox tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 3625466/docker-prox tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 3623821/systemd-res tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 482/master tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3625448/docker-prox tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 869903/docker-proxy tcp6 0 0 :::80 :::* LISTEN 3625489/docker-prox tcp6 0 0 :::81 :::* LISTEN 3625471/docker-prox tcp6 0 0 :::22 :::* LISTEN 1/init tcp6 0 0 ::1:25 :::* LISTEN 482/master tcp6 0 0 :::443 :::* LISTEN 3625453/docker-prox tcp6 0 0 :::9001 :::* LISTEN 869908/docker-proxy ``` Should I open a new issue?
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@ahmadnassri commented on GitHub (Dec 18, 2022):

I've dealing with this same issue for months ... logs stuck in infinite loop

12/18/2022 12:24:12 PM Disabling IPV6 in hosts
12/18/2022 12:24:12 PM ❯ Disabling IPV6 in hosts: /data/nginx
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/1.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/9.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/2.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/3.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/4.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/5.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/10.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/7.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/6.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/11.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/custom/http.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/custom/root.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/custom/http_top.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_proxy.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_redirect.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream_tcp.conf
12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream_udp.conf
12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)
12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)
12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)
12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)
12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)
12/18/2022 12:24:15 PM nginx: [emerg] still could not bind()

output of netstat -tulpn | grep 80

tcp        0      0 0.0.0.0:8085            0.0.0.0:*               LISTEN      56020/docker-proxy
tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      117982/docker-proxy
tcp        0      0 0.0.0.0:8083            0.0.0.0:*               LISTEN      56153/docker-proxy
tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      8249/nginx: master
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3381/docker-proxy
tcp6       0      0 :::8085                 :::*                    LISTEN      56027/docker-proxy
tcp6       0      0 :::8081                 :::*                    LISTEN      117989/docker-proxy
tcp6       0      0 :::8083                 :::*                    LISTEN      56160/docker-proxy
tcp6       0      0 :::8000                 :::*                    LISTEN      8249/nginx: master
tcp6       0      0 :::80                   :::*                    LISTEN      3389/docker-proxy

output of netstat -tulpn | grep 443

tcp        0      0 0.0.0.0:4430            0.0.0.0:*               LISTEN      8249/nginx: master
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      3308/docker-proxy
tcp6       0      0 :::4430                 :::*                    LISTEN      8249/nginx: master
tcp6       0      0 :::443                  :::*                    LISTEN      3317/docker-proxy

output of netstat -tulpn | grep 81

tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      117982/docker-proxy
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3381/docker-proxy
tcp        0      0 0.0.0.0:81              0.0.0.0:*               LISTEN      3357/docker-proxy
tcp6       0      0 :::8081                 :::*                    LISTEN      117989/docker-proxy
tcp6       0      0 :::81                   :::*                    LISTEN      3365/docker-proxy

it seems to fail at binding ports 80, 81, 443 ...

the only thing that solves it is a restart of the docker container, which works fine, then after some time it repeats again ... I tried wiping it all out and starting all over again from scratch, and the same problem occurs

<!-- gh-comment-id:1356841881 --> @ahmadnassri commented on GitHub (Dec 18, 2022): I've dealing with this same issue for months ... logs stuck in infinite loop ``` 12/18/2022 12:24:12 PM Disabling IPV6 in hosts 12/18/2022 12:24:12 PM ❯ Disabling IPV6 in hosts: /data/nginx 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/1.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/9.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/2.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/3.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/4.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/5.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/10.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/7.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/6.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/11.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/http.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/root.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/http_top.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_proxy.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_redirect.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream_tcp.conf 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream_udp.conf 12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) 12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) 12/18/2022 12:24:15 PM nginx: [emerg] still could not bind() ``` output of `netstat -tulpn | grep 80` ``` tcp 0 0 0.0.0.0:8085 0.0.0.0:* LISTEN 56020/docker-proxy tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 117982/docker-proxy tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 56153/docker-proxy tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 8249/nginx: master tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3381/docker-proxy tcp6 0 0 :::8085 :::* LISTEN 56027/docker-proxy tcp6 0 0 :::8081 :::* LISTEN 117989/docker-proxy tcp6 0 0 :::8083 :::* LISTEN 56160/docker-proxy tcp6 0 0 :::8000 :::* LISTEN 8249/nginx: master tcp6 0 0 :::80 :::* LISTEN 3389/docker-proxy ``` output of `netstat -tulpn | grep 443` ``` tcp 0 0 0.0.0.0:4430 0.0.0.0:* LISTEN 8249/nginx: master tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3308/docker-proxy tcp6 0 0 :::4430 :::* LISTEN 8249/nginx: master tcp6 0 0 :::443 :::* LISTEN 3317/docker-proxy ``` output of `netstat -tulpn | grep 81` ``` tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 117982/docker-proxy tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3381/docker-proxy tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 3357/docker-proxy tcp6 0 0 :::8081 :::* LISTEN 117989/docker-proxy tcp6 0 0 :::81 :::* LISTEN 3365/docker-proxy ``` it seems to fail at binding ports `80`, `81`, `443` ... the only thing that solves it is a restart of the docker container, which works fine, then after some time it repeats again ... I tried wiping it all out and starting all over again from scratch, and the same problem occurs
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@Go2Engle commented on GitHub (Dec 18, 2022):

I've dealing with this same issue for months ... logs stuck in infinite loop


12/18/2022 12:24:12 PM Disabling IPV6 in hosts

12/18/2022 12:24:12 PM ❯ Disabling IPV6 in hosts: /data/nginx

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/1.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/9.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/2.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/3.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/4.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/5.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/10.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/7.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/6.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/11.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/custom/http.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/custom/root.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/custom/http_top.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_proxy.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_redirect.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream_tcp.conf

12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream_udp.conf

12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)

12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)

12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)

12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)

12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use)

12/18/2022 12:24:15 PM nginx: [emerg] still could not bind()

output of netstat -tulpn | grep 80


tcp        0      0 0.0.0.0:8085            0.0.0.0:*               LISTEN      56020/docker-proxy

tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      117982/docker-proxy

tcp        0      0 0.0.0.0:8083            0.0.0.0:*               LISTEN      56153/docker-proxy

tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      8249/nginx: master

tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3381/docker-proxy

tcp6       0      0 :::8085                 :::*                    LISTEN      56027/docker-proxy

tcp6       0      0 :::8081                 :::*                    LISTEN      117989/docker-proxy

tcp6       0      0 :::8083                 :::*                    LISTEN      56160/docker-proxy

tcp6       0      0 :::8000                 :::*                    LISTEN      8249/nginx: master

tcp6       0      0 :::80                   :::*                    LISTEN      3389/docker-proxy

output of netstat -tulpn | grep 443


tcp        0      0 0.0.0.0:4430            0.0.0.0:*               LISTEN      8249/nginx: master

tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      3308/docker-proxy

tcp6       0      0 :::4430                 :::*                    LISTEN      8249/nginx: master

tcp6       0      0 :::443                  :::*                    LISTEN      3317/docker-proxy

output of netstat -tulpn | grep 81


tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      117982/docker-proxy

tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3381/docker-proxy

tcp        0      0 0.0.0.0:81              0.0.0.0:*               LISTEN      3357/docker-proxy

tcp6       0      0 :::8081                 :::*                    LISTEN      117989/docker-proxy

tcp6       0      0 :::81                   :::*                    LISTEN      3365/docker-proxy

it seems to fails to bind ports 80, 81, 443 ...

the only thing that solves it is a restart of the docker container, which works fine, then after some time it repeats again ... I tried wiping it all out and starting all over again from scratch, and the same problem occurs

Did you delete data directories as well? That's what I had to do to fix it.

<!-- gh-comment-id:1356842431 --> @Go2Engle commented on GitHub (Dec 18, 2022): > I've dealing with this same issue for months ... logs stuck in infinite loop > > > > ``` > > 12/18/2022 12:24:12 PM Disabling IPV6 in hosts > > 12/18/2022 12:24:12 PM ❯ Disabling IPV6 in hosts: /data/nginx > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/1.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/9.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/2.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/3.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/4.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/5.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/10.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/7.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/6.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/proxy_host/11.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/http.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/root.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/http_top.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_proxy.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_redirect.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream_tcp.conf > > 12/18/2022 12:24:12 PM ❯ /data/nginx/custom/server_stream_udp.conf > > 12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) > > 12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) > > 12/18/2022 12:24:12 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) > > 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) > > 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) > > 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) > > 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) > > 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) > > 12/18/2022 12:24:13 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) > > 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) > > 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) > > 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) > > 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) > > 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) > > 12/18/2022 12:24:14 PM nginx: [emerg] bind() to 0.0.0.0:81 failed (98: Address already in use) > > 12/18/2022 12:24:15 PM nginx: [emerg] still could not bind() > > ``` > > > > output of `netstat -tulpn | grep 80` > > > > ``` > > tcp 0 0 0.0.0.0:8085 0.0.0.0:* LISTEN 56020/docker-proxy > > tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 117982/docker-proxy > > tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 56153/docker-proxy > > tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 8249/nginx: master > > tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3381/docker-proxy > > tcp6 0 0 :::8085 :::* LISTEN 56027/docker-proxy > > tcp6 0 0 :::8081 :::* LISTEN 117989/docker-proxy > > tcp6 0 0 :::8083 :::* LISTEN 56160/docker-proxy > > tcp6 0 0 :::8000 :::* LISTEN 8249/nginx: master > > tcp6 0 0 :::80 :::* LISTEN 3389/docker-proxy > > ``` > > > > output of `netstat -tulpn | grep 443` > > > > ``` > > tcp 0 0 0.0.0.0:4430 0.0.0.0:* LISTEN 8249/nginx: master > > tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3308/docker-proxy > > tcp6 0 0 :::4430 :::* LISTEN 8249/nginx: master > > tcp6 0 0 :::443 :::* LISTEN 3317/docker-proxy > > ``` > > > > output of `netstat -tulpn | grep 81` > > > > ``` > > tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 117982/docker-proxy > > tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3381/docker-proxy > > tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 3357/docker-proxy > > tcp6 0 0 :::8081 :::* LISTEN 117989/docker-proxy > > tcp6 0 0 :::81 :::* LISTEN 3365/docker-proxy > > ``` > > > > it seems to fails to bind ports `80`, `81`, `443` ... > > > > the only thing that solves it is a restart of the docker container, which works fine, then after some time it repeats again ... I tried wiping it all out and starting all over again from scratch, and the same problem occurs Did you delete data directories as well? That's what I had to do to fix it.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@ahmadnassri commented on GitHub (Dec 18, 2022):

yep, nuked the whole data directory.

<!-- gh-comment-id:1356842871 --> @ahmadnassri commented on GitHub (Dec 18, 2022): yep, nuked the whole data directory.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@iambdud commented on GitHub (Dec 21, 2022):

I’m still having this “issue”. I put issue in quotes because it does not seem to impact anything… I’m currently proxying several different sites without issue.

<!-- gh-comment-id:1361350111 --> @iambdud commented on GitHub (Dec 21, 2022): I’m still having this “issue”. I put issue in quotes because it does not seem to impact anything… I’m currently proxying several different sites without issue.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@IvanKhramov commented on GitHub (Mar 3, 2023):

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

<!-- gh-comment-id:1453217608 --> @IvanKhramov commented on GitHub (Mar 3, 2023): This problem still without a solution, did anyone figure out how to solve?
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@kreddad commented on GitHub (Mar 28, 2023):

check here for temporary solution
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2750

<!-- gh-comment-id:1487106644 --> @kreddad commented on GitHub (Mar 28, 2023): check here for temporary solution https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2750
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@MauOnline commented on GitHub (Jul 31, 2025):

Wow, still there in 2025. Not really inspiring. Why is the ticket is closed?

<!-- gh-comment-id:3139832854 --> @MauOnline commented on GitHub (Jul 31, 2025): Wow, still there in 2025. Not really inspiring. Why is the ticket is closed?
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@clemone210 commented on GitHub (Jul 31, 2025):

Wow, still there in 2025. Not really inspiring. Why is the ticket is closed?

the issue is not present anymore with latest version on my side, feel free to open a new issue if you have this problem and reference to this one.

<!-- gh-comment-id:3139892654 --> @clemone210 commented on GitHub (Jul 31, 2025): > Wow, still there in 2025. Not really inspiring. Why is the ticket is closed? the issue is not present anymore with latest version on my side, feel free to open a new issue if you have this problem and reference to this one.
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@cd-slash commented on GitHub (Sep 23, 2025):

I am still seeing the same issue in Sept 2025

<!-- gh-comment-id:3322713025 --> @cd-slash commented on GitHub (Sep 23, 2025): I am still seeing the same issue in Sept 2025
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@HendrikHaase commented on GitHub (Oct 12, 2025):

The issue still persists. What info can i provide to narrow it down?

i recall it occured some minutes after adding a a new host (just creating the host, no new ssl cert or anything that requires external communication)

<!-- gh-comment-id:3394164942 --> @HendrikHaase commented on GitHub (Oct 12, 2025): The issue still persists. What info can i provide to narrow it down? i recall it occured some minutes after adding a a new host (just creating the host, no new ssl cert or anything that requires external communication)
kerem commented 2026-02-26 06:34:05 +03:00
Author
Owner
Copy link

@adamef93 commented on GitHub (Jan 25, 2026):

Still a very active problem, this shouldn't be closed

<!-- gh-comment-id:3795988501 --> @adamef93 commented on GitHub (Jan 25, 2026): Still a very active problem, this shouldn't be closed
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#706
No description provided.