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.
[SOLVED] Apache and then Nginx won't start after issuing Let's Encrypt certificate
[SOLVED] Apache and then Nginx won't start after issuing Let's Encrypt certificate
After I issue a Let's Encrypt certificate (for any of my domains) then the apache won't start. At first when I typed in cli the problem was I killed the process occupying the sock (for some reason it was nginx) but then again I couldn't start apache.
Now (after killing nginx) I get the following error
I tried everything, from reissuing the certificates to killing the processes one by one. Nothing worked until now.
If I kill apache now I can reload/restart it but then I get the following error when I try to reload nginx.
Code: Select all
systemctl status apache2.service
Code: Select all
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
Now (after killing nginx) I get the following error
Code: Select all
apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2)
Active: active (exited) (Result: exit-code) since Tue 2015-12-15 20:09:49 EET; 22min ago
Process: 3545 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
Process: 8299 ExecReload=/etc/init.d/apache2 reload (code=exited, status=1/FAILURE)
Process: 3555 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)
Dec 15 20:24:15 my-domain apache2[5039]: Reloading web server: apache2.
Dec 15 20:24:15 my-domain systemd[1]: Reloaded LSB: Apache2 web server.
Dec 15 20:31:47 my-domain systemd[1]: Started LSB: Apache2 web server.
Dec 15 20:31:51 my-domain systemd[1]: Started LSB: Apache2 web server.
Dec 15 20:32:12 my-domain systemd[1]: Started LSB: Apache2 web server.
Dec 15 20:32:14 my-domain systemd[1]: Reloading LSB: Apache2 web server.
Dec 15 20:32:14 my-domain apache2[8299]: Reloading web server: apache2 failed!
Dec 15 20:32:14 my-domain apache2[8299]: Apache2 is not running ... (warning).
Dec 15 20:32:14 my-domain systemd[1]: apache2.service: control process exited, code=exited status=1
Dec 15 20:32:14 my-domain systemd[1]: Reload failed for LSB: Apache2 web server.
If I kill apache now I can reload/restart it but then I get the following error when I try to reload nginx.
Code: Select all
nginx.service - LSB: Stop/start nginx
Loaded: loaded (/etc/init.d/nginx)
Active: failed (Result: exit-code) since Thu 2015-12-17 22:22:32 EET; 53s ago
Process: 17152 ExecStop=/etc/init.d/nginx stop (code=exited, status=0/SUCCESS)
Process: 16689 ExecReload=/etc/init.d/nginx reload (code=exited, status=0/SUCCESS)
Process: 17191 ExecStart=/etc/init.d/nginx start (code=exited, status=1/FAILURE)
Dec 17 22:22:30 my-domain nginx[17191]: nginx: [emerg] bind() to MY-IP-GOES-HERE failed (98: Address already in use)
Dec 17 22:22:30 my-domain nginx[17191]: nginx: [emerg] bind() to MY-IP-GOES-HERE failed (98: Address already in use)
Dec 17 22:22:31 my-domain nginx[17191]: nginx: [emerg] bind() to MY-IP-GOES-HERE failed (98: Address already in use)
Dec 17 22:22:31 my-domain nginx[17191]: nginx: [emerg] bind() to MY-IP-GOES-HERE failed (98: Address already in use)
Dec 17 22:22:32 my-domain nginx[17191]: nginx: [emerg] bind() to MY-IP-GOES-HERE failed (98: Address already in use)
Dec 17 22:22:32 my-domain nginx[17191]: nginx: [emerg] still could not bind()
Dec 17 22:22:32 my-domain systemd[1]: nginx.service: control process exited, code=exited status=1
Dec 17 22:22:32 my-domain systemd[1]: Failed to start LSB: Stop/start nginx.
Dec 17 22:22:33 my-domain systemd[1]: Unit nginx.service entered failed state.
Dec 17 22:23:18 my-domain systemd[1]: Unit nginx.service cannot be reloaded because it is inactive.
Re: [SOLVED] Apache and then Nginx won't start after issuing Let's Encrypt certificate
The issue appears to be due to a broken Let's Encrypt installation. After some experimenting I did clean and successfully install of apache2 + vesta + let's encrypt and everything worked as designed.