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 #24] New option to support upstream self signed ssl connections #23

New issue

Closed

opened 2026-02-26 05:33:06 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 05:33:06 +03:00

Owner

Originally created by @jc21 on GitHub (Nov 4, 2018).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/24

Some upstream hosts only provide a SSL connection and they are sometimes using self signed certificates (EdgeOS is one such example).

Would be nice to have an option to specify that the upstream is SSL and the nginx proxy would ignore certificate errors because the server should be in control of the user who's creating the reverse proxy.

In most cases this means that the Proxy Host setup requires SSL as well and the added benefit here is that the edge host will be using a certified certificate at all times, regardless of what the upstream host has.

Originally created by @jc21 on GitHub (Nov 4, 2018). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/24 Some upstream hosts only provide a SSL connection and they are sometimes using self signed certificates (EdgeOS is one such example). Would be nice to have an option to specify that the upstream is SSL and the nginx proxy would ignore certificate errors because the server should be in control of the user who's creating the reverse proxy. In most cases this means that the Proxy Host setup requires SSL as well and the added benefit here is that the edge host will be using a certified certificate at all times, regardless of what the upstream host has.

kerem

2026-02-26 05:33:06 +03:00

closed this issue
added the
enhancement
label

kerem commented

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

Author

Owner

@sh4444dow commented on GitHub (Dec 12, 2018):

That feature is definetely needed in a bunch of situations. I even considered to produce a pull request concerning this feature. Did you start to implement it ?

Sincerely,

@sh4444dow

@sh4444dow commented on GitHub (Dec 12, 2018): That feature is definetely needed in a bunch of situations. I even considered to produce a pull request concerning this feature. Did you start to implement it ? Sincerely, @sh4444dow

kerem commented

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

Author

Owner

@jc21 commented on GitHub (Dec 12, 2018):

No not yet. I left this note for myself to get to later. Give me a couple of days and I'll see if I have time to put it in quickly.

@jc21 commented on GitHub (Dec 12, 2018): No not yet. I left this note for myself to get to later. Give me a couple of days and I'll see if I have time to put it in quickly.

kerem commented

2026-02-26 05:33:08 +03:00

Author

Owner

@sh4444dow commented on GitHub (Dec 13, 2018):

Okay =) If I'm not mistaken, this enhancement note is strongly related to #34 issue. I link it just for reminder.

Sincerely,

@sh4444dow

@sh4444dow commented on GitHub (Dec 13, 2018): Okay =) If I'm not mistaken, this enhancement note is strongly related to #34 issue. I link it just for reminder. Sincerely, @sh4444dow

kerem commented

2026-02-26 05:33:08 +03:00

Author

Owner

@jc21 commented on GitHub (Jan 3, 2019):

Added in v2.0.7

@jc21 commented on GitHub (Jan 3, 2019): Added in v2.0.7

kerem referenced this issue

2026-02-26 07:38:21 +03:00

[PR #23] [MERGED] Added default HTTPs site. #3178

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

No description provided.

Rows
Columns