Article ID: 126734, created on Aug 30, 2015, last review on Jun 17, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux


Nginx service fails to start on CentOS 7 boot.
The following error can be found in /var/log/nginx/error.log:

2015/07/28 01:47:51 [emerg] 941#0: bind() to failed (99: Cannot assign requested address)

Systemctl shows the following nginx status:

# systemctl status nginx.service
nginx.service - Startup script for nginx service
   Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled)
   Active: failed (Result: exit-code) since Fri 2015-08-21 13:41:36 EDT; 1h 17min ago

Aug 21 13:41:36 echo[1509]: Starting nginx service
Aug 21 13:41:36 nginx[1559]: nginx: [emerg] bind() to failed (99: Cannot ass...ress)
Aug 21 13:41:36 nginx[1559]: nginx: configuration file /etc/nginx/nginx.conf test failed
Aug 21 13:41:36 systemd[1]: nginx.service: control process exited, code=exited status=1
Aug 21 13:41:36 systemd[1]: Failed to start Startup script for nginx service.
Aug 21 13:41:36 systemd[1]: Unit nginx.service entered failed state.
Aug 21 13:46:22 systemd[1]: Unit nginx.service cannot be reloaded because it is inactive.


Such behavior as known as software issue #PPPM-3112 and is fixed in Plesk 12 MU#62


  1. Apply latest Plesk microupdates by following article #9294 instructions.

  2. Make sure that systemd-networkd package is installed. The service ensures that network interfaces are up and have IP addresses bound.

    Additional details are available here

Search Words

nginx service failed


99: Cannot assign requested address

[FAILED] Failed to start Startup script for nginx service.


Domain/apache not working

centos 7 standalone


plesk pages stay blanc

29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 742559b1631652fadd74764ae8be475e

Email subscription for changes to this article
Save as PDF