Unable to establish SSL connection #553
Comments
|
Anyone? |
|
Hi. Could you share |
|
Thank for reply, @buchdag |
|
Could you try to reach your subdomains over |
|
@buchdag Nothing. |
|
Could you try removing the config parts that use |
|
@buchdag So I shouldn't expose any ports? |
|
Port 80 is already exposed by By the way |
|
It's okay for me, I wanted to test those containers without nginx-proxy. |
|
I think that the issue is probably more with |
|
@buchdag, removed exposed ports and VIRTUAL_PORT from clients. So client config is: docker-compose logs: |
|
And does it work now, can you access |
|
@buchdag Unfortunately no |
|
Is it okay? |
|
Nope, it means that Could you dump the content of |
|
Cannot reproduce docker-compose logs
|
|
/etc/nginx/conf.d/default.config # If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
# scheme used to connect to this server
map $http_x_forwarded_proto $proxy_x_forwarded_proto {
default $http_x_forwarded_proto;
'' $scheme;
}
# If we receive X-Forwarded-Port, pass it through; otherwise, pass along the
# server port the client connected to
map $http_x_forwarded_port $proxy_x_forwarded_port {
default $http_x_forwarded_port;
'' $server_port;
}
# If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any
# Connection header that may have been passed to this server
map $http_upgrade $proxy_connection {
default upgrade;
'' close;
}
# Apply fix for very long server names
server_names_hash_bucket_size 128;
# Default dhparam
ssl_dhparam /etc/nginx/dhparam/dhparam.pem;
# Set appropriate X-Forwarded-Ssl header
map $scheme $proxy_x_forwarded_ssl {
default off;
https on;
}
gzip_types text/plain text/css application/javascript application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
log_format vhost '$host $remote_addr - $remote_user [$time_local] '
'"$request" $status $body_bytes_sent '
'"$http_referer" "$http_user_agent"';
access_log off;
resolver 127.0.0.11;
# HTTP 1.1 support
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $proxy_connection;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Ssl $proxy_x_forwarded_ssl;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
# Mitigate httpoxy attack (see README for details)
proxy_set_header Proxy "";
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
listen 80;
access_log /var/log/nginx/access.log vhost;
return 503;
}
server {
server_name _; # This is just an invalid value which will never trigger on a real hostname.
listen 443 ssl http2;
access_log /var/log/nginx/access.log vhost;
return 503;
ssl_session_tickets off;
ssl_certificate /etc/nginx/certs/default.crt;
ssl_certificate_key /etc/nginx/certs/default.key;
}
# test1.mywebsite.com
upstream test1.mywebsite.com {
## Can be connected with "nginx-proxy" network
# test1_nginx_1
server 172.26.0.2:80;
}
server {
server_name test1.mywebsite.com;
listen 80 ;
access_log /var/log/nginx/access.log vhost;
return 301 https://$host$request_uri;
}
server {
server_name test1.mywebsite.com;
listen 443 ssl http2 ;
access_log /var/log/nginx/access.log vhost;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:!DSS';
ssl_prefer_server_ciphers on;
ssl_session_timeout 5m;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
ssl_certificate /etc/nginx/certs/test1.mywebsite.com.crt;
ssl_certificate_key /etc/nginx/certs/test1.mywebsite.com.key;
ssl_dhparam /etc/nginx/certs/test1.mywebsite.com.dhparam.pem;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/nginx/certs/test1.mywebsite.com.chain.pem;
add_header Strict-Transport-Security "max-age=31536000" always;
include /etc/nginx/vhost.d/default;
location / {
proxy_pass http://test1.mywebsite.com;
}
} |
|
Seems to me that Are you certain your host's port Can you curl |
|
Oh! Works. There was a classic nginx with a Lets Encrypt and there were no problems, so I didn’t even think to look there. |
|
@indapublic can I close the issue ? |
|
Sure. Closing |
|
Just investigated that website is not opened while Cloudflare switcher is turn off.
After turning on all works. |
Hi! I need help.
I have staging with 3 subdomains. Each domain have this configuration:
All domains is working well, opened on each port.
Nginx proxy configuration:
Nginx proxy logs:
Seems ok for me, isn’t it?
But SSL is not working.
nginx-proxy only is working ok
The text was updated successfully, but these errors were encountered: