# Não consigo iniciar um Discourse
**URL:** https://meta.discourse.org/t/i-cant-start-a-discourse/287894
**Category:** Self-hosting
**Created:** [Dezembro 7, 2023, 9:31pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894 "2023-12-07T21:31:54Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@Wleksion](https://meta.discourse.org/u/Wleksion)
#### Post date: [Dezembro 8, 2023, 9:09pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/22 "2023-12-08T21:09:16Z")
> [@Firepup650](#):
>
> exceto pelo Google
Como? Eu não entendi bem o que você quis dizer.
---
### Author:  [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [Dezembro 8, 2023, 10:16pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/23 "2023-12-08T22:16:13Z")
Quero dizer, trocar `github.com` por `google.com` no comando
---
### Author:  [@Wleksion](https://meta.discourse.org/u/Wleksion)
#### Post date: [Dezembro 9, 2023, 11:11am UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/24 "2023-12-09T11:11:45Z")
> [@Firepup650](#):
>
> curl [github.com](http://github.com) -v
```plaintext
root@37-app:/var/www/discourse# curl google.com -v
* Could not resolve host: google.com
* Closing connection 0
curl: (6) Could not resolve host: google.com
root@37-app:/var/www/discourse#
```
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [Dezembro 9, 2023, 12:07pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/25 "2023-12-09T12:07:05Z")
Não consegue conectar porque as portas estão fechadas. Você está usando firewall, proxy reverso, outros serviços, etc.?
Como é sua configuração — você está usando algum serviço de hospedagem?
---
### Author:  [@Wleksion](https://meta.discourse.org/u/Wleksion)
#### Post date: [Dezembro 9, 2023, 12:23pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/26 "2023-12-09T12:23:53Z")
Atualmente tenho um sistema baseado no Ubuntu 18.04. Eu uso vds.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [Dezembro 9, 2023, 12:37pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/27 "2023-12-09T12:37:05Z")
Bem, você tem as portas 443 e 80 abertas e nenhum outro serviço escutando nelas?
---
### Author:  [@Wleksion](https://meta.discourse.org/u/Wleksion)
#### Post date: [Dezembro 9, 2023, 12:38pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/28 "2023-12-09T12:38:48Z")
Como posso aprender isso? Se fosse Linux normal, eu poderia te dar as informações que você quer imediatamente, mas acho que precisamos fazer coisas diferentes aqui já que estamos usando docker.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [Dezembro 9, 2023, 3:00pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/29 "2023-12-09T15:00:29Z")
E ainda assim o Ubuntu é apenas um Linux comum 😉
Claro, ele também pode vir via Docker. Mas eu começaria procurando primeiro por coisas fáceis e comuns. Como o que o seu UFW diz.
---
### Author:  [@Wleksion](https://meta.discourse.org/u/Wleksion)
#### Post date: [Dezembro 9, 2023, 3:21pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/30 "2023-12-09T15:21:19Z")
> [@Jagster](#):
>
> 443
Eu digitei ` ./launcher enter app` e então entrei com este comando:
```plaintext
root@37-app:/var/www/discourse# netstat -tulnp
bash: netstat: command not found
```
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [Dezembro 9, 2023, 4:33pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/31 "2023-12-09T16:33:33Z")
Não entre no docker. Pergunte, e `ufw status`, normalmente no shell.
---
### Author:  [@Wleksion](https://meta.discourse.org/u/Wleksion)
#### Post date: [Dezembro 9, 2023, 4:40pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/33 "2023-12-09T16:40:51Z")
```plaintext
root@37:~# netstat -tulnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 136231/systemd-reso
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 128299/docker-proxy
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 136191/sshd: /usr/s
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 128276/docker-proxy
tcp6 0 0 :::80 :::* LISTEN 128306/docker-proxy
tcp6 0 0 :::22 :::* LISTEN 136191/sshd: /usr/s
tcp6 0 0 :::443 :::* LISTEN 128284/docker-proxy
udp 0 0 127.0.0.53:53 0.0.0.0:* 136231/systemd-reso
```
++
```plaintext
root@37:~# ufw status
Status: inactive
```
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [Dezembro 9, 2023, 4:59pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/34 "2023-12-09T16:59:52Z")
Tente isto:
> [@Configure a firewall for Discourse](https://meta.discourse.org/t/configure-a-firewall-for-discourse/20584):
>
> It’s unclear [if Linux distributions really “need” a firewall](https://meta.discourse.org/t/does-discourse-docker-automatically-configure-firewall-too/16750/11) – but we have found that the following [Uncomplicated Firewall](https://wiki.ubuntu.com/UncomplicatedFirewall) rules work fine with a standard Docker based Discourse install: ufw allow http ufw allow https ufw allow ssh ufw enable That is, allow HTTP (port 80), HTTPS (port 443), and SSH (port 22), and nothing else. Check the current status of your firewall with ufw status verbose Sample output: Status: active Logging: on (low) Default: deny (incoming), allow (outgoing), disable…
Se não ajudar, então você sabe que o problema pode ser o próprio docker.
---
### Author:  [@Wleksion](https://meta.discourse.org/u/Wleksion)
#### Post date: [Dezembro 9, 2023, 5:04pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/35 "2023-12-09T17:04:45Z")
Segui os passos do artigo que você me deu, mas ainda recebo o mesmo erro. O que devo fazer agora?
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [Dezembro 9, 2023, 5:15pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/36 "2023-12-09T17:15:10Z")
Você leu isto:
> [@After upgrade, docker cannot communicate with the outside world](https://meta.discourse.org/t/after-upgrade-docker-cannot-communicate-with-the-outside-world/171902):
>
> I woke up this morning to reports that my discourse server was “down”. I was able to ssh into the server without a problem, noticed some security updates needed to be applied, applied them with apt full-upgrade, and restarted the server with reboot. Took a little while to come back up but when it did I checked that the discourse docker container was running. Oddly, no problem. Tried stopping and restarting with ./launcher app stop and ./launcher app start. Didn’t help. Tried doing a ./lau…
Ou isto:
> [@Install fails with port 80,443 on GCP](https://meta.discourse.org/t/install-fails-with-port-80-443-on-gcp/155313):
>
> Hi, I created a VM with GCP compute engine. My domain name is [solarnauts.net](http://solarnauts.net) (from Namecheap) I have created a DNS A-record, for the host I have put the subdomain [discourse.solarnauts.net](http://discourse.solarnauts.net) and for the value, the external IP of my VM. When I run ./discourse-setup, I get the port 80 and 443 warnings (see down below). Despite add a firewall rule to my VM opening these 2 ports, i still get this error. What do you advise? Thanks Checking your domain name . . .WARNING: Port 443 of computer does n…
Ou isto:
> [@Failed to Bootstrap Ping is working to github](https://meta.discourse.org/t/failed-to-bootstrap-ping-is-working-to-github/23869):
>
> root@daysrilanka:~# mkdir /var/discourse root@daysrilanka:~# git clone https://github.com/discourse/discourse\_docker.git /var/discourse Cloning into '/var/discourse'... remote: Counting objects: 1353, done. remote: Compressing objects: 100% (6/6), done. remote: Total 1353 (delta 2), reused 0 (delta 0) Receiving objects: 100% (1353/1353), 301.74 KiB | 115.00 KiB/s, done. Resolving deltas: 100% (791/791), done. Checking connectivity... done. root@daysrilanka:~# cd /var/discourse root@daysrilanka:/…
Existem vários tópicos que estão próximos dos mesmos problemas que você tem.
Desculpe, mas tenho conhecimento zero de Docker 🥴
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [Dezembro 10, 2023, 6:33pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/37 "2023-12-10T18:33:00Z")
Parece ser um problema de rede. Você pode tentar copiar /var/discourse para um novo servidor, especialmente um com um serviço de hospedagem diferente.
Há um tópico sobre a mudança para outro servidor. [Mover um site Discourse para outro VPS com rsync](https://meta.discourse.org/t/move-a-discourse-site-to-another-vps-with-rsync/43812)
---
### Author:  [@anon36555649](https://meta.discourse.org/u/anon36555649)
#### Post date: [Dezembro 11, 2023, 6:43am UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/39 "2023-12-11T06:43:31Z")
Com que tipo de servidor você está tentando iniciar o Discourse?
Um servidor de $12/mês com esta plataforma funcionará com o procedimento de instalação padrão:
> **[DigitalOcean | Cloud Infrastructure for Developers](https://www.digitalocean.com/)**
>
> An ocean of simple, scalable cloud solutions.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [Dezembro 11, 2023, 7:11am UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/40 "2023-12-11T07:11:18Z")
Não sei se é questão de dinheiro porque esse Discourse não consegue ver o mundo exterior 🤔
---
### Author:  [@anon36555649](https://meta.discourse.org/u/anon36555649)
#### Post date: [Dezembro 11, 2023, 7:14am UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/41 "2023-12-11T07:14:15Z")
> [@supermathie](#):
>
> Parece que sua rede docker está quebrada; você precisará consertar isso.
Isso parece ser o problema, provavelmente pedir ao administrador do servidor/help desk seria um bom primeiro passo se não houver conexão com a internet.
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [Dezembro 11, 2023, 4:12pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/42 "2023-12-11T16:12:38Z")
> [@Jagster](#):
>
> Não consegue conectar porque as portas estão fechadas
É preciso ter cuidado aqui para não confundir dois problemas separados durante a solução de problemas. Portas de entrada fechadas não afetam conexões _de saída_.
O melhor primeiro passo aqui é provavelmente uma reinicialização para garantir que a pilha de rede e o Docker inicializem de forma limpa.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [Dezembro 11, 2023, 5:18pm UTC](https://meta.discourse.org/t/i-cant-start-a-discourse/287894/43 "2023-12-11T17:18:36Z")
E, no entanto, a maioria dos administradores usa UFW e ele cuida de ambas as direções.
[Página anterior](https://meta.discourse.org/t/i-cant-start-a-discourse/287894.md?page=1)
[Próxima página](https://meta.discourse.org/t/i-cant-start-a-discourse/287894.md?page=3)