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 después de reconstrucción online de Producción tests-passed

Soporte del producto Instalación

merefield (Robert) 14 Diciembre, 2023 17:29 4

¡Encontré el problema! ¡Un plugin! (¡el mío!)

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

Tema		Respuestas	Vistas
502 bad gateway with clean rebuild and no plugins except discourse docker Self-hosting	5	516	14 Febrero 2024
Error connecting to Redis on localhost - Rebuilt Self-hosting	14	2098	29 Enero 2020
Error connecting to Redis Self-hosting	17	7432	21 Marzo 2023
Redis Error after upgrade Self-hosting	13	1883	3 Junio 2020
Issue with new update: debugging options Self-hosting	16	589	30 Agosto 2024

502 Bad Gateway después de reconstrucción online de Producción tests-passed

Temas relacionados