Settings up SSL and non SSL Nginx sites to play nice together

Posted on by

I learned the hard way recently the importance of setting additional Nginx server configurations when hosting both SSL and Non-SSL sites on the same machine.

When I created a new server with an SSL connection and did not set a connection reset for the other sites that were not using SSL I found Google and other search engines were showing the wrong URL in my search results.

It took almost two weeks for the fix to propagate to all the search engines after I fixed it so don’t make the same mistake I did.

Make sure to create Nginx servers for HTTPS and HTTP for each website the machine will be hosting.

I made sure that the default configuration (IP without the domain or unknown server name would just reset the connection and not try to load another site. I also made sure that I forced SSL on sites that had it by redirecting users if they weren’t using SSL.

On sites that don’t use SSL I made a server running on SSL with the correct name that would reset the connection. I could possibly redirect the user back to an HTTP connection, but I don’t think it is necessary and have not tried it myself to make sure that it works.

HTTP Server IP connection reset (444)
HTTPS Server IP connection reset (444) redirection to https example


server {
     listen 80 default;
     return 444;

server { listen 443 default; ssl on; ssl_certificate /etc/ssl/certs/ssl-cert-snakeoil.pem; ssl_certificate_key /etc/ssl/private/ssl-cert-snakeoil.key; return 444; }


server {
    listen  80;
    rewrite ^$request_uri?;

server { listen 443; server_name; ssl on; ssl_certificate /etc/ssl/certs/ssl-cert-snakeoil.pem; ssl_certificate_key /etc/ssl/private/ssl-cert-snakeoil.key; keepalive_timeout 60;

location / {
        proxy_set_header        Host    $host;
        proxy_set_header        X-Real-IP      $remote_addr;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;