Cannot configure HTTPS for www subdomain using nginx server blocks
I want to stop this from happening
https://www.site.com/articles/abc
This should be redirected (to remove www) as in my server block configuration. I don't understand why however. I have looked a lot at similar solutions on server fault and wonder if there is something more specific for DO.
here is the config thank you for help.
server {
listen 80;
listen [::]:80;
servername site.com www.site.com;
return 301 https://$servername$request_uri;
}
server {
listen 443 ssl;
listen [::]:443 ssl http2;
include snippets/ssl-site.com.conf;
include snippets/ssl-params.conf;
root /var/www/site.com/html;
index index.html index.htm index.nginx-debian.html index.php;
server_name site.com www.site.com;
#rewrite ^ https://site.com$request_uri? permanent;
#return 301 https://$server_name$request_uri;
add_header X-Frame-Options "SAMEORIGIN";
rewrite ^(.*)/(\d+)-([^/]+)(.*)$ $1/$3 permanent;
rewrite ^.*\.(pptx)$ https://caribbean-diving.com permanent;
location ~* \.(?:css|js|gif|jpeg|jpg|png)$ {
expires max;
add_header Cache-Control public;
}
error_page 404 /404.html;
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html;
}
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/run/php/php7.0-fpm.sock;
}
location / {
try_files $uri $uri/ /index.php?$args;
}
location ~ /.well-known {
allow all;
}
}
Ok looks like I was only doing a cert for the non www not www...and perhaps the order of things happening meant that even if the www variant was not redirecting because the www was not properly certified..so I re ran that
So now I can see I get a padlock for the www version as well. However the redirection still has issues- ie doesn't actually redirect. So there is an seo problem rather than a nasty SSL problem but I want to solve the reason why the www is not redirected properly.
I have another domain that is working sweet and the config looks identical so it is confusing.
Edit that other domain was using .htaccess to redirect!
So have now fixed them both with a separate server block to catch https://www variants..