# Falha na instalação no Debian 11 (ProxMox/KVM)

**URL:** https://meta.discourse.org/t/installation-failed-on-debian-11-proxmox-kvm/251292
**Category:** Self-hosting
**Created:** [10 Janeiro , 2023 14:22 UTC](https://meta.discourse.org/t/installation-failed-on-debian-11-proxmox-kvm/251292 "2023-01-10T14:22:16Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![lukasjelinek](https://avatars.discourse-cdn.com/v4/letter/l/96bed5/32.png) [@lukasjelinek](https://meta.discourse.org/u/lukasjelinek)
#### Post date: [10 Janeiro , 2023 14:22 UTC](https://meta.discourse.org/t/installation-failed-on-debian-11-proxmox-kvm/251292/1 "2023-01-10T14:22:16Z")

</div>

Olá, tento instalar o contêiner Docker do Discourse (usando este guia: [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md)) em um novo servidor com Debian 11 recém-instalado. Mas falha com a mensagem de erro anexada abaixo. A mensagem em si não fornece muita informação sobre o que acontece - mas sugere que há um problema com o acesso ao GitHub ([github.com](http://github.com) não pode ser resolvido). O servidor em si é uma máquina virtual gerenciada pelo ProxMox/KVM. Alguém pode ajudar com este problema, por favor?

```plaintext
I, [2023-01-10T14:10:50.610422 #1] INFO -- : cd /var/www/discourse & git fetch --depth 1 origin tests-passed
fatal: unable to access 'https://github.com/discourse/discourse.git/': Could not resolve host: github.com
...
Pups::ExecError: cd /var/www/discourse & git fetch --depth 1 origin tests-passed failed with return #<Process::Status: pid 141 exit 128>
Location of failure: /usr/local/lib/ruby/gems/3.1.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"code", "cmd"=>["git reset --hard", "git clean -f", "git remote set-branches --add origin main", "git remote set-branches origin $version", "git fetch --depth 1 origin $version", "git checkout $version", "mkdir -p tmp", "chown discourse:www-data tmp", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p /shared/log/rails", "bash -c \"touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log\"", "bash -c \"ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log $home/log\"", "bash -c \"mkdir -p /shared/{uploads,backups}\"", "bash -c \"ln -s /shared/{uploads,backups} $home/public\"", "bash -c \"mkdir -p /shared/tmp/{backups,restores}\"", "bash -c \"ln -s /shared/tmp/{backups,restores} $home/tmp\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp", "[! -d public/plugins] || find public/plugins/ -maxdepth 1 -xtype l -delete]"}
bootstrap failed with exit code 128

```

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [10 Janeiro , 2023 14:28 UTC](https://meta.discourse.org/t/installation-failed-on-debian-11-proxmox-kvm/251292/2 "2023-01-10T14:28:29Z")

</div>

Olá e bem-vindo @lukasjelinek 🙂

Houve alguns relatos disso recentemente, embora receio que ainda não haja solução. Acredito que @hiddenseal moveu a instância deles para um novo servidor e isso resolveu para eles, e o problema de @littleviolette ainda está pendente:

> [@Docker sometimes fails to connect to github.com](https://meta.discourse.org/t/docker-sometimes-fails-to-connect-to-github-com/250643):
>
> While trying to upgrade Discourse via ./launcher rebuild app I get an issue with fatal: unable to access 'https://github.com/discourse/REPO.git/': Failed to connect to github.com port 443: Connection timed out However, the problem is: sometimes this fails even for discourse. But if you try to do it again, immediately after, with no changes, it may go through, but fail on one of the plugins. If I remove all the plugins, the discourse connection may fail or it may go through and actually build t…

> [@HELP: Discourse Update broke app -- fails to rebuild](https://meta.discourse.org/t/help-discourse-update-broke-app-fails-to-rebuild/251043):
>
> When I tried to update to the latest version today, I encountered the follow error: fatal: unable to access 'https://github.com/discourse/discourse.git/': Could not resolve host: github.com I am running the app on a DigitalOcean Droplet Ubuntu 18.04.6 LTS (GNU/Linux 3.13.0-52-generic x86\_64) I am not familiar with docker or server-side programming. I would really appreciate your help! pray Here is the error code in its entirety: root@forum:/var/discourse# ./launcher rebuild app x86\_64 arc…

Há algo semelhante nesses tópicos que soa familiar para você e que possa nos ajudar a rastrear a causa?

---

<div class="post-metadata">

### Author: ![lukasjelinek](https://avatars.discourse-cdn.com/v4/letter/l/96bed5/32.png) [@lukasjelinek](https://meta.discourse.org/u/lukasjelinek)
#### Post date: [10 Janeiro , 2023 15:11 UTC](https://meta.discourse.org/t/installation-failed-on-debian-11-proxmox-kvm/251292/3 "2023-01-10T15:11:45Z")

</div>

Parece que o último caso é o mesmo (embora em uma distribuição Linux diferente).

---

<div class="post-metadata">

### Author: ![littleviolette](https://avatars.discourse-cdn.com/v4/letter/l/d26b3c/32.png) [@littleviolette](https://meta.discourse.org/u/littleviolette)
#### Post date: [10 Janeiro , 2023 17:45 UTC](https://meta.discourse.org/t/installation-failed-on-debian-11-proxmox-kvm/251292/4 "2023-01-10T17:45:42Z")

</div>

Não conseguimos descobrir o que deu errado com o servidor existente. Acabamos copiando a instância do Discourse para um novo droplet e ele voltou a funcionar.
