403 Error after queue
tracked
SNOWOBALL
- Open VRChat
- Join a queue for a full instance
- Wait until "queue ready" notification
- Click "join" through notification or instance in the menu
- "You are not allowed to travel to that location. Instance queue isn't empty. you must queue first. (Code: 403)"
- Repeat (I had to retry 7 times on NYE)
This issue occurred to me on NYE and a few weeks prior as well. It definitely wasn't a one-off.
Associated output log:
2025.01.01 03:25:49 Log - [Behaviour] Destination requested: wrld_64c17705-a5c0-46f5-acae-8760dc13092e:85739~group(grp_887eb49b-153e-41d0-9795-f150b1eebfba)~groupAccessType(plus)~region(eu)
2025.01.01 03:25:49 Error - Failed to join user in instance wrld_64c17705-a5c0-46f5-acae-8760dc13092e:85739~group(grp_887eb49b-153e-41d0-9795-f150b1eebfba)~groupAccessType(plus)~region(eu) - You are not allowed to travel to that location. Instance queue isn't empty‚ you must queue first․ (Code: 403)
2025.01.01 03:25:49 Log - Remove notification from Local notifications:<Notification from username:, sender user id:8JoV9XEdpo to of type: localNotifs, id: 16147921, created at: 01/01/2025 02:25:46 UTC, details: {{}}, type:localNotifs, m seen:False, message: "Press Join to travel.">
2025.01.01 03:25:49 Log - Remove notification from AllTime notifications:<Notification from username:, sender user id:8JoV9XEdpo to of type: localNotifs, id: 16147921, created at: 01/01/2025 02:25:46 UTC, details: {{}}, type:localNotifs, m seen:False, message: "Press Join to travel.">
2025.01.01 03:25:49 Log - Remove notification from Recent notifications:<Notification from username:, sender user id:8JoV9XEdpo to of type: localNotifs, id: 16147921, created at: 01/01/2025 02:25:46 UTC, details: {{}}, type:localNotifs, m seen:False, message: "Press Join to travel.">
Photo Viewer
View photos in a modal
Log In
Miniontoby
The instance was a Group+. Were you in that group?
If you like opened the instance page from external websites, then it willl show the instance, but if you attempt to join it without being in the group, then it will give you a 403.
But yeah likelly it is just the queue being an issue here yes
Oh and once you got a 403 in that way, then after you joined the group, you must restart vrchat, else it will not even attempt/look if you have permissions to join it anymore. vrchat just straight up uses cache and doesnt update that.
But that is probably a whole different bug report on itself tho...
fluffyawoo
still happening
Whaddageek
If I had to guess, the 403 return code is a recent addition and it's causing the client function to bomb out to a catch statement as an actual Error, instead of gracefully going into the queuing function because the instance is full.
Whaddageek
This is STILL occurring seven months later.
StormRel
marked this post as
tracked