Hello, We have a discourse for the Scala PL for users which was running fine for years : [imagen] Scala Users a forum for the Scala programming language. beginner questions welcome Last week, I upgraded to the latest version using "./launcher rebuild app "…

Looking deeper, deleting the _t cookie remove the “error 500”, but the error appears again when logged after maybe around 1h.

v2026.9.0 has not been release yet - are you referring to the development/latest version? [imagen] Discourse Releases Browse Discourse release history & changelogs.

I’ve not set any specific version, so I guess by default it should be latest (according to "tests-passed" is now "latest" ). In the dashboard, this is the version I get at the bottom.

In /logs, can you find the 500 error and share the error and its backtrace?

I only have that in the logs (production.log), nothing elsewhere: Started GET "/" for 127.0.0.1 at 2026-09-07 08:05:50 +0000 Processing by ListController#latest as HTML Rendered layout layouts/application.html.erb (Duration: 164.0ms | GC: 13.5ms) Completed 500 Internal Server Error in 248ms (V…

It’s on the route /logs unless that is failing too.

Sorry, I was looking at the container logs. Here they are: Message (18 copies reported) PG::InvalidTextRepresentation (ERROR: invalid input syntax for type inet: "unix:" LINE 7: client_ip = 'unix:', ^ ) lib/mini_sql_multisite_connection.rb:109:in 'MiniSqlMultisiteConnection#run' app/models/u…

Are you operating some kind of proxy - can you describe the architecture? Looks like you are trying to pass the string “unix:” to the ip_address field … This could be a misconfiguration upstream of Discourse. There was a similar issue reported, and solved here which related to Caddy: …

Thanks a lot for the help! I have exactly this configuration: [imagen] Installing Discourse Behind Reverse Proxy using recommended (supported) installation Self-hosting In this post, I will show you exactly how to run discourse behind a nginx reverse proxy. W…

Error 500 tras actualizar a v2026.9.0 / resuelto temporalmente borrando los datos del navegador

Soporte Instalación

merefield (Robert) 3 Septiembre, 2026 17:18 5

En /logs, ¿puedes encontrar el error 500 y compartir el error y su backtrace?

Tema		Respuestas	Vistas
The discourse stopped working with error 500 Internal Server Error Bug	1	3123	7 Marzo 2017
Forum doesn't work after latest upgrade Self-hosting	17	528	17 Mayo 2024
I'm using a Unix socket between Caddy and Discourse instead of TCP, but from time to time I get a 'unix:' error Support	12	265	29 Agosto 2026
Stuck with 500 error after weird bugs and a rebuild Self-hosting	17	2240	8 Enero 2024
Link to upgrade shows 500 error Bug	6	1088	2 Octubre 2017

Error 500 tras actualizar a v2026.9.0 / resuelto temporalmente borrando los datos del navegador

Temas relacionados