starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #3737] 'force HTTPS' switch not recognized when creating new (proxy) host #2468

New issue

Closed

opened 2026-02-26 07:35:40 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:35:40 +03:00

Owner

Originally created by @shakebox on GitHub (May 3, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3737

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- No, but creator of other image confirmed that issue should be an upstream issue
Are you sure you're not using someone else's docker image?
- No, using other image, but issue seems to be upstream issue
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug
When creating new (proxy, haven't tested others) host and you turn on the 'force HTTPS' switch, this setting will not be stored. You need to re-enable it manually by doing "edit" on the same host afterwards. Only then the activation of this switch is actually doing something!

Nginx Proxy Manager Version
2.11.1

To Reproduce
Steps to reproduce the behavior:

press 'add proxy host'
fill in the details and switch to the 'TLS' tab
set the cert or set to 'request a new TLS certificate', then TURN ON the 'force HTTPS' button
save and wait until you have new host created
go to 'edit' for this newly created host
go to TLS tab and see that the 'force HTTPS' button is NOT active

Expected behavior
when turning on any of the options switches while creating a new host, I'd expect it 'to do something' and not being ignored. For newbie users it may be dangerous because they may rely on the switch to behave as expected and never check the settings again after the initial creation.

Screenshots

Operating System
Ubuntu 22.04

Additional context
i was told from a fork user that it may be related to this: github.com/NginxProxyManager/nginx-proxy-manager@79cd0c5294/backend/internal/host.js (L22)
as this is also called for new hosts and therefore the ssl_forced is always set to 'false'!?

Originally created by @shakebox on GitHub (May 3, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3737 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - No, but creator of other image confirmed that issue should be an upstream issue - Are you sure you're not using someone else's docker image? - No, using other image, but issue seems to be upstream issue - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** When creating new (proxy, haven't tested others) host and you turn on the 'force HTTPS' switch, this setting will not be stored. You need to re-enable it manually by doing "edit" on the same host afterwards. Only then the activation of this switch is actually doing something! **Nginx Proxy Manager Version** 2.11.1 **To Reproduce** Steps to reproduce the behavior: 1. press 'add proxy host' 2. fill in the details and switch to the 'TLS' tab 3. set the cert or set to 'request a new TLS certificate', then TURN ON the 'force HTTPS' button 4. save and wait until you have new host created 5. go to 'edit' for this newly created host 6. go to TLS tab and see that the 'force HTTPS' button is NOT active **Expected behavior** when turning on any of the options switches while creating a new host, I'd expect it 'to do something' and not being ignored. For newbie users it may be dangerous because they may rely on the switch to behave as expected and never check the settings again after the initial creation. **Screenshots**  **Operating System** Ubuntu 22.04 **Additional context** i was told from a fork user that it may be related to this: https://github.com/NginxProxyManager/nginx-proxy-manager/blob/79cd0c5294f1e3ad4cc9ed5187b7759808b91162/backend/internal/host.js#L22 as this is also called for new hosts and therefore the ssl_forced is always set to 'false'!?

kerem

2026-02-26 07:35:40 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:35:41 +03:00

Author

Owner

@manilx commented on GitHub (May 20, 2024):

I have found the same issue. This has been fine on older versions, as I'm not adding new entries all the time I just found this now.

@manilx commented on GitHub (May 20, 2024): I have found the same issue. This has been fine on older versions, as I'm not adding new entries all the time I just found this now.

kerem commented

2026-02-26 07:35:41 +03:00

Author

Owner

@code-a-cola commented on GitHub (Jun 11, 2024):

happening to me as well

@code-a-cola commented on GitHub (Jun 11, 2024): happening to me as well

kerem commented

2026-02-26 07:35:41 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 27, 2024):

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

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

kerem commented

2026-02-26 07:35:41 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 18, 2026):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Jan 18, 2026): Issue was closed due to inactivity.

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

No description provided.

Rows
Columns