mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1196] ssl passthrough toggle switch #977
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#977
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 @michael-pellegrini on GitHub (Jun 21, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1196
SSL pass-through toggle switch for proxy hosts.
The problem is that many devices on the network have their own self signed SSL certificates and
I cannot use NPM to proxy to these hosts without gathering and uploading each device's certificates to NPM.
Because NPM performs the SSL termination.
The solution I would like is a toggle switch on the add new proxy host window that would pass the devices self-signed cert.
Eliminating the need to upload each certficate.
@the1ts commented on GitHub (Jul 29, 2021):
Just checking on the underlying problem, are you saying that NPM cannot proxy for a self-signed cert host in the destination section of edit proxy host? as I'm doing that without the need to trust that cert in NPM. Or are you saying you have to see the self-signed cert in a client through NPM rather than the lets encrypt cert?
@chaptergy commented on GitHub (Oct 12, 2021):
SSL passthrough is unfortunately not that easy. please see https://github.com/jc21/nginx-proxy-manager/issues/853#issuecomment-941035257