So, sounds like it might be a few different problems, that may or may not be related. Just a heads up, V3 is going to be officially unsupported soon so might want to look into upgrading to V4 at some point.
If you make any change whatsoever to the NGiNX config file, you need to restart NGiNX for it to work using
nginx -t && service nginx reload (also, make sure you
chmod 600 both the certificate and key file, in case you haven’t.)
For the SPDY issue, it could be anything really, but usually it’s somewhere between browser configuration and DNS. If you renew your IP and flush your DNS and get no luck, you can also flush the SPDY sockets in Chrome by navigating to
chrome://net-internals/#sockets and hitting the Flush Socket Pools button.
All certificate authorities issue SSL certs for a domain, or “common name”, not an IP Address (with a specific exception). So the default virtual host and Welcome page will show over HTTP okay but will not respond over HTTPS since technically no SSL has been configured for NGiNX’s default page (shown as the server’s IP). Even so, only a self-signed certificate will enable HTTPS traffic to an IP address over public DNS, and that’s usually used for higher ports (such as admin panels and so on).
Your IP will still resolve to the NGiNX default page over regular HTTP but request headers sent with the domain name will resolve over HTTPS. This is normal.
I can’t be sure from your question but it seems your problem can be narrowed down by:
- undoing any manual configuration changes to NGiNX that EE generated
- checking your
hosts file and making sure there’s no redundancy (so you can resolve SSL over public DNS)
- flushing your DNS cache
You can also let us know if you used Let’s Encrypt or a Custom SSL certificate.