LittleBigRefresh
LBP3 disconnects after a certain amount of time passes
if you play LBP3 for long enough, the game will disconnect you from the server for no clear reason, making you have to connect again
pretty sure just the token expiring? because the game still sends requests but the server responds 403
The above is probably the case. As I understand it the game should be automatically grabbing a new token, though? Is this an error popping up in-game @Arcadius2006?
LBP3 RPCS3
- Set
GameTokenExpirySecondsto 1 minute for testing
The game successfully reauthenticates for the first 5 attempts:
After multiple successful reauthentications, the game stops attempting to reauthenticate for some reason:
- No error messages appear in-game
- Only loading indicators are shown
But other times it just does it 10+ times before it stops working?
Unsure what to conclude other than that the game eventually just doesnt try to reauthenticate. no idea if also PS3 behavior.
Wanted to open a new issue on what I found yesterday, but then found this. LBP3, on versions 1.21 and 1.26 on upstream Patchwork and on RPCS3, likes to periodically call /lbp/login every ~30 seconds after browsing community categories for a few minutes. The server will eventually rate-limit the game, leading to the game no longer sending any requests but still acting like it's online. Like mentioned above, the game will only show (infinite) loading icons and no error messages. I can't reproduce this on my local instance, it only happens on Bonsai.
what i reached on my end did not look like a ratelimit from the server, it seems to be really random and more like a game bug, i was able to reproduce it inconsistently on my instance
this could be a separate issue i think still related
The server rate limits the login requests for me because once the game starts spamming them, it does one per ~30 seconds. The server generally rate limits game login requests once a user exceeds 10 per 5 minutes. You're not hitting the rate limit because they're happening more rarely for you. Also for me the server never responds with 403, all requests which require authentication are successful. So idk, but my guess is for you the game starts to send invalid tokens, leading to the server responding with 403 and the game trying to reauthenticate because of that (which LBP does for most requests if the server responds with 403 to them). For me the game for some reason tries to reauthenticate without receiving 403 prior. This is really weird.
Maybe this could be related to Bosnai's responses not containing the X-Original-Content-Length, Vary and Content-Encoding headers, which DeflateMiddleware would normally add when non-asset game responses become too large? My instance seems to set them fine, but they're missing for Bonsai.
Could be a Cloudflare configuration error, or something happening during ingress.
I'll try and capture some traffic and see if the headers are there.
no idea which change over the past month but it seems to no longer happen for me on my instance