# Tendo problemas para colocar o site no ar após a atualização
**URL:** https://meta.discourse.org/t/having-trouble-getting-the-site-up-after-update/259444
**Category:** Self-hosting
**Created:** [26 Março , 2023 09:19 UTC](https://meta.discourse.org/t/having-trouble-getting-the-site-up-after-update/259444 "2023-03-26T09:19:46Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Vinoth\_Deivasigamani](https://meta.discourse.org/u/Vinoth_Deivasigamani)
#### Post date: [26 Março , 2023 09:19 UTC](https://meta.discourse.org/t/having-trouble-getting-the-site-up-after-update/259444/1 "2023-03-26T09:19:47Z")
A atualização pela GUI falhou. Então fiz uma atualização pela linha de comando fazendo o seguinte:
cd /var/discourse
./launcher rebuild app
Quando tento me conectar ao site pelo navegador, recebo o erro ‘Este site não pode ser alcançado’. Pensando que talvez o contêiner não tenha sido iniciado, tentei:
./launcher start app
Recebo uma mensagem dizendo que o contêiner já foi iniciado. Fiz o seguinte para garantir:
./launcher restart app
Ainda o mesmo problema. O site continua inacessível pelo navegador. Não sou muito familiarizado com docker ou discourse. Então nem sei por onde começar a depurar.
Isso é o que recebo quando executo:
./launcher logs app
x86\_64 arch detected.
WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
Started runsvdir, PID is 28
ok: run: redis: (pid 40) 0s
ok: run: postgres: (pid 36) 0s
supervisor pid: 38 unicorn pid: 67
Shutting Down
run-parts: executing /etc/runit/3.d/01-nginx
ok: down: nginx: 0s, normally up
run-parts: executing /etc/runit/3.d/02-unicorn
(38) exiting
ok: down: unicorn: 0s, normally up
run-parts: executing /etc/runit/3.d/10-redis
ok: down: redis: 1s, normally up
run-parts: executing /etc/runit/3.d/99-postgres
ok: down: postgres: 0s, normally up
ok: down: cron: 1s, normally up
ok: down: nginx: 8s, normally up
ok: down: postgres: 1s, normally up
ok: down: redis: 8s, normally up
ok: down: rsyslog: 0s, normally up
ok: down: unicorn: 8s, normally up
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
Started runsvdir, PID is 28
ok: run: redis: (pid 43) 1s
ok: run: postgres: (pid 37) 1s
supervisor pid: 35 unicorn pid: 67
Agradeceria se alguém pudesse me ajudar a colocar o site no ar novamente.
---
### Author:  [@Vinoth\_Deivasigamani](https://meta.discourse.org/u/Vinoth_Deivasigamani)
#### Post date: [26 Março , 2023 10:55 UTC](https://meta.discourse.org/t/having-trouble-getting-the-site-up-after-update/259444/2 "2023-03-26T10:55:18Z")
Por impulso, executei novamente:
./launcher rebuild app
Voltou a funcionar. Não faço ideia do que deu errado antes. Mas fico feliz que tenha se resolvido.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [25 Abril , 2023 10:55 UTC](https://meta.discourse.org/t/having-trouble-getting-the-site-up-after-update/259444/3 "2023-04-25T10:55:25Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.