[GH-ISSUE #1232] I can't revert back to the normal http #1003

New issue

Closed

opened 2026-02-26 06:35:24 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:35:24 +03:00

Owner

Originally created by @ArsBinarii on GitHub (Jul 11, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1232

Version 2.9.4
I enabled all options under SSL and generated a SSL certificate for a Proxy Host.
I can't revert back to the normal http
I removed the certificate, disabled all under ssl, changed the scheme to http, it still redirects to https, certificate is still there

Originally created by @ArsBinarii on GitHub (Jul 11, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1232 Version 2.9.4 I enabled all options under SSL and generated a SSL certificate for a Proxy Host. I can't revert back to the normal http I removed the certificate, disabled all under ssl, changed the scheme to http, it still redirects to https, certificate is still there

kerem

2026-02-26 06:35:24 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-02-26 06:35:24 +03:00

Author

Owner

@the1ts commented on GitHub (Jul 29, 2021):

One of the options under SSL is HSTS (HTTP Strict Transport Security), this tells a browser to never allow non-https to that host, so the browser, in future requests, never hits http:// but the browser itself rewrites your request to https://. This HSTS request from the server side (NPM) is cached by the browser, in the case of NPM for 2 years.

In short both the browser and NPM are doing exactly what you requested it to do by ticking that HSTS box and visiting the page.

To fix take a look at how to remove HSTS for your particular web browser and follow the instructions for this problem host. Or move to a different hostname.

@the1ts commented on GitHub (Jul 29, 2021): One of the options under SSL is HSTS (HTTP Strict Transport Security), this tells a browser to never allow non-https to that host, so the browser, in future requests, never hits http:// but the browser itself rewrites your request to https://. This HSTS request from the server side (NPM) is cached by the browser, in the case of NPM for 2 years. In short both the browser and NPM are doing exactly what you requested it to do by ticking that HSTS box and visiting the page. To fix take a look at how to remove HSTS for your particular web browser and follow the instructions for this problem host. Or move to a different hostname.

kerem commented

2026-02-26 06:35:24 +03:00

Author

Owner

@chaptergy commented on GitHub (Jul 29, 2021):

Just to add here are some direct links on how to remove HSTS in Firefox, Chrome and Safari

@chaptergy commented on GitHub (Jul 29, 2021): Just to add here are some direct links on how to [remove HSTS in Firefox, Chrome and Safari](https://community.spiceworks.com/how_to/158595-how-to-clear-hsts-settings-for-safari-firefox-and-chrome)

kerem referenced this issue

2026-02-26 08:32:02 +03:00

[PR #4098] [CLOSED] Duplicate advanced_config to both top and bottom #3812

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

No description provided.

Rows
Columns