mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #776] Request: "ssl_preread" functionality #652
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#652
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 @andyad8865 on GitHub (Dec 16, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/776
Is your feature request related to a problem? Please describe.
yes, I have multiple hosts that already gather and maintain their own certificates and currently, the manager does not appear to support hosts having their own certs and just forwarding only create a new cert per host.
Describe the solution you'd like
I would like under the SSL options for the "ssl_preread" to be made available for people who have such a case of hosts that already manage their own certificates.
Describe alternatives you've considered
The only other alternatives I can find is removing SSL from the host and then managing the host SSL from the manager like a normal non-SSL host.
@github-actions[bot] commented on GitHub (Mar 22, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@andyad8865 commented on GitHub (Mar 22, 2024):
Bump
@github-actions[bot] commented on GitHub (Dec 16, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Jan 30, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍