Every connection-refused hunt I've been part of — mine, and the ones documented in public issues — ended in one of two embarrassments. Either the thing that should have been listening was never started (the systemd service nobody enabled after the reboot), or the caller was talking to itself: 127.0.0.1 inside a container, pointing at nothing.
Today's post on the site breaks the six causes down for Ollama specifically, ranked by how often each one turns out to be the answer. The caller table is the part worth taping next to the monitor: container → host.docker.internal or the service name, never localhost.
So, the question:
What was actually broken the last time you saw connection refused?
The service that wasn't enabled? The port you changed in one config file and not the other? The container that called itself for an hour before anyone checked? Old wrong answers welcome — the dumber the cause, the better the story.
Top comments (0)