SSL Issues with Force www

Posted at centminmod.com/nginx_domain_dns_setup.html#httpsredirect

key to testing is using 302 temp redirect first in a private incognito browser session otherwise the problems you can experience may end up being due to browser caching or 301 permanent redirects unless you clear browser cache and reboot local computer(s) and even then some web browsers don't let go of 301 permanent redirect browser cache that willingly

You have it wrong way round those configs are telling to redirect non-www to www
just change in http port 80 non-ssl vhost conf file

from

Code (Text):

server_name anomaly.ws;
return 302 $scheme://www.anomaly.ws$request_uri;

to

Code (Text):

server_name anomaly.ws www.anomaly.ws;
return 302 https://anomaly.ws$request_uri;

and in https port 443 ssl vhost conf change to

Code (Text):

server {
listen 443 ssl http2;
server_name anomaly.ws;

 

ah yes non-ssl nginx vhost would need disabling as per Nginx Vhost & NSD DNS Setup - CentminMod.com LEMP Nginx web stack for CentOS