TCP status gets stuck false when cached #27
Description
My node tox.abilinski.com was hit with this on nodes.tox.chat. I've managed to repro the case locally, and removing nodes.json fixes the issue. It seems like if I, from a clean state:
- Disable UDP in my firewall
- Run toxstatus long enough to generate
nodes.json - Stop toxstatus, enable UDP in my firewall
- Run toxstatus
Then the status page will indefinitely show:
Unable connect to this node through UDP. A TCP relay seems to be up and running, however.
It seems like there's an issue with cache invalidation from nodes.json, but I haven't looked into it too much yet. Now that I have a local repro I'll try to look into it, just opening this issue to help keep notes in case someone else knows something about it or in case I don't come back to it, but for the time being I plan on investigating this soon.