HTTP to HTTPS Nginx/Forge

Enjoy: https://bashy.im/blog/nginx-redirect-to-https-with-without-www-subdomain

So could I get away with putting this

listen 80;
        listen [::]:80;

        server_name www.example.com example.com;

        return 301 https://example.com$request_uri;

at the top on my block?

You need different server blocks to listen on different server_names without using the evil "if".

Put each of them above each other as it states in the blog post. I just have mine after each other in the same file.

So just adding this to the top won't work then?

listen 80;
    listen [::]:80;
    listen 443 ssl;

    server_name www.crm.domain.com crm.domain.com;
    root /home/forge/crm.domain.com/public;

    return 301 https://crm.domain.com$request_uri;

It will if you do this in the same file

server {
    listen 80;
    listen [::]:80; // probably don't need this if you don't want to listen on IPv6

    server_name www.crm.domain.com crm.domain.com;

    return 301 https://crm.domain.com$request_uri;
}

server {
    listen 443 ssl;

    # FORGE SSL (DO NOT REMOVE!)
    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_certificate /etc/nginx/ssl/crm.domain.com/7947/server.crt;
    ssl_certificate_key /etc/nginx/ssl/crm.domain.com/7947/server.key;

    server_name www.crm.domain.com;

    return 301 https://crm.domain.com$request_uri;
}

server {
    // original server block
}

Like it is in my post but I've just done it for you... :) https://bashy.im/blog/nginx-redirect-to-https-with-without-www-subdomain

Great stuff now I get it, cheers Ben ( @bashy ) needed to see it for my example to understand it, don't ask me why but that's how I tend to learn, kinda like the JS/Ajax stuff you helped with the other day, got that now actually wrote my own today, so was quite impressed with myself.

@bashy so for each application on my server I can specify the above configurations and i should not get any issues such as any SSL conflict issues ( not sure even if I am saying this right! ), right? [Edited] While I see this approach works great, and maintainable, when I manage my own servers, sometimes I am obligated to use third party shared hosting servers :( but this raise a question, is there any benefit from handling HTTP traffic from nginx config files VS .htaccess?

@lstables That's fine, glad you're learning from all this!

@em57 Well this is a very good way of doing the redirects, it requires you to have access to the virtualhost file for the Nginx site though. Since Nginx doesn't read any sort of file like Apache (.htaccess) before it loads the page, you have to do it in the server block(s). Unless someone else knows of a way.

Nginx is really for the advanced users, if you don't require the features of it just use Apache, it's just as good at processing requests and passing it onto PHP.