I’m self-hosted and have 3 of the plugins that were recently moved to core. My upgrade steps: Edited containers/app.yml and removed the lines for the 3 plugins (data-explorer, solved, assign) cd /var/discourse sudo ./launcher rebuild app The rebuild takes the usual 5 minutes and seems to complet…

[Bild] xyzzy: , I get no response. So the request times out?

[Bild] pfaffman: So the request times out? The server refuses the connection. It seems to take about 2 seconds for the connection to be refused in both browsers I’ve tried. And nothing new shows up in production.log.

Any ideas what’s going on? Any suggestions for additional debugging steps?

I’d look at two things is the server process running and listening is your browser trying to contact the correct server Check that your forum URL’s domain name does resolve, from your own PC, to the IP address of your server. Double-check. Perhaps try, on your server ping -c1 DOMAINNAME netstat…

You can try docker logs app The last person I helped had a bogus value for his letsencrypt email address. It sounds like nginx isn’t starting up for some reason. The most common reason is that the certs are broken.

Fehlgeschlagenes Upgrade von 3.5.0.beta8-dev auf 3.6.0.beta1

Unterstützung Installation

pfaffman (Jay Pfaffman) 13. Oktober 2025 um 00:33 2

Die Anfrage läuft also ab?

Thema		Antworten	Aufrufe
Redis Error after upgrade Self-hosting	13	1711	3. Juni 2020
Sidekiq not running. Sidekiq heartbeat test failed, restarting Self-hosting unsupported-install	14	2902	11. Mai 2020
Sidekiq heartbeat test failed, restarting Self-hosting	11	2117	12. Januar 2020
"Ensure sidekiq is running." when it is definitely running Self-hosting	18	7885	2. Oktober 2015
"Sidekiq is not running" Self-hosting	6	3052	7. Februar 2016

Fehlgeschlagenes Upgrade von 3.5.0.beta8-dev auf 3.6.0.beta1

Verwandte Themen