# Bind para 0.0.0.0:443 falhou: porta já está alocada

**URL:** <https://meta.discourse.org/t/bind-for-0-0-0-0-443-failed-port-is-already-allocated/151871>\
**Category:** Self-hosting\
**Created:** [Maio 18, 2020, 7:55pm UTC](https://meta.discourse.org/t/bind-for-0-0-0-0-443-failed-port-is-already-allocated/151871 "2020-05-18T19:55:49Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Rs40x](https://avatars.discourse-cdn.com/v4/letter/r/f19dbf/32.png) [@Rs40x](https://meta.discourse.org/u/Rs40x)\
**Post date:** [Maio 18, 2020, 7:55pm UTC](https://meta.discourse.org/t/bind-for-0-0-0-0-443-failed-port-is-already-allocated/151871/1 "2020-05-18T19:55:50Z")

</div>

Os fóruns estão fora do ar desde que a reconstrução falhou durante a atualização (var/discourse/launcher rebuild app).

Tentei a solução [daqui](https://github.com/moby/moby/issues/25981). A seguinte solução não funcionou.

systemctl stop docker  
rm -rf /var/lib/docker/network/files  
systemctl start docker

```plaintext
/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint app (db53): **Bind for 0.0.0.0:443 failed: port is already allocated**.

# netstat -tulpen | grep 443
tcp6 0 0 :::443 :::* LISTEN 0 488127 30700/docker-proxy  

# docker ps

1d8b7461b27d local_discourse/import "/sbin/boot" 6 weeks ago Up 9 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp import

```

O que mais posso fazer para colocar os fóruns de volta no ar?

Obrigado antecipadamente.

---

_[View the full topic](https://meta.discourse.org/t/bind-for-0-0-0-0-443-failed-port-is-already-allocated/151871)._