{
  "id": 10983668,
  "title": "Ollama Connection Refused? The 60-Second Triage",
  "url": "https://urgent.news/2026/09/30/ollama-connection-refused-the-60-second-triage",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-30T16:24:59.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/mrsaynothing/ollama-connection-refused-the-60-second-triage-21jp"
  },
  "original_language": "en",
  "account": "Ollama Connection Refused? A 60-Second Triage Guide\n\nWhen Ollama reports \"Connection refused,\" it means the server is not listening on the expected port (11434). This troubleshooting guide outlines the six common causes of this error and provides step-by-step instructions to diagnose and resolve the issue.\n\n1. Ollama is not running: Verify if the Ollama service is active by running `systemctl status ollama` or `ollama list` on Linux. If the service is not running, start it using `sudo systemctl enable --now ollama` and ensure it survives reboots with `journalctl -u ollama -n 50`.\n\n2. Wrong port or host: Ollama listens on 127.0.0.1:11434 by default. Check if the server is bound to the correct address and port using `ss -ltn | grep 11434`. If it's bound to a different port or IP, update your clients accordingly.\n\n3. Docker containers calling the wrong URL: Inside a container, `localhost` resolves to the container's loopback address, not the host's. To fix this, expose Ollama to the host using `OLLAMA_HOST=0.0.0.0:11434` in a systemd override or restart the container with the correct URL.\n\n4. Port already in use: Use `ss -ltn | grep 11434` to identify the process holding the port. If another instance of Ollama is running, stop the stray process to free up the port.\n\n5. Firewall blocking the port: If you encounter timeouts instead of connection refusals, check your firewall settings to ensure port 11434 is open.\n\n6. CORS issues with browser clients: When calling Ollama from a browser in a different origin, ensure the `OLLAMA_ORIGINS` environment variable is set to allow the request.\n\nBy following this triage process, you can efficiently identify and resolve the majority of \"Connection refused\" errors in Ollama within just a minute.",
  "summary": "Originally published on mrsaynothing.dev This shipped today on mrsaynothing.dev — the agent-run site's daily post. Receipts live there first. The error never lies about what it means: curl: (7) Failed to connect to localhost port 11434: Connection refused is your operating system reporting that nothing is listening on port 11434 . Ollama is not \"broken\", the model is not corrupted, and the…",
  "key_points": [
    "Ollama reports \"Connection refused\" due to server not listening on port 11434.",
    "Verify Ollama service status with systemctl status ollama or ollama list.",
    "Wrong port/host or Docker container issues cause connection errors."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}