Regression in Behavior with Fix #2186 Affecting SSL Connections about nginx-proxy HOT 9 CLOSED

I forgot to mention that you'll probably need to configure DEFAULT_HOST on the proxy too, so that request without a hostname are correctly routed to the VIRTUAL_HOST / container of your choice.

from nginx-proxy.

@buchdag From what I understand from your comment, the behavior in version 1.2.0 was a bug?

Yep. This was working without additional config because the proxy :

• was redirecting to containers in cases where it shouldn't (no host header or unknown host).
• was serving incorrect certificates instead of rejecting HTTPS connection when no corresponding certificates existed

from nginx-proxy.

I forgot to mention that you'll probably need to configure DEFAULT_HOST on the proxy too, so that request without a hostname are correctly routed to the VIRTUAL_HOST / container of your choice.

@buchdag Thank you, I understand better now. Actually, by adding the DEFAULT_HOST, it works perfectly, and there's no need to add the default.crt/key.

from nginx-proxy.

Related comment: #2186 (comment)

from nginx-proxy.

Hi.

Could you detail what's mounted to /etc/nginx/certs ?

Have you tried creating a default certificate / key pair ? (default.crt and default.key in /etc/nginx/certs).

from nginx-proxy.

@buchdag Thanks for pointing it.

Below the content of the mounted certificates

root@cb2e399bcfb0:/app# ls -lah /etc/nginx/certs/
total 28K
drwxrwxr-x 2 1001 1001 4.0K Dec 20 19:24 .
drwxr-xr-x 1 root root 4.0K Dec 20 19:25 ..
-rw-rw-r-- 1 1001 1001 1.4K Dec 20 16:35 example.com.test.crt
-rw------- 1 1001 1001 1.7K Dec 20 16:35 example.com.test.key

Have you tried creating a default certificate / key pair ? (default.crt and default.key in /etc/nginx/certs).

if I try to create default certificates:

root@cb2e399bcfb0:/app# ls -lah /etc/nginx/certs/
total 28K
drwxrwxr-x 2 1001 1001 4.0K Dec 20 19:24 .
drwxr-xr-x 1 root root 4.0K Dec 20 19:25 ..
-rw-rw-r-- 1 1001 1001 1.3K Dec 20 19:24 default.crt
-rw------- 1 1001 1001 1.7K Dec 20 19:24 default.key
-rw-rw-r-- 1 1001 1001 1.4K Dec 20 16:35 example.com.test.crt
-rw------- 1 1001 1001 1.7K Dec 20 16:35 example.com.test.key

I met the 503 nginx error.

Logs

nginx-proxy  | nginx.1     | localhost 192.168.16.1 - - [20/Dec/2023:19:29:56 +0000] "GET / HTTP/2.0" 503 592 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36" "-"

from nginx-proxy.

@buchdag From what I understand from your comment, the behavior in version 1.2.0 was a bug?

from nginx-proxy.

Glad to hear it now works for you. Could you close this issue if you consider it solved ?

from nginx-proxy.

Works perfectly! Thanks !

from nginx-proxy.