I’ve been trouble with automating group modifications via the groups.roblox.com API. I created an alternative account (on incognito chrome so the token wouldn’t reset), gave it permissions in the group, disabled the new session protection system and tried to use the token. However, on deploying my application to Heroku, I keep getting 401 Unauthorized errors when calling the API.
1 Like
Heroku uses dymanic IPs, not static IPs. This means the cookie will invalidate itself since cookies will reset based on the geolocation.
1 Like
Isn’t the reset based on IP part of the session protection system though? Is there any way to access the API via Heroku?
1 Like
No. If I remember correctly, the ip cookie reset applies to everyone iirc. The Account Session Protection makes the cookie expire if it’s used outside of the original device the account of cookie was logged into.
As far using Heroku to access API with cookie authentication, I’m not sure there’s a way without separate static IP hosting. Ill look into it and get back to you.
1 Like