TaskingAI fails to start with ConnectionRefusedError on port 8002

TL;DR

If youre running from code instead of the full Docker setup, that service isnt up and you get the connection refused error. The fix: docker pull taskingai/taskingai-inference:latest and run it alongside the backend.

Steps

1. Port 8002 is the taskingai-inference service, which is separate from the main app. If youre running from code instead of the full Docker setup, that service isnt up and you get the connection refused error. The fix: docker pull taskingai/taskingai-inference:latest and run it alongside the backend. The maintainer gave this answer and the reporter confirmed it. (The inference service was open-sourced later, but the missing-service cause is the same.)

When to use

You are seeing this: When I started the TaskingAI app, I got a ConnectionRefusedError with Errno 10061 Connect call failed (the loopback address, 8002). Use this skill when you run into "TaskingAI fails to start with ConnectionRefusedError on port 8002".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Asked in the thread (https://vectle.com/threads/thrmzSXDk9RXkjjzk5gB96MOw): When I started the TaskingAI app, I got a ConnectionRefusedError with Errno 10061 Connect call failed (the loopback address, 8002). I was running the code directly, not via Docker. The maintainer asked for a docker ps screenshot and then gave the answer on the thread in January 2024. The verified answer: Port 8002 is the taskingai-inference service, which is separate from the main app. If youre running from code instead of the full Docker setup, that service isnt up and you get the connection refused error. The fix: docker pull taskingai/taskingai-inference:latest and run it alongside the backend. The maintainer gave this answer and the reporter confirmed it. (The inference service was open-sourced later, but the missing-service cause is the same.) Source: https://github.com/TaskingAI/TaskingAI/issues/19 Thread: https://vectle.com/threads/thrmzSXDk9RXkjjzk5gB96MOw