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…

Update: We fixed the issue by copying the Discourse instance to a new droplet with @pfaffman ’s help. Thank you all for your advice!

Hm. I had the exact same issue with a different hosting provider and resolved it by moving to digital ocean. [изображение] Docker sometimes fails to connect to github.com installation While trying to upgrade Discourse via ./launcher rebuild app I get an issue with fatal:…

Exit code 128 is out of memory. Increase your ram or swap.

[изображение] Jay Pfaffman: Exit code 128 is out of memory. No it’s not? 128 is a generic error code. Out of memory results in 137 most of the time. could not resolve host is a network of DNS issue.

@pfaffman After increasing the vCPU from 6 - 8 (the only thing I can upgrade on DigitalOcean), I am still getting the same Exit Code 128 error. My server’s spec: 8vCPUs/16GB Memory/320GB SSD/6TB Transfer System load: 0.2 Usage of /: 55.6% of 314.85GB Memory usage: …

@RGJ How can I resolve the DNS issue? Are there other issues at play?

Yeah. Sorry. I didn’t know you had that much ram. fatal: unable to access 'https://github.com/discourse/discourse.git/': Could not resolve host: github.com That’s the issue. Don’t know how you’d get that on a digital ocean droplet. Must be something with your docker network. But I don’t have any i…

Docker seems to be running correctly. Anything else I can try? root@forum:~# docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world 2db29710123e: Pull complete Digest: sha256:94ebc7edf3401f299cd3376a1669bc0a49aef92d6d2669005f9bc5ef028dc333…

The below didn’t work. Still getting the same error. :confused: git config --global --unset https.proxy

Could this be the cause of the issue? How could I resolve it? # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use # Failed listening on port 6379 (TCP), aborting. Thank you!

ПОМОЩЬ: Обновление Discourse сломало приложение — не собирается

Поддержка Самостоятельное хостинг

littleviolette 10.Январь.2023 17:43:53 16

Обновление: Мы решили проблему, скопировав экземпляр Discourse на новый Droplet при помощи @pfaffman. Спасибо всем за советы!

Need help getting the Discourse instance running again after update broke app

Тема		Ответов	Просм.
First installation - Error on rebuild app Self-hosting	9	407	15.02.2024
Can't build container, no clear errors Self-hosting	3	2202	01.04.2022
Latest site upgrade not working Self-hosting	11	1781	22.02.2022
Unable to boostrap Discourse since last upgrade Self-hosting	5	726	22.01.2023
Discourse stopped working all of a sudden Self-hosting	8	364	06.07.2024

ПОМОЩЬ: Обновление Discourse сломало приложение — не собирается

Связанные темы