Too many Build & Test clients can cause a "Failed to Authenticate" error
tracked
BobyStar
Running 3+ clients and reloading them through a period of time yields me with a "Failed to authenticate with realtime servers: Too many requests" error leading me to be blocked from testing for a long period of time (sometimes hours).
This is really hindering on my ability to test networking conditions when there are multiple players at play. Like testing an unstable network connection or slow network initialization for late joiners due to differing conditions. Especially with Super VR Ball, it's almost impossible for me to network test for longer than 20 minutes before being kicked for this reason.
Proposed Solution:
- Allow me to turn off specific requests during Build & Tests, like getting group info and social information, so I produce less requests overall. Or a light version of the client with a default avatar and minimal menus similar to ClientSim in functionality.
Other Solutions:
- Allow more requests to be ran during Build & Test. (Simplest but not fun for security!)
- Allow a local realtime server that I can host with the main client. (Understandably difficult for many reasons.)
- Allow me to slowdown/step through networking events so I can test how the network handles network clogging or unstable connections. Related Canny
- Whitelist my account for a higher request limit/unlimited requests. (This would be easiest but there's got to be a better solution :P)
Log In
A
tracked
A
Merged in a post:
Multi-Client testing gives "Failed to authenticate with the realtime servers"
==Cat==
If you are multi client world testing doing new builds, eventually you will not be able to login anymore getting the error in the title. VRCX will show you stuck in your homeworld for hours even with the game closed and computer fully restarted. The effect seems to last a few hours before it settles itself on the server. Neither the normal game client nor testing allow login.
Most likely a server side bug getting your account stuck in limbo in the api. I have never had this happen since world building from 2018-now, this is the first time.
Jar
I'm running into this issue with just one or two clients. Not sure why the offline testing client needs to authenticate anyway except for creator economy stuff anyway