"Not found" error on ITK Snap (connecting to remote server)

I'm running nninteractive on a remote server with a GPU and I'm trying to connect to it using ITK Snap on a separate computer on the same network (over VPN).

The following is the output on the server:

2026-06-04 10:12:39,477 WARNING nninteractive.server: Starting server WITHOUT authentication. Anyone who can reach 0.0.0.0:41527 can drive inference. Pass --api-key or set NN_INTERACTIVE_API_KEY to enable bearer-token auth.
2026-06-04 10:12:39,478 INFO nninteractive.server: Loading checkpoint from /model/nnInteractive_v1.0 (fold=0, checkpoint=checkpoint_final.pth)
2026-06-04 10:12:44,369 INFO nninteractive.server: torch.compile enabled; compiling network and warming up (the first compile is slow)...
2026-06-04 10:13:09,990 INFO nninteractive.server: warmup forward pass complete in 24.7s; clients' first prediction will be fast
2026-06-04 10:13:09,991 INFO nninteractive.server: Checkpoint loaded; serving on http://0.0.0.0:41527 (max_sessions=1, idle_timeout=600s, liveness_timeout=60s)
INFO:     Started server process [1]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:41527 (Press CTRL+C to quit)
session initialized
================================================================================
Model license:
CC BY-NC-SA 4.0
================================================================================
session initialized
Using torch.compile
session initialized
INFO:     SERVER_IP:34482 - "GET /status HTTP/1.1" 404 Not Found
INFO:     SERVER_IP:45978 - "GET /status HTTP/1.1" 404 Not Found
INFO:     SERVER_IP:37316 - "GET /status HTTP/1.1" 404 Not Found
INFO:     SERVER_IP:56270 - "GET /status HTTP/1.1" 404 Not Found
...

The last 4 lines appear whenever I try to reconnect at ITK Snap, and it's always 4 lines with different random ports for every reconnect. What are they? What am I missing here?

Start by tracing the server's HTTP route definitions and the ITK Snap connection requests, focusing on the repeated GET /status calls shown in the logs. Determine why that endpoint returns 404 and compare the server's exposed API with the client expectation; done means the cause and a reproducible compatibility fix or configuration change are established.