We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Nginx fails to restart after enabling SSL Support; Site goes down
Nginx fails to restart after enabling SSL Support; Site goes down
After Enabling SSL Support and entering required keys, and then hitting Save, the settings get saved but the site goes down and nginx fails to restart.
Nginx error log gives the following:
BUT if I reboot the server, Nginx starts up and I can access the site with both 'http' and with 'https' but I get 500 Internal Server on the page and 502 Bad Gateway in browser console. This error goes away if I disable the SSL support from VestaCP panel and reboot the server.
For your consideration:
nginx version: nginx/1.10.2
vesta - core package Version:0.9.8 (amd64) Release:16
Nginx error log gives the following:
Code: Select all
2016/11/02 18:59:29 [emerg] 8687#8687: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:29 [emerg] 8687#8687: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:29 [emerg] 8687#8687: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:29 [emerg] 8687#8687: still could not bind()
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: bind() to 104.131.90.2:443 failed (98: Address already in use)
2016/11/02 18:59:54 [emerg] 8922#8922: still could not bind()
For your consideration:
nginx version: nginx/1.10.2
vesta - core package Version:0.9.8 (amd64) Release:16
Re: Nginx fails to restart after enabling SSL Support; Site goes down
After rebooting the server, when it gives 500 Internal Server error, netstat -tuapen | grep 443 gives:
It looks nginx itself is listening to the port. What could be causing 502? I had done clean Nginx + Apache install and haven't messed up with any nginx or apache configuration.
Code: Select all
tcp 0 0 104.131.90.2:443 0.0.0.0:* LISTEN 0 22290 4453/nginx.conf
Re: Nginx fails to restart after enabling SSL Support; Site goes down
What do you think about?
-
- Posts: 11
- Joined: Thu Dec 15, 2016 2:54 pm
Re: Nginx fails to restart after enabling SSL Support; Site goes down
Same error! You found solution?
Re: Nginx fails to restart after enabling SSL Support; Site goes down
Can you post all your nginx confs?
/home/*/conf/web/nginx.conf
/home/*/conf/web/snginx.conf
/home/*/conf/web/nginx.*.conf_letsencrypt
/home/*/conf/web/nginx.conf
/home/*/conf/web/snginx.conf
/home/*/conf/web/nginx.*.conf_letsencrypt
Re: Nginx fails to restart after enabling SSL Support; Site goes down
I did a fresh install and it worked. Perhaps letsencrypt messed up some config.