Nginx – Redirect http subdomain to https

httphttpsnginxredirectsubdomain

I'm trying to redirect all requests from http://blog.example.org to https://blog.example.org.

Unfortunately I receive this error:

400 Bad Request The plain HTTP request was sent to HTTPS port

My config:

server {
    listen      80;
    server_name blog.example.org;
    return 301 https://$host$request_uri$is_args$args;
}


server {
    server_name blog.example.org;
    listen 443 ssl http2;

    root /srv/www/wordpress;
    index index.php index.html index.htm;

Best Answer

Your return statement is incorrect. You should have:

return 301 https://$server_name$request_uri;

Correct way in new versions of nginx

Turn out my first answer to this question was correct at certain time, but it turned into another pitfall - to stay up to date please check Taxing rewrite pitfalls

I have been corrected by many SE users, so the credit goes to them, but more importantly, here is the correct code:

server {
       listen         80;
       server_name    my.domain.com;
       return         301 https://$server_name$request_uri;
}

server {
       listen         443 ssl;
       server_name    my.domain.com;
       # add Strict-Transport-Security to prevent man in the middle attacks
       add_header Strict-Transport-Security "max-age=31536000" always; 

       [....]
}

Nginx – Why WordPress Loads Blank Pages on Nginx and PHP-FPM

By default the Nginx source does not define SCRIPT_FILENAME in the fastcgi_params file, so unless the repo you installed Nginx from does that you need to do it yourself.

Check if the following line is in your fastcgi_params file:

fastcgi_param  SCRIPT_FILENAME    $document_root$fastcgi_script_name;

and if not then add it.

Best Answer

Related Solutions

NGINX Redirect – How to Rewrite All HTTP Requests to HTTPS While Maintaining Sub-Domain

Correct way in new versions of nginx

Nginx – Why WordPress Loads Blank Pages on Nginx and PHP-FPM

Related Topic