[GH-ISSUE #184] SSL settings are not applied

kerem commented

2026-02-26 06:31:00 +03:00

Owner

Originally created by @pikausp on GitHub (Aug 7, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/184

Describe the bug
SSL settings are not applied when creating a new proxy. The cert is indeed generated and HTTPS is supported, however, settings such as Force SSL do not take effect. I found out when I added a new proxy and tried accessing the site. I was not redirected to HTTPS.

I verified I had not forgotten to check toggle the buttons by creating a new site and verified the same issue occurred. I also checked the id.conf file and things such as including the force SSL file were missing.

Opening the Edit dialog and toggling the options gets the desired results.

The version of NPM I use is 2.0.13

This is the conf file when I checked Force SSL, HTTP/2 Support and HSTS Enabled.

server {
  set $forward_scheme http;
  set $server         "127.0.0.1";
  set $port           81;

  listen 80;
listen 443 ssl http2;

  server_name my.test.domain.com;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-4/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-4/privkey.pem;

# Asset Caching
  include conf.d/include/assets.conf;

  # Block Exploits
  include conf.d/include/block-exploits.conf;

  access_log /data/logs/proxy_host-4.log proxy;

  location / {
    # Proxy!
    include conf.d/include/proxy.conf;
  }
}

To Reproduce
Steps to reproduce the behavior:

Go to 'Proxy Hosts'
Click on 'Add proxy host'
Fill out the site information
Go to 'SSL' tab
Toggle on Force SSL, HTTP/2 Support, HSTS Enabled

Expected behavior
The settings will take effect and the site config will reflect the settings.

Screenshots
When I select all those and then go edit the host, the certificate is selected but all the options I checked previously are unchecked

Originally created by @pikausp on GitHub (Aug 7, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/184 **Describe the bug** SSL settings are not applied when creating a new proxy. The cert is indeed generated and HTTPS is supported, however, settings such as Force SSL do not take effect. I found out when I added a new proxy and tried accessing the site. I was not redirected to HTTPS. I verified I had not forgotten to check toggle the buttons by creating a new site and verified the same issue occurred. I also checked the `id.conf` file and things such as including the force SSL file were missing. Opening the `Edit` dialog and toggling the options gets the desired results. The version of NPM I use is 2.0.13 This is the conf file when I checked Force SSL, HTTP/2 Support and HSTS Enabled. ``` server { set $forward_scheme http; set $server "127.0.0.1"; set $port 81; listen 80; listen 443 ssl http2; server_name my.test.domain.com; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-4/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-4/privkey.pem; # Asset Caching include conf.d/include/assets.conf; # Block Exploits include conf.d/include/block-exploits.conf; access_log /data/logs/proxy_host-4.log proxy; location / { # Proxy! include conf.d/include/proxy.conf; } } ``` **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Proxy Hosts' 2. Click on 'Add proxy host' 3. Fill out the site information 4. Go to 'SSL' tab 5. Toggle on Force SSL, HTTP/2 Support, HSTS Enabled **Expected behavior** The settings will take effect and the site config will reflect the settings. **Screenshots** When I select all those and then go edit the host, the certificate is selected but all the options I checked previously are unchecked ![image](https://user-images.githubusercontent.com/6717146/62621559-72566c00-b91c-11e9-8787-bca799d03c4b.png)

kerem added the

bug

label

2026-02-26 06:31:00 +03:00

kerem commented

2026-02-26 06:31:01 +03:00

Author

Owner

@nldoty commented on GitHub (Aug 20, 2019):

I am also experiencing this as well.

@nldoty commented on GitHub (Aug 20, 2019): I am also experiencing this as well.

kerem commented

2026-02-26 06:31:01 +03:00

Author

Owner

@giomf commented on GitHub (Nov 11, 2020):

Got the same problem over here.
Actually the forwarding works if I specify a path.
For example http://domain/path.
Without path (http://domain) it still does not work.

Im using NPM version 2.6.2

@giomf commented on GitHub (Nov 11, 2020): Got the same problem over here. Actually the forwarding works if I specify a path. For example http://domain/path. Without path (http://domain) it still does not work. Im using NPM version 2.6.2

kerem commented

2026-02-26 06:31:01 +03:00

Author

Owner

@giomf commented on GitHub (Nov 11, 2020):

Ok wait. After restarting the Browser everything work fine now.

@giomf commented on GitHub (Nov 11, 2020): Ok wait. After restarting the Browser everything work fine now.

kerem commented

2026-02-26 06:31:02 +03:00

Author

Owner

@chris1668 commented on GitHub (Nov 11, 2020):

Yes that was my other problem, Firefox's web cache did not play nice with
the upgrade and once I cleared it the rest of Web Interface would load.

On Wed, Nov 11, 2020 at 10:34 AM Guillaume Fournier <
notifications@github.com> wrote:

Ok wait. After restarting the Browser everything work fine now.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jc21/nginx-proxy-manager/issues/184#issuecomment-725589656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2OJUCCEIBMTVV7ZGKIH5LSPLKJ5ANCNFSM4IJ7XGOA
.

@chris1668 commented on GitHub (Nov 11, 2020): Yes that was my other problem, Firefox's web cache did not play nice with the upgrade and once I cleared it the rest of Web Interface would load. On Wed, Nov 11, 2020 at 10:34 AM Guillaume Fournier < notifications@github.com> wrote: > Ok wait. After restarting the Browser everything work fine now. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/jc21/nginx-proxy-manager/issues/184#issuecomment-725589656>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA2OJUCCEIBMTVV7ZGKIH5LSPLKJ5ANCNFSM4IJ7XGOA> > . >

kerem commented

2026-02-26 06:31:02 +03:00

Author

Owner

@papatistos commented on GitHub (Dec 30, 2020):

I am also having this issue on NPM 2.3.1

My settings:

But I can still consistently and on different browsers connect via http. It does not enforce https.

@papatistos commented on GitHub (Dec 30, 2020): I am also having this issue on NPM 2.3.1 My settings: ![image](https://user-images.githubusercontent.com/3662750/103365015-65ad5780-4abf-11eb-8d05-a0720cd3b6b3.png) But I can still consistently and on different browsers connect via http. It does not enforce https.

kerem commented

2026-02-26 06:31:02 +03:00

Author

Owner

@beefycheddar commented on GitHub (Jan 7, 2021):

I am experiencing this on 2.7.1. Https is not enforced even with the switch enabled.

@beefycheddar commented on GitHub (Jan 7, 2021): I am experiencing this on 2.7.1. Https is not enforced even with the switch enabled.

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@dnv commented on GitHub (Jan 26, 2021):

Having the same issue on v2.7.3, Force SSL doesn't actually enforce a redirect. Reset your entire browser cache/cookies/etc and try accessing via http directly, it will work even though it shouldn't. If you browser is aware of the https also working it can redirect you without asking (at least Chrome seemingly does), but it's the browser doing the redirect, not NPM. Can be confirmed by resetting the browser.

@dnv commented on GitHub (Jan 26, 2021): Having the same issue on v2.7.3, Force SSL doesn't actually enforce a redirect. Reset your entire browser cache/cookies/etc and try accessing via http directly, it will work even though it shouldn't. If you browser is aware of the https also working it can redirect you without asking (at least Chrome seemingly does), but it's the browser doing the redirect, not NPM. Can be confirmed by resetting the browser.

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@ma-karai commented on GitHub (Feb 4, 2021):

is there an update or workaround on this ?

@ma-karai commented on GitHub (Feb 4, 2021): is there an update or workaround on this ?

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@dnv commented on GitHub (Feb 4, 2021):

is there an update or workaround on this ?

My workaround was migrating to Caddy.

@dnv commented on GitHub (Feb 4, 2021): > is there an update or workaround on this ? My workaround was migrating to Caddy.

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@ma-karai commented on GitHub (Feb 14, 2021):

ok

@ma-karai commented on GitHub (Feb 14, 2021): ok

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@chaptergy commented on GitHub (May 12, 2021):

@chaptergy commented on GitHub (May 12, 2021): Possibly related: https://github.com/jc21/nginx-proxy-manager/issues/516

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@ma-karai commented on GitHub (Nov 16, 2021):

is this fixed ?

@ma-karai commented on GitHub (Nov 16, 2021): is this fixed ?

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@oaeide commented on GitHub (Jan 17, 2022):

Seems this is still an issue. Opened 07.aug 2019...what?

@oaeide commented on GitHub (Jan 17, 2022): Seems this is still an issue. Opened 07.aug 2019...what?

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@zierbeek commented on GitHub (Mar 4, 2022):

still an issue;...

@zierbeek commented on GitHub (Mar 4, 2022): still an issue;...

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@zierbeek commented on GitHub (Mar 20, 2022):

is the team still on active development even?

@zierbeek commented on GitHub (Mar 20, 2022): is the team still on active development even?

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@jackblk commented on GitHub (Mar 23, 2022):

Still not fixed, but can be circumvent:

Create a new proxy host/redirection
Edit the proxy: enable Force SSL
Clear browser cache/data (or just open an incognito/private session)

It should be redirected to HTTPS now.

I think this is the same issue with https://github.com/NginxProxyManager/nginx-proxy-manager/issues/516

@jackblk commented on GitHub (Mar 23, 2022): Still not fixed, but can be circumvent: * Create a new proxy host/redirection * Edit the proxy: enable Force SSL * Clear browser cache/data (or just open an incognito/private session) It should be redirected to HTTPS now. I think this is the same issue with https://github.com/NginxProxyManager/nginx-proxy-manager/issues/516

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@Eliam077 commented on GitHub (May 9, 2023):

is there any news in 2023 ?

i still have the same issue :(
will have to disable Port 80

@Eliam077 commented on GitHub (May 9, 2023): is there any news in 2023 ? i still have the same issue :( will have to disable Port 80

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@realies commented on GitHub (Dec 3, 2023):

This is still happening.

@realies commented on GitHub (Dec 3, 2023): This is still happening.

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 13, 2024):

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

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

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@realies commented on GitHub (Jul 13, 2024):

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

brah.

@realies commented on GitHub (Jul 13, 2024): > Issue is now considered stale. If you want to keep it open, please comment :+1: brah.

kerem commented

2026-02-26 06:31:03 +03:00

Author

Owner

@studio-outsider commented on GitHub (Apr 5, 2025):

Still an issue

@studio-outsider commented on GitHub (Apr 5, 2025): Still an issue

kerem commented

2026-02-26 06:31:04 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 17, 2025):

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

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

kerem commented

2026-02-26 06:31:04 +03:00

Author

Owner

@Visualflea commented on GitHub (Oct 17, 2025):

I'm seeing this issue

@Visualflea commented on GitHub (Oct 17, 2025): I'm seeing this issue

kerem commented

2026-02-26 06:31:04 +03:00

Author

Owner

@delta0815 commented on GitHub (Nov 12, 2025):

Same issue here

@delta0815 commented on GitHub (Nov 12, 2025): Same issue here

Rows
Columns

[GH-ISSUE #184] SSL settings are not applied #161