starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #892] Starting w/ 2.8.0 seeing errors and significant CPU usage #755

New issue

Closed

opened 2026-02-26 06:34:17 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 06:34:17 +03:00

Owner

Originally created by @yieldhog on GitHub (Feb 13, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/892

Using 2.8.0 docker image on Synology. Have been successfully using this tool for over a year (its great). I noticed with the latest version my CPU usage has been spiking quite a bit, logs show a looping error as follows, I did not change any settings from 2.7.3 to 2.8.0, thank you.

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:  2711 Illegal instruction     (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

Originally created by @yieldhog on GitHub (Feb 13, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/892 Using 2.8.0 docker image on Synology. Have been successfully using this tool for over a year (its great). I noticed with the latest version my CPU usage has been spiking quite a bit, logs show a looping error as follows, I did not change any settings from 2.7.3 to 2.8.0, thank you. ``` 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: 2711 Illegal instruction (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js ```

kerem

2026-02-26 06:34:17 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:34:17 +03:00

Author

Owner

@appleimperio commented on GitHub (Feb 13, 2021):

Same here on Open Media Vault raspberry pi 4, image v 2.8.0
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)

@appleimperio commented on GitHub (Feb 13, 2021): Same here on Open Media Vault raspberry pi 4, image v 2.8.0 ` 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) `

kerem commented

2026-02-26 06:34:17 +03:00

Author

Owner

@jiriteach commented on GitHub (Feb 13, 2021):

I experienced this as well as part of the upgrade. I killed my containers and re-launched with existing config and all is working fine now.

@jiriteach commented on GitHub (Feb 13, 2021): I experienced this as well as part of the upgrade. I killed my containers and re-launched with existing config and all is working fine now.

kerem commented

2026-02-26 06:34:17 +03:00

Author

Owner

@appleimperio commented on GitHub (Feb 13, 2021):

Thanks it worked with a restart of the container i was having the same issue, I delete the container and created again with same config.

@appleimperio commented on GitHub (Feb 13, 2021): Thanks it worked with a restart of the container i was having the same issue, I delete the container and created again with same config.

kerem commented

2026-02-26 06:34:17 +03:00

Author

Owner

@yieldhog commented on GitHub (Feb 13, 2021):

@Jiriteach Thanks, I deleted the container and restarted. No longer getting prior error. I tried renewing an SSL certificate but am getting this error now, are you?

Renewing Let'sEncrypt certificates via Cloudflare for Cert #7: XXXX.com
Command failed: /usr/bin/certbot renew --non-interactive --cert-name "npm-7" --disable-hook-validation
Another instance of Certbot is already running.

@yieldhog commented on GitHub (Feb 13, 2021): @Jiriteach Thanks, I deleted the container and restarted. No longer getting prior error. I tried renewing an SSL certificate but am getting this error now, are you? ``` Renewing Let'sEncrypt certificates via Cloudflare for Cert #7: XXXX.com Command failed: /usr/bin/certbot renew --non-interactive --cert-name "npm-7" --disable-hook-validation Another instance of Certbot is already running. ```

kerem commented

2026-02-26 06:34:17 +03:00

Author

Owner

@yieldhog commented on GitHub (Feb 13, 2021):

Nevermind, looks like it has to do with DNS challenge on my part related to Cloudflare.

As far as the issue above and "address in use" / excessive CPU usage on upgrade to 2.8.0, it seems like the solution is to delete the container and build again. Thanks for the help.

@yieldhog commented on GitHub (Feb 13, 2021): Nevermind, looks like it has to do with DNS challenge on my part related to Cloudflare. As far as the issue above and "address in use" / excessive CPU usage on upgrade to 2.8.0, it seems like the solution is to delete the container and build again. Thanks for the help.

kerem commented

2026-02-26 06:34:17 +03:00

Author

Owner

@appleimperio commented on GitHub (Feb 13, 2021):

@Jiriteach Thanks, I deleted the container and restarted. No longer getting prior error. I tried renewing an SSL certificate but am getting this error now, are you?
Renewing Let'sEncrypt certificates via Cloudflare for Cert #7: XXXX.com
Command failed: /usr/bin/certbot renew --non-interactive --cert-name "npm-7" --disable-hook-validation
Another instance of Certbot is already running.

I use Cloudflare too and getting similar error how did you solve it?
[2/13/2021] [11:07:00 PM] [SSL ] › ✖ error Error: Command failed: /usr/bin/certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation

@appleimperio commented on GitHub (Feb 13, 2021): > @Jiriteach Thanks, I deleted the container and restarted. No longer getting prior error. I tried renewing an SSL certificate but am getting this error now, are you? > > ``` > Renewing Let'sEncrypt certificates via Cloudflare for Cert #7: XXXX.com > Command failed: /usr/bin/certbot renew --non-interactive --cert-name "npm-7" --disable-hook-validation > Another instance of Certbot is already running. > ``` I use Cloudflare too and getting similar error how did you solve it? [2/13/2021] [11:07:00 PM] [SSL ] › ✖ error Error: Command failed: /usr/bin/certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation

kerem commented

2026-02-26 06:34:17 +03:00

Author

Owner

@yieldhog commented on GitHub (Feb 14, 2021):

@appleimperio I had to delete the SSL, re-create using additional information from issue #680 I added:

# Cloudflare API token
dns_cloudflare_email=something@hotmail.com
dns_cloudflare_api_key = 0123456789abcdef0123456789abcdef01234567

After re-creating the SSL cert using the above, seems as if I am able to renew as well.

@yieldhog commented on GitHub (Feb 14, 2021): @appleimperio I had to delete the SSL, re-create using additional information from issue #680 I added: ``` # Cloudflare API token dns_cloudflare_email=something@hotmail.com dns_cloudflare_api_key = 0123456789abcdef0123456789abcdef01234567 ``` After re-creating the SSL cert using the above, seems as if I am able to renew as well.

kerem commented

2026-02-26 06:34:17 +03:00

Author

Owner

@Nenodema commented on GitHub (Feb 15, 2021):

Rebuilding the container was indeed the solution...!

@Nenodema commented on GitHub (Feb 15, 2021): Rebuilding the container was indeed the solution...!

No milestone

No project

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#755

No description provided.

Rows
Columns