401 on `/matchmaker/lobbies/find`
I'm missing an entitlement?
(I unlinked and linked just now to make sure it wasn't an old token or something)
Do I have to generate the token somewhere other than
rivet init?11 Replies
Looks like you might be using the wrong token here
I think it's maybe using a cloud token when it should be using a public token
Is this in Godot?
yes
Hmm that is interesting since it should be swapping the tokens in correctly for you
Is this after making a standalone build with Godot, or when launching from the editor?
deploying with the build and deploy button yields no error, but then when i run it in the editor it throws this
If you go to the playtest tab, can you switch to "this machine" then back to "rivet servers"
This is more of a sanity check, but just want to make sure the token isn't getting cached
Oh also did you ever verify if you were on the main branch of the examples repo, or on the
pre-rivet branch?this machine and rivet servers both 401 (i switched a couple of times and tried each time)
and i'm not using the example project, but i am using the edited rivet_client.gd
the one from my PRCan you try going to settings in the plugin and unlinking, then linking again?
I haven't seen this machine + rivet servers giving that error before, so I'll have to look more into that
@Nathan can you think of anything recent that might cause 401s like this?
i did this and the error wasn't fixed
(reinstalled the godot plugin (v1.3.6) and now i'm getting missing RIVET_TOKEN errors hang on)
hmm
Just checking, but when you reinstall/update, do you delete the existing plugin folder or overwrite it with the new files?
this time i deleted
/addons/riveti think the cloud token (looks like
cloud.xxxx.xxxx) is somehow getting mixed up with the public/dev token (pub_*.xxxx.xxxx/dev_*.xxxx.xxxx) which is causing the 401. i have no idea how that's happening though, forest and i will take a peek tomorrow.