Restarting the server, restarting the container, console rebuilding doesn’t help. Container is up as I can ./launcher enter app Got a bunch of these in logs, ideas on how to investigate redis failure? Error connecting to Redis on localhost:6379 (Errno::EADDRNOTAVAIL) subscribe failed, reconnectin…

Found the issue! A plugin! (mine!!)

Is redis actually running inside the container? Does sv think it is? root@michael-discourse-docker-app:/# sv status redis run: redis: (pid 548) 9843135s; run: log: (pid 547) 9843135s Does anything show in /var/log/redis/current? Can you sv down redis (if up) and sv up redis? Any relevant logs s…

/var/www/discourse/log# sv status redis run: redis: (pid 565) 1430s; run: log: (pid 560) 1430s /var/www/discourse/log# sv down redis /var/www/discourse/log# sv up redis /var/www/discourse/log# tail /var/log/redis/current 4766:M 14 Dec 2023 17:26:20.195 * monotonic clock: POSIX clock_gettime 4766:M …

Thanks Michael, looks like it was a Zeitwerk naming infraction! (not picked up by Rubocop I might add, and works in Dev). But those commands are very very useful for future reference!

502 Bad Gateway nach Online-Neuerstellung von Tests-bestandenem Production gerade eben

Unterstützung Installation

merefield (Robert) 14. Dezember 2023 um 17:29 4

Problem gefunden! Ein Plugin! (Meins!!)

502 bad gateway with clean rebuild and no plugins except discourse docker

Thema		Antworten	Aufrufe
502 bad gateway with clean rebuild and no plugins except discourse docker Self-hosting	5	422	14. Februar 2024
Error connecting to Redis on localhost - Rebuilt Self-hosting	14	1833	29. Januar 2020
Error connecting to Redis Self-hosting	17	7089	21. März 2023
Redis Error after upgrade Self-hosting	14	1682	3. Juli 2020
Issue with new update: debugging options Self-hosting	16	305	30. August 2024

502 Bad Gateway nach Online-Neuerstellung von Tests-bestandenem Production gerade eben

Verwandte Themen