The logs show the following: PG::InvalidTextRepresentation (ERROR: invalid input syntax for type inet: "unix:" LINE 7: client_ip = 'unix:', ^ ) lib/mini_sql_multisite_connection.rb:109:in 'MiniSqlMult rack-mini-profiler (4.0.1) lib/patches/db/pg/alias_method.rb:109:in 'PG::Connection#exec' rack-mi…

I’m not an expert and I did not use Caddy but Nginx on my self-hosted instance, but can I ask for your actual Caddy and Discourse templates configuration in ./app/containers.yml? Can you remember what you usually did before the error happens? I mean, changing admin settings, posting, using some plu…

This means that a request / user has a remote ip pointing to your socket, which means something in your proxy chain is misconfigured.

@satonotdead @Falco app.yml templates: - "templates/postgres.18.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.socketed.template.yml" - "templates/enable-ruby-yjit.yml" ## which TCP/IP ports should this container expose? ## If you…

If the connection to the socket is right until it gets dropped, I think you can add explicit timeouts and transport options.

I think you can add explicit timeouts and transport options How?

Well, as I said before, I did not use Caddy but you can look into their official docs .

I think I found the problem. If I perform a rebuild, I never restart Caddy. From now on, I’m going to do this: ./launcher rebuild app && systemctl reload caddy I suspect that Caddy uses the socket cache or something similar after a rebuild. But it doesn’t usually happen immediately after a rebuild…

I’ve been working on this for days. I’ve verified that Caddy sends the header, that nginx receives and applies it, that there’s no CDN, no other process touching the socket, and no webhooks. Every single test passes. And the Unix error keeps appearing. I thought it was because of the rebuild, but it…

Did you add the timeouts I suggested to your Caddy template? While I’m no expert, I think that might solve your problem.

Doing that doesn’t make sense because some requests fail in 15 seconds and others in less than 1 second. It’s basically pointless.

Ich verwende einen Unix-Socket zwischen Caddy und Discourse statt TCP, aber ab und zu erhalte ich einen „unix:“-Fehler

Unterstützung

satonotdead 4. August 2026 um 18:09 12

Richtig, du kannst diese beiden Links überprüfen:

Es scheint, als würde dir ein Header fehlen und/oder deine Kette in der Discourse-Vorlagendatei.

Thema		Antworten	Aufrufe
Difference between socket- and port-based connection to outer NGINX? Self-hosting	10	12655	28. Dezember 2019
500 Oops errors after upgrading Support	1	106	20. Juli 2026
Warning: Could not create server TCP listening socket *:6379: bind: Address already in use Self-hosting	3	6720	9. April 2023
Discourse stopped working on Raspberry Pi 4 Self-hosting	12	613	9. November 2022
Error connecting to Redis Self-hosting	17	7153	21. März 2023

Ich verwende einen Unix-Socket zwischen Caddy und Discourse statt TCP, aber ab und zu erhalte ich einen „unix:“-Fehler

Verwandte Themen