# After restarting the server, nginx does not start

**URL:** <https://forum.hestiacp.com/t/after-restarting-the-server-nginx-does-not-start/16175>\
**Category:** Uncategorized\
**Created:** [October 12, 2024, 6:13pm UTC](https://forum.hestiacp.com/t/after-restarting-the-server-nginx-does-not-start/16175 "2024-10-12T18:13:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Konstantinus](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/konstantinus/32/652_2.png) [@Konstantinus](https://forum.hestiacp.com/u/Konstantinus)\
**Post date:** [October 12, 2024, 6:13pm UTC](https://forum.hestiacp.com/t/after-restarting-the-server-nginx-does-not-start/16175/1 "2024-10-12T18:13:03Z")

</div>

Hello!  
After restarting the server (in the console or due to a power outage), HestiaCP starts, but the nginx server does not.  
Restarting from the console or via the panel’s web interface helps to solve the problem.  
In the file /var/log/nginx/error.log:  
2024/10/12 15:40:23 [emerg] 1720#1720: bind() to 192.168.88.3:80 failed (99: Cannot assign requested address)  
2024/10/12 17:42:26 [warn] 1754#1754: “ssl\_stapling” ignored, host not found in OCSP responder “[r10.o.lencr.org](http://r10.o.lencr.org)” in the certificate "/home/library/conf/web/ **_._/ssl/** _ **.** _.p  
2024/10/12 17:42:26 [emerg] 1754#1754: bind() to 192.168.88.3:80 failed (99: Cannot assign requested address)

Thank you for your help in solving the problem!

---

<div class="post-metadata">

**Author:** ![sahsanu](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/sahsanu/32/9318_2.png) [@sahsanu](https://forum.hestiacp.com/u/sahsanu)\
**Post date:** [October 12, 2024, 7:09pm UTC](https://forum.hestiacp.com/t/after-restarting-the-server-nginx-does-not-start/16175/2 "2024-10-12T19:09:17Z")

</div>

Hi @Konstantinus,

> [@Konstantinus](#):
>
> 2024/10/12 15:40:23 [emerg] 1720#1720: bind() to 192.168.88.3:80 failed (99: Cannot assign requested address)

That means that ip `192.168.88.3` has not been configured when Nginx tries to start or that the port for that ip is already in use.

Nginx service usually starts after network is online:

```auto
$ systemctl cat nginx | grep -E '^After|^Wants'
After=network-online.target remote-fs.target nss-lookup.target
Wants=network-online.target

```

So maybe your system is assigning the ip address a bit late… you could add another service that restarts nginx on boot but it would be better to know the root cause and fix it instead of use that workaround.

---

<div class="post-metadata">

**Author:** ![system](https://forum.hestiacp.com/uploads/default/original/1X/d9a5b68bf50ced83e880b56452e592b204761b19.png) [@system](https://forum.hestiacp.com/u/system)\
**Post date:** [November 11, 2024, 7:09pm UTC](https://forum.hestiacp.com/t/after-restarting-the-server-nginx-does-not-start/16175/3 "2024-11-11T19:09:52Z")

</div>

Closed on November 11, 2024, 7:09pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.