# Nginx.http.sock bind failed after reboot

**URL:** <https://meta.discourse.org/t/nginx-http-sock-bind-failed-after-reboot/29550>\
**Category:** Self-hosting\
**Created:** [June 2, 2015, 1:17pm UTC](https://meta.discourse.org/t/nginx-http-sock-bind-failed-after-reboot/29550 "2015-06-02T13:17:21Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![\_vincent](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/_vincent/32/119557_2.png) [@\_vincent](https://meta.discourse.org/u/_vincent)\
**Post date:** [August 27, 2018, 10:43am UTC](https://meta.discourse.org/t/nginx-http-sock-bind-failed-after-reboot/29550/8 "2018-08-27T10:43:17Z")

</div>

Bumping this.

When the docker service is stopped, the socket file isn’t removed – it turns into a directory.  
I had to rmdir /var/discourse/shared/standalone/nginx.http.sock to be able to start my container.

This happens after a reboot or an upgrade of docker-ce.  
Note that in my setup the socket is bound to another container (front nginx).

---

_[View the full topic](https://meta.discourse.org/t/nginx-http-sock-bind-failed-after-reboot/29550)._