Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
Anytime new configuration changes are made or added, you’ll need to restart or reload NGINX.
service nginx restart
or
service nginx reload
As a general note, the ipv6only=on directive can be removed from both of the server blocks – it’s on by default :-). When you restart NGINX, it will most likely fail if both have it set.
Beyond that one change, everything else looks okay and should work as expected the symlink isn’t working and showing up in sites-enabled.
You can also test configuration using:
nginx -t
…
https://nginx.org/en/docs/http/ngx_http_core_module.html
“this parameter (0.7.42) determines (via the IPV6_V6ONLY socket option) whether an IPv6 socket listening on a wildcard address [::] will accept only IPv6 connections or both IPv6 and IPv4 connections. This parameter is turned on by default. It can only be set once on start.”
I have same issue with a primary and sub-domain. Sub-domain always loads the main domain’s content. Static html file loads (index.html) correctly - the problem is with fastcgi configuration. Any more suggestions on fastcgi conf?