starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #2418] Internal error on renewing SSL certificate when all requests of proxy host are redirected #1697

New issue

Closed

opened 2026-02-26 07:32:05 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 07:32:05 +03:00

Owner

Originally created by @davhae on GitHub (Nov 22, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2418

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- No
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug
When using the Advanced NGINX Configuration of a proxy host to redirect all requests, renewal of certificates returns an internal error.

The configuration may look like this:

rewrite ^(/.*)$ https://another-domain.com/ permanent;

Nginx Proxy Manager Version
v2.9.18

Expected behavior
I don't really know if it is expected, but requests to .well-known should be handled by the reverse proxy.

Operating System
Ubuntu Jammy

Originally created by @davhae on GitHub (Nov 22, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2418 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - No - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** When using the Advanced NGINX Configuration of a proxy host to redirect all requests, renewal of certificates returns an internal error. The configuration may look like this: ``` rewrite ^(/.*)$ https://another-domain.com/ permanent; ``` **Nginx Proxy Manager Version** v2.9.18 **Expected behavior** I don't really know if it is expected, but requests to .well-known should be handled by the reverse proxy. **Operating System** Ubuntu Jammy

kerem

2026-02-26 07:32:05 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:32:05 +03:00

Author

Owner

@the1ts commented on GitHub (Nov 23, 2022):

Just asking, but does the problem domain have force-ssl enabled? There is a bug with this config, remove the force-ssl, manually renew and turn back on until the fixed is merged and released. The bug is because the current config forces the redirect to https before letsencrypt exception is processed so letsencrypt fails since it doesn't work over https. So check if its this bug or your rewrite that is causing the letsencrypt breakage.

@the1ts commented on GitHub (Nov 23, 2022): Just asking, but does the problem domain have force-ssl enabled? There is a bug with this config, remove the force-ssl, manually renew and turn back on until the fixed is merged and released. The bug is because the current config forces the redirect to https before letsencrypt exception is processed so letsencrypt fails since it doesn't work over https. So check if its this bug or your rewrite that is causing the letsencrypt breakage.

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@gnilebein commented on GitHub (Dec 12, 2022):

Just asking, but does the problem domain have force-ssl enabled? There is a bug with this config, remove the force-ssl, manually renew and turn back on until the fixed is merged and released. The bug is because the current config forces the redirect to https before letsencrypt exception is processed so letsencrypt fails since it doesn't work over https. So check if its this bug or your rewrite that is causing the letsencrypt breakage.

Is there an issue about the bug that I can subscribe to in order to get an info when it is fixed? I could not find one with the search.

@gnilebein commented on GitHub (Dec 12, 2022): > Just asking, but does the problem domain have force-ssl enabled? There is a bug with this config, remove the force-ssl, manually renew and turn back on until the fixed is merged and released. The bug is because the current config forces the redirect to https before letsencrypt exception is processed so letsencrypt fails since it doesn't work over https. So check if its this bug or your rewrite that is causing the letsencrypt breakage. Is there an issue about the bug that I can subscribe to in order to get an info when it is fixed? I could not find one with the search.

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@davhae commented on GitHub (Dec 12, 2022):

Disabling force-ssl for the only Redirection-Host using the certificate does not make it renewable.
On the other hand, temporarily removing the rewrite while force-ssl is activate results in a successful renew.

@davhae commented on GitHub (Dec 12, 2022): Disabling force-ssl for the only Redirection-Host using the certificate does not make it renewable. On the other hand, temporarily removing the rewrite while force-ssl is activate results in a successful renew.

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@gnilebein commented on GitHub (Dec 12, 2022):

Disabling force-ssl for the only Redirection-Host using the certificate does not make it renewable. On the other hand, temporarily removing the rewrite while force-ssl is activate results in a successful renew.

There is an fix for the issue... Just need to be merged... i added the change to my docker container (FIX: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/2038)

@gnilebein commented on GitHub (Dec 12, 2022): > Disabling force-ssl for the only Redirection-Host using the certificate does not make it renewable. On the other hand, temporarily removing the rewrite while force-ssl is activate results in a successful renew. There is an fix for the issue... Just need to be merged... i added the change to my docker container (FIX: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/2038)

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@davhae commented on GitHub (Dec 13, 2022):

Disabling force-ssl for the only Redirection-Host using the certificate does not make it renewable. On the other hand, temporarily removing the rewrite while force-ssl is activate results in a successful renew.

There is an fix for the issue... Just need to be merged... i added the change to my docker container (FIX: #2038)

Like i said it has nothing to do with force-ssl

@davhae commented on GitHub (Dec 13, 2022): > > Disabling force-ssl for the only Redirection-Host using the certificate does not make it renewable. On the other hand, temporarily removing the rewrite while force-ssl is activate results in a successful renew. > > There is an fix for the issue... Just need to be merged... i added the change to my docker container (FIX: #2038) Like i said it has nothing to do with force-ssl

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@evelynhathaway commented on GitHub (Dec 26, 2022):

@davhae Maybe the issue is that rewrite redirects before the NPM has a chance to respond to Let's Encrypt. What if you try wrapping your rewrite in a location block?

Custom Nginx Configuration - Redirects ACME challenge (Before)

rewrite ^(/.*)$ https://another-domain.com/ permanent;

Custom Nginx Configuration - Responds to ACME challenge (After)

location / {
  rewrite ^(/.*)$ https://another-domain.com/ permanent;
}

@evelynhathaway commented on GitHub (Dec 26, 2022): @davhae Maybe the issue is that `rewrite` redirects before the NPM has a chance to respond to Let's Encrypt. What if you try wrapping your `rewrite` in a `location` block? **Custom Nginx Configuration - Redirects ACME challenge (Before)** ```nginx rewrite ^(/.*)$ https://another-domain.com/ permanent; ``` **Custom Nginx Configuration - Responds to ACME challenge (After)** ```nginx location / { rewrite ^(/.*)$ https://another-domain.com/ permanent; } ```

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 4, 2024):

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

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

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 21, 2025):

Issue was closed due to inactivity.

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

kerem referenced this issue

2026-02-26 08:30:46 +03:00

[PR #1697] [MERGED] Sets certbot official dns plugin version requirement to match certbot version #3471

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

No description provided.

Rows
Columns