SSL settings are not applied

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

[dnv]

is there an update or workaround on this ?

My workaround was migrating to Caddy.

[jackblk]

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