Internal HTTP (authentication?) failures (InsertService, MarketplaceService, etc)

Bug Reports Engine Bugs
#1

We are getting various internal (i.e. Roblox API-related) errors related to HTTP requests (possibly authentication-related?). This is affecting us mostly in the form of InsertService calls that are failing (when it errors, that specific asset cannot be loaded into that server).

The first time an ID fails to insert via InsertService:LoadAsset, we get this error:
User is not authorized to access Asset.
while subsequent calls to insert the same ID fail with this error:
Temp read failed.

We have seen some other errors, including:
Exception in place validation: std::exception
Error fetching MarketplaceService receipts: HTTP 403 (Forbidden)
loadChatInfoInternal had an error: HTTP 403 (Forbidden)

DataStore calls seem to be unaffected as far as I can tell.

If a server gets an InsertService error, it is rendered completely broken (because of how our game is designed). We have noticed it specifically in VIP servers (because those close and launch more frequently), but it might be a problem in all servers.

We have not published any changes to the game and started noticing it within the last hour or two.

4 Likes
Massive surge in HTTP 403 forbidden errors
#2

1 Are you trying to insert free model or something that’s not Roblox’s item?
2 are you sure your game setting have Https service on?

#3
  1. They are assets owned by the same group the game is published under
  2. Yes.

This is not failing on every call. This is a game that was operating perfectly (with regard to these API calls) yesterday, and is still mostly working today. It is intermittent.

3 Likes
#5

I’m seeing a small number of these in my sentry logs:
only 12 in the last 24 hours from 5k players:
HTTP unknown error (HttpError: Timedout)
Stack:
CoreGui.RobloxGui.Modules.SocialUtil, line 112

and 2 of these:
HTTP unknown error (HttpError: ConnectFail)
Stack:
CoreGui.RobloxGui.Modules.SocialUtil, line 112

doesn’t appear to me negatively impacting my players, they seem to be remaining connected and playing after the error reports.