It appears it had nothing to do with the includes but what I had in my server blocks. If I put a particular https server include above another it broke one. I made 1 of the https server blocks as the default.
From: nginx [mailto:nginx-boun...@nginx.org] On Behalf Of Cox, Eric S Sent: Tuesday, February 14, 2017 3:08 PM To: nginx@nginx.org Subject: Including Multiple Server Blocks via wildcard In my main nginx.conf file I am doing an include for various files to include multiple server blocks (1 block per file).... If I use a wildcard include the https servers break but the http server is fine.... Example.... include /servers/*; this would include 3 server blocks 1 http 2 https If I include each file specifically the servers work fine (including both https server blocks) ANY IDEA WHY THIS WOULD BE? The server starts up fine but I just can't connect to the HTTPS endpoints (timeout) .... Example include /servers/server1; include /servers/server2; include /servers/server3; Each server file contains a while server block.... Example..... server { listen 443 ssl backlog=2048; server_name server1.domain.com; ssl_certificate /test.crt; ssl_certificate_key /test.key; ssl_session_cache shared:SSL:1m; ssl_session_timeout 5m; ssl_protocols TLSv1.2; location / { root /html; } include /locations/*_conf; status_zone https_server1; } Thanks, Eric ________________________________ This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ________________________________ This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
