11 comment

1. www redirection should be done by contacting your ISP (GoDaddy, etc.)
   HTTPS redirection can also be done with your provider with a paid SSL certificate or a free one available from https://letsencrypt.org/. The free one is not as secure as the paid one since the paid one uses the payment transaction itself to verify identity.

2. Thank you for the article nixCraft !

3. how to redirect everything:
   – http://www.mydomain.com (http and www)
   – http://mydomain.com (http and non-www)
   – https://www.mydomain.com (https and www)
   To
   https://mydomain.com ? (https and non-www)

   1. Just switch domain names. That is all

      ## redirect http://www.cyberciti.biz to http://cyberciti.biz/
      server {
          listen       80;
          access_log  off;
          error_log   off;
          server_name  www.cyberciti.biz
          return       301 http://cyberciti.biz$request_uri;
      }
      ## Continue below for cyberciti.biz
      server {
          listen       80;
          access_log  off;
          error_log   off;
          server_name  cyberciti.biz;
          ## rest of config below ##
      }
      ## ssl config ##
      server {
              listen 443 ssl http2;
              access_log  off;
              error_log   off;
              server_name www.cyberciti.biz;
              return 301 https://cyberciti.biz$request_uri;
      }
      ## define our https://cyberciti.biz/ ##
      server {
          listen 443 ssl http2;
          access_log  /var/log/nginx/www.cyberciti.biz_access.log;
          error_log  /var/log/nginx/www.cyberciti.biz_error.log;
          ## server name and root
          server_name  cyberciti.biz;
          root        /home/lighttpd/cyberciti.biz/http;
       
          # certs sent to the client in SERVER HELLO are concatenated in ssl_certificate
          ssl_certificate /etc/nginx/ssl/letsencrypt/cyberciti.biz/cyberciti.biz.crt;
          ssl_certificate_key /etc/nginx/ssl/letsencrypt/cyberciti.biz/cyberciti.biz.key;
          ssl_session_timeout 1d;
          ssl_session_cache shared:SSL:50m;
          ssl_session_tickets off;
          # Diffie-Hellman parameter for DHE ciphersuites, recommended 2048 bits
          ssl_dhparam /etc/nginx/ssl/letsencrypt/cyberciti.biz/dhparams.pem;
       
          # intermediate configuration. tweak to your needs.
          ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
          ssl_ciphers 'ECDHE-ECDSA-CHACHA20
          ## rest of config
      

      1. thank you!

4. there is an typo in the first listing:
   you should use biz instead of bibz

   1. Thanks for the heads up!

5. you can reduce this a little, ie for your two port 80 sections, you can use one:

   ## redirect www.cyberciti.biz to https://www.cyberciti.biz/
   server {
       listen      80;
       access_log  off;
       error_log   off;
       server_name www.cyberciti.biz cyberciti.biz;
       return      301 https://www.cyberciti.biz$request_uri;
   }

   But, I might suggest this is even better:

   ## redirect www.cyberciti.biz to https://www.cyberciti.biz/
   server {
       listen      80;
       access_log  off;
       error_log   off;
       server_name www.cyberciti.biz cyberciti.biz;
       location ~ /.well-known/acme-challenge/(.*) {
          allow all ; 
          root /var/nginx/letsencrypt;
      }
      location / {
         return      301 https://www.cyberciti.biz$request_uri;
     }
   }

   This way you get to use the acme challenge for letsencrypt on port 80 without messing around. The final redirect might as well rewrite the servername to “www” as well, there’s nothing gained by using the servername in functionaility or readability.

6. Could you do the config below to redirect http://www.cyberciti.biz and http://cyberciti.biz and https://cyberciti.biz to https://www.cyberciti.biz/

   server { ## this redirects these 2 http://www.cyberciti.biz and http://cyberciti.biz listen 80; server_name www.cyberciti.biz cyberciti.biz; return 301 https://www.cyberciti.biz$request_uri; }   server { ## this redirects this one https://cyberciti.biz listen 443 ssl; server_name www.cyberciti.biz cyberciti.biz; return 301 https://www.cyberciti.biz$request_uri; ## add ssl and the rest of your server config info here }

   server { ## this redirects these 2 http://www.cyberciti.biz and http://cyberciti.biz listen 80; server_name www.cyberciti.biz cyberciti.biz; return 301 https://www.cyberciti.biz$request_uri; } server { ## this redirects this one https://cyberciti.biz listen 443 ssl; server_name www.cyberciti.biz cyberciti.biz; return 301 https://www.cyberciti.biz$request_uri; ## add ssl and the rest of your server config info here }

7. Sorry I for got to do the code tag so it messed up the server_names.

   Could you do the config below to redirect http://www.cyberciti.biz and http://cyberciti.biz and https://cyberciti.biz to https://www.cyberciti.biz/

   server { ## this redirects these 2 http://www.cyberciti.biz and http://cyberciti.biz listen 80; server_name www.cyberciti.biz cyberciti.biz; return 301 https://www.cyberciti.biz$request_uri; }   server { ## this redirects this one https://cyberciti.biz listen 443 ssl; server_name www.cyberciti.biz cyberciti.biz; return 301 https://www.cyberciti.biz$request_uri;   ## add ssl and the rest of your server config info here }

   server { ## this redirects these 2 http://www.cyberciti.biz and http://cyberciti.biz listen 80; server_name www.cyberciti.biz cyberciti.biz; return 301 https://www.cyberciti.biz$request_uri; } server { ## this redirects this one https://cyberciti.biz listen 443 ssl; server_name www.cyberciti.biz cyberciti.biz; return 301 https://www.cyberciti.biz$request_uri; ## add ssl and the rest of your server config info here }

8. Again sorry… that didn’t work… how can I get the code to show in a box like yours does?

    Still, have a question? Get help on our forum!