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 #2185] Internal Server Error #1564

New issue

Closed

opened 2026-02-26 07:31:35 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:31:35 +03:00

Owner

Originally created by @Sum4196 on GitHub (Aug 2, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2185

This issue seems to come up when an SSL certificate is tied to proxy_host entries and the SSL certificate is removed. The text below helped me get around this issue. However, I think it would be a very simple thing to implement to warn the user or simply not allow the removal of an SSL certificate if it's in use. I hope this helps someone else or possibly starts the process to a solution for everyone. Thank you @BetterToAutomateTheWorld for your response below as it helped me get back up and running without having to start over.

"""
Solution find in my case :

copy pasting a nmp-xx certificates folder to the one which nginx is looking at
nginx -t
restart container

(anyway, this issue in basically from the root because we don't use the certificate for a specific domain, or a domain for a specific certificate, I will guess a deletion has gone wrong somewhere)

I will guess the best way to fix it in a clean way would be to delete all domains, certificates, and recreate all from zero/root...

PS : didn't know where the occurrence of the certificate was in my configuration in my case, a find / grep -r didn't return anything

Originally posted by @BetterToAutomateTheWorld in https://github.com/NginxProxyManager/nginx-proxy-manager/issues/133#issuecomment-670184450
"""

Originally created by @Sum4196 on GitHub (Aug 2, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2185 This issue seems to come up when an SSL certificate is tied to proxy_host entries and the SSL certificate is removed. The text below helped me get around this issue. However, I think it would be a very simple thing to implement to warn the user or simply not allow the removal of an SSL certificate if it's in use. I hope this helps someone else or possibly starts the process to a solution for everyone. Thank you @BetterToAutomateTheWorld for your response below as it helped me get back up and running without having to start over. """ Solution find in my case : - copy pasting a nmp-xx certificates folder to the one which nginx is looking at - nginx -t - restart container _(anyway, this issue in basically from the root because we don't use the certificate for a specific domain, or a domain for a specific certificate, I will guess a deletion has gone wrong somewhere)_ I will guess the best way to fix it in a clean way would be to delete all domains, certificates, and recreate all from zero/root... _PS : didn't know where the occurrence of the certificate was in my configuration in my case, a `find / grep -r` didn't return anything_ _Originally posted by @BetterToAutomateTheWorld in https://github.com/NginxProxyManager/nginx-proxy-manager/issues/133#issuecomment-670184450_ """

kerem

2026-02-26 07:31:35 +03:00

closed this issue
added the
stale
label

kerem commented

2026-02-26 07:31:35 +03:00

Author

Owner

@DerfOh commented on GitHub (Feb 2, 2023):

This issue is a huge headache to face in production, really poisons the water for using NPM for letsencrypt if a massive bug like this can occur. I deleted my certs because that's the only way I can seemingly get around the "another instance of certbot is running" bug and now here I am pulling my hair out at 4:30pm because for some reason today this happens can't even get to the login page because nginx refuses to start. Using NPM v2.9.19

Edit:
The above workaround works, copying another site's npm certificates folder to the one that is missing but really it shouldn't come down to that. For now I'll be changing over to using a wildcard cert generated outside of NPM until the issue is closed. Hopefully maintainers are understanding that this is a show-stopping bug and refactor the SSL/Certbot components as having to manually bash into a container to just make it work is exceedingly tedious and sort-of pours water on the ease of using a UI overlay like NPM.

@DerfOh commented on GitHub (Feb 2, 2023): This issue is a huge headache to face in production, really poisons the water for using NPM for letsencrypt if a massive bug like this can occur. I deleted my certs because that's the only way I can seemingly get around the ["another instance of certbot is running" bug ](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/918) and now here I am pulling my hair out at 4:30pm because for some reason today this happens can't even get to the login page because nginx refuses to start. Using NPM v2.9.19 Edit: The above workaround works, copying another site's npm certificates folder to the one that is missing but really it shouldn't come down to that. For now I'll be changing over to using a wildcard cert generated outside of NPM until the issue is closed. Hopefully maintainers are understanding that this is a show-stopping bug and refactor the SSL/Certbot components as having to manually bash into a container to just make it work is exceedingly tedious and sort-of pours water on the ease of using a UI overlay like NPM.

kerem commented

2026-02-26 07:31:35 +03:00

Author

Owner

@andeerc commented on GitHub (Jan 9, 2024):

Estou sofrendo o mesmo problema, mas por algum motivo não gera nenhum log, nem no console, e continua retornando um "500 internal server error"

@andeerc commented on GitHub (Jan 9, 2024): Estou sofrendo o mesmo problema, mas por algum motivo não gera nenhum log, nem no console, e continua retornando um "500 internal server error"

kerem commented

2026-02-26 07:31:35 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 6, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Aug 6, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:31:35 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 15, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Aug 15, 2025): Issue was closed due to inactivity.

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

No description provided.

Rows
Columns