Nodes/ComfyUI-Text2Speech/TTSServerStatus
ComfyUI Node

TTSServerStatus

Is your TTS server alive? This node tells you before you waste an hour

By GeekatplayStudio·Created 10 months ago·Updated 8 months ago· 2
TTSServerStatus
    • status
    server_urlhttp://127.0.0.1:5002/status

    TTSServerStatus is the pack's built-in pulse check. The whole ComfyUI-Text2Speech setup depends on a separate Flask server running on port 5002 - and when your workflow errors, the very first question is "is that server actually up?" This node answers it in one click. Add it before you start debugging anything else, and you've cleanly separated "server problem" from "request problem."

    It's a one-trick pony, but the trick is genuinely useful. Instead of staring at a cryptic connection error from the TTS node, you get a plain-English verdict.

    How it works

    The node is dead simple: it sends a GET request to server_url with a 5-second timeout and reports what comes back. The default endpoint is http://127.0.0.1:5002/status, which the server responds to with a JSON {"status": "running"}. A 200 response returns the string "Server is running"; anything else returns a message with the status code; a connection failure returns "Server not running or unreachable" plus the underlying error, which is the useful part - it usually tells you whether it's a refused connection, a timeout, or something weirder.

    Note what it doesn't do: it doesn't gate anything, and it doesn't start the server for you. It returns a status string rather than raising, so your queue keeps going either way. Treat it as a diagnostic instrument, not a safety switch.

    The inputs and output

    There's one input, server_url (default http://127.0.0.1:5002/status), and you'll almost never touch it - unless you moved the server to another host or port. The output is a single status STRING. Since it's a string rather than a colored lamp, wire it into any text-display node (ShowText or similar) to actually see it, or just run the graph and inspect the result. The pack's own workflow puts it in front of HttpTTSToAudio as a sanity check.

    Installing it

    Same install as its sibling node - you get both at once. ComfyUI Manager (search "ComfyUI-Text2Speech") or cd ComfyUI/custom_nodes && git clone https://github.com/GeekatplayStudio/ComfyUI-Text2Speech, then restart and pip install -r requirements.txt (install.bat on the standalone Windows build). The dependencies are light - flask, requests, edge-tts, pyttsx3 - and there are no models to download.

    When it tells you it's down

    If the status node reports the server unreachable, the fix is to run python tts_server.py (or run_tts.bat on Windows) and check that nothing else is squatting on port 5002. One caveat: this whole pack assumes localhost, so if ComfyUI is running in a container or on a different machine, 127.0.0.1 won't reach the server - you'd need to point both nodes at the real host.

    Honest take: you don't need this node in every workflow. You need it the first time HttpTTSToAudio throws a connection error and you wonder whether it's you, the network, or the server. Five seconds with this node saves you twenty minutes of poking at a workflow that was never the problem.

    Categorygeekatplay/TTS

    Inputs (1)

    NameTypeDefaultDescription
    server_urlSTRINGhttp://127.0.0.1:5002/status

    Outputs (1)

    NameTypeDescription
    statusSTRING