Resolved Nginx does not start anymore

[Aragato]

Hello,

I am running the latest Plesk on the latest stable Debian. After one of my sites experienced a 504 Nginx Gateway Error I followed the official Plesk resolution advice on the following site:
https://kb.plesk.com/en/120210

I edited the nginx.conf as stated.
At the end it says: Restart 'php-fpm', 'apache' and 'nginx' services.

I restarted php-fpm, worked
restarted apache, worked
tried to restart nginx, took very long and I already knew something did not work out. It did not come back. Restarted Server etc. But still it does not start.

I get the following results:
# service nginx restart
Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalctl -xn' for details.

# systemctl status nginx.service
nginx.service - Startup script for nginx service
Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
Active: failed (Result: exit-code) since Fri 2016-06-17 16:33:21 CEST; 10s ago
Process: 4094 ExecStart=/usr/sbin/nginx (code=exited, status=1/FAILURE)
Process: 4091 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=0/SUCCESS)
Process: 4087 ExecStartPre=/usr/bin/test $NGINX_ENABLED = yes (code=exited, status=0/SUCCESS)

Jun 17 16:33:18 p1.aragato-server.net nginx[4094]: nginx: [warn] conflicting server name "ipv6.yaadomm.com" on [::]:443, ignored
Jun 17 16:33:18 p1.aragato-server.net nginx[4094]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:33:19 p1.aragato-server.net nginx[4094]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:33:19 p1.aragato-server.net nginx[4094]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:33:20 p1.aragato-server.net nginx[4094]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:33:20 p1.aragato-server.net nginx[4094]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:33:21 p1.aragato-server.net nginx[4094]: nginx: [emerg] still could not bind()
Jun 17 16:33:21 p1.aragato-server.net systemd[1]: nginx.service: control process exited, code=exited status=1
Jun 17 16:33:21 p1.aragato-server.net systemd[1]: Failed to start Startup script for nginx service.

# journalctl -xn
-- Logs begin at Fri 2016-06-17 16:24:59 CEST, end at Fri 2016-06-17 16:34:29 CEST. --
Jun 17 16:34:27 p1.aragato-server.net nginx[5431]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:34:27 p1.aragato-server.net nginx[5431]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:34:28 p1.aragato-server.net nginx[5431]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:34:28 p1.aragato-server.net nginx[5431]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:34:29 p1.aragato-server.net nginx[5431]: nginx: [emerg] bind() to [::]:443 failed (98: Address already in use)
Jun 17 16:34:29 p1.aragato-server.net nginx[5431]: nginx: [emerg] still could not bind()
Jun 17 16:34:29 p1.aragato-server.net systemd[1]: nginx.service: control process exited, code=exited status=1
Jun 17 16:34:29 p1.aragato-server.net systemd[1]: Failed to start Startup script for nginx service.
-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has failed.
--
-- The result is failed.
Jun 17 16:34:29 p1.aragato-server.net systemd[1]: Unit nginx.service entered failed state.
Jun 17 16:34:29 p1.aragato-server.net sshd[5432]: Connection closed by 89.40.112.123 [preauth]




Please help! This is urgent! I have no clue what the problem is. It is critical and if there is an experienced linux/nginx/plesk admin who can help I will of course pay a service charge.

 

[UFHH01]

Hi Aragato,

pls. use the "Plesk Repair Utility ( Plesk 12.5 online documentation )" first, as for example:

plesk repair web​

Afterwards, pls. make sure that when you restart nginx, port 443 is not already used by another process ( orphaned nginx processes can be as well killed with the command "kill -9 XXXX", where XXXX is the process number, which you may list with "ps aux | grep nginx" )