the desktop app kept failing with timed out connecting to the backend after 8000ms. the backend itself was completely healthy, answering on loopback instantly. the problem was the path the app picked. the server name resolved to the local network address, and the firewall silently drops that port on the local network. only the private mesh network path between my machines is open.
a silent drop is the worst kind of failure. no refusal, no error, no reset, just nothing, so the app waits out its full 8000 milliseconds and gives up. the kernel log showed the connection attempts arriving on the wifi interface and getting dropped one by one. meanwhile a live connection over the mesh was up right then, working.
the fix was pointing the app at the mesh address instead of the server name. no server change needed, that path works from anywhere. then it still failed with the literal address while a browser to the same address succeeded, which points at something app specific. started reading the app's own probe code to see what it actually waits for and how. still chasing that tail.