mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2499] Certificate renew not possible if force https is selected. #1744
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1744
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SvenPausH on GitHub (Dec 23, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2499
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Certificate renew not possible if force https is selected.
Nginx Proxy Manager Version
latest 2.9.19
To Reproduce
Steps to reproduce the behavior:
Operating System
RPI4
@LanceMcCarthy commented on GitHub (Dec 25, 2022):
[EDIT] It turns out my issue was related to the firewall blocking traffic from 127.0.0.1. It's not related to the OP's question apparently.
@ybizeul commented on GitHub (Jan 19, 2023):
I wonder, is your certificate still valid when you are trying to renew ?
I might be totally off, but I think the way it works, is HTTP validation works over HTTPS as long as your current certificate is still valid, otherwise, it'll try and use http. But if you force redirect that would bounce back to https which is no longer valid.
Just a thought.
@github-actions[bot] commented on GitHub (Feb 1, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 18, 2025):
Issue was closed due to inactivity.