Upon network hitches, pipeline websocket may stop sending updates to the client and doesn't reconnect
TapGhoul
- Open vrchat
- Sit in any world for long enough, when on a faulty connection
- Try to self-invite from the website, or check for changes on the social list
If you're unlucky, you won't get that self-invite (or any other notification) and the social list won't update.
The log shows nothing about a websocket issue, the server is either just not sending updates, or the local websocket is silently failing. There is no EOS log showing any weirdness either, the session continues just fine, and according to vrcx and the website my status doesn't even hitch - I remain online and in instance, with proper updates to my status and location being pushed out as I travel as if nothing is wrong.
This occurs on both stable and betas. I never get a "Lost connection to VRChat" alert when this happens.
For a bit of extra context: this has been reported by others and I've seen this issue before, but due to a bug in my router's firmware in a recent update this is becoming super frequent. Every 10-20 mins I have all packets either delayed or blackholed for a short period - no NACKs or anything. Every time this happens, various applications respond differently - twitch's chat websocket reconnects, twitch streams need a reload, ICMP pings time out. This happens for maybe up to 500ms or so every time it happens.
Attempting to travel to instances via external means using the vrchat URL handler works perfectly, everything loads, travel works just fine, and status updates to friends and to the website/vrcx, but the websocket still remains busted.
Log In
Hackebein
This is not only an issue of the last couple weeks, this is a long running issue for many years. Iirc the issue is related do to that the websockets are read-only and the connection never gets terminated. For the game the websocket is still connected. Because they are read-only there is no way to check if the ws connection is still getting messages send or a dead tunnel. That's why you never see any "Lost connection to VRChat" message.
TapGhoul
Hackebein I generally know it's a long-standing issue, but given stuff on my end has made it super frequently occurring, hopefully the extra info re my recently fucked up network conditions triggering it can help either way. That's the past 2 weeks thing.
gl-inet botched a change in their 4.9.0 firmware :V
TapGhoul
Just gonna add: this was posted during an API outage. It's not because of that outage that I posted this, this has been a more active issue for the above reasons for the past couple weeks, though the underlying issue has been a longstanding one for years.