) #646

New issue

Closed

opened 2026-02-26 06:33:49 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @CorneliousJD on GitHub (Dec 7, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/762

Hey guys, so I first want to apolgozie if this is not the right place to ask this, but my current understanding of the advanced tab on proxy host is to add things into the location / {} area.

I have Home Assistant running and I need to change some SSL settings to allow a Samsung SmartThings integration to work. I had this working via LSIO's "SWAG/LetsEncrypt" container with the following config, but when I try to add the pertenenat info in the advanced section on NPM I get "Internal Error"

#HOMEASSISTANT
server {
server_name home.DOMAIN.com;
listen 443 ssl http2;
proxy_buffering off;
#SSL Settings for Samsung SmartThings Integration
	ssl_certificate /config/keys/letsencrypt/fullchain.pem;
	ssl_certificate_key /config/keys/letsencrypt/privkey.pem;
	ssl_dhparam /config/nginx/dhparams.pem;
	ssl_protocols TLSv1.2;
	ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
	ssl_prefer_server_ciphers on;
	ssl_ecdh_curve secp384r1;
	ssl_session_timeout  10m;
	ssl_session_cache shared:SSL:10m;
	ssl_session_tickets off;
location / {
proxy_pass http://X.X.X.X:8123;
proxy_set_header Host $host;
proxy_redirect http:// https://;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}  
}

What I try to add when I get an error in NPM is

#SSL Settings for Samsung SmartThings Integration
	ssl_protocols TLSv1.2;
	ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
	ssl_prefer_server_ciphers on;
	ssl_ecdh_curve secp384r1;
	ssl_session_timeout  10m;
	ssl_session_cache shared:SSL:10m;
	ssl_session_tickets off;

Thanks in advance!

Originally created by @CorneliousJD on GitHub (Dec 7, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/762 Hey guys, so I first want to apolgozie if this is not the right place to ask this, but my current understanding of the advanced tab on proxy host is to add things into the location / {} area. I have Home Assistant running and I need to change some SSL settings to allow a Samsung SmartThings integration to work. I had this working via LSIO's "SWAG/LetsEncrypt" container with the following config, but when I try to add the pertenenat info in the advanced section on NPM I get "Internal Error" ``` #HOMEASSISTANT server { server_name home.DOMAIN.com; listen 443 ssl http2; proxy_buffering off; #SSL Settings for Samsung SmartThings Integration ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_protocols TLSv1.2; ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH'; ssl_prefer_server_ciphers on; ssl_ecdh_curve secp384r1; ssl_session_timeout 10m; ssl_session_cache shared:SSL:10m; ssl_session_tickets off; location / { proxy_pass http://X.X.X.X:8123; proxy_set_header Host $host; proxy_redirect http:// https://; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } ``` What I try to add when I get an error in NPM is ``` #SSL Settings for Samsung SmartThings Integration ssl_protocols TLSv1.2; ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH'; ssl_prefer_server_ciphers on; ssl_ecdh_curve secp384r1; ssl_session_timeout 10m; ssl_session_cache shared:SSL:10m; ssl_session_tickets off; ``` Thanks in advance!

kerem closed this issue

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

kerem commented

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

Author

Owner

@CorneliousJD commented on GitHub (Dec 8, 2020):

I realize that this is probably not actually an issue since everything seems to be in the location / section and not the server itself.

I'll close this out myself for now as I don't really think it's a big deal to me currently and do not want to detract from other features and be that guy with a weird "one-off" that pesters people.

Incase anyone googles and finds this later, if I must get this setup working again in the future I'll just temp fire up a SWAG container and do what I need to do and swap back to NPM :)

jc21 if you see this - thanks for all the hard work that's gone into NPM, it's fantastic.

@CorneliousJD commented on GitHub (Dec 8, 2020): I realize that this is probably not actually an issue since everything seems to be in the location / section and not the server itself. I'll close this out myself for now as I don't really think it's a big deal to me currently and do not want to detract from other features and be that guy with a weird "one-off" that pesters people. Incase anyone googles and finds this later, if I must get this setup working again in the future I'll just temp fire up a SWAG container and do what I need to do and swap back to NPM :) jc21 if you see this - thanks for all the hard work that's gone into NPM, it's fantastic.

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

No description provided.

Rows
Columns