Same errors as before here. Sorry Ched!
API returning broken responses at random
Started by Omanpx [1906686] on in Bugs & Issues.
Posts archived: 49 / 49 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Same issues on my side.
Latest occurence 1mn ago:
2024-03-19T17:37:28.1972581Z
Latest occurence 1mn ago:
2024-03-19T17:37:28.1972581Z
I'm not sure if this could be an IP address related issue, but after back-to-back errors, I tried the same calls using Cloudflare WARP, and the errors disappeared.
Fetheryhorse6 [2317488] had the same issue last night and tried using a VPN, and the errors were gone for him too.
Fetheryhorse6 [2317488] had the same issue last night and tried using a VPN, and the errors were gone for him too.
Mentions: Fetheryhorse6 [2317488]
I do seem to be getting a lot more errors on one machine than the other.
[image: cdn.discordapp.com]
Yeah, still broken (PS that's a deleted key, don't bother ;P)
Above was just on the try it page, so nothing else weird going on there. Chrome
Yeah, still broken (PS that's a deleted key, don't bother ;P)
Above was just on the try it page, so nothing else weird going on there. Chrome
Experiencing the same. Looking at the headers doesn't tell me anything, as everything except for the expected things (cf-ray and date) stayed the same.
It's almost like if there was encryption in the result... Maybe someone enabled zip compression on a specific machine API endpoint config to reduce bandwidth? ;)
If someone can reproduce this are they able to capture a full HAR file with the request and response please?
https://developers.cloudflare.com/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/
You can email this to alex@torn.com. Please sanitize it to remove your session IDs (see the blog above)
https://developers.cloudflare.com/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/
You can email this to alex@torn.com. Please sanitize it to remove your session IDs (see the blog above)
Sent one, believe I correctly sanitized it.
Sent
^^ Thanks, i've got a handful of users - no need for more HAR files from new users (i'm emailing some of those users directly to ask for more tho!)
Its possible I have pushed a change that fixed this.
Thank you! Seems to be working much better.
Working perfectly here now!! Tyvm!
Sorry no screen shots as I am at work, however issue still persists
It's fixed on my side.
Thx for handling this quickly, as always.
Thx for handling this quickly, as always.
Everything seems good on my end. Ive had my sheet updating once a min for the last hour and haven't caught an error. Last one I see in logs was at 19:57:21tct
Also OK for me -- thanks Davzz
API LEVEL Error?
I think you have an entirely seperate issue there. Its saying that the API key access level is not right?
I think you just need to use an API key with a higher level of permission.
AKA Public < Limited < Full
Is my best guess as to why its fixed for everyone else. Unless i'm reading this wrong.
I think you have an entirely seperate issue there. Its saying that the API key access level is not right?
I think you just need to use an API key with a higher level of permission.
AKA Public < Limited < Full
Is my best guess as to why its fixed for everyone else. Unless i'm reading this wrong.
Yup dire is right. If its a level error or this:
16 => Access level of this key is not high enough : A selection is being called of which this key does not have permission to access.
That means you are not using a key that has the correct level of permission to access whatever your trying to.
This thread was about JSON parse error/Invalid JSON error, cause by the api returning junk data like this:
[image: cdn.discordapp.com]
which has seemingly been resolved.
16 => Access level of this key is not high enough : A selection is being called of which this key does not have permission to access.
That means you are not using a key that has the correct level of permission to access whatever your trying to.
This thread was about JSON parse error/Invalid JSON error, cause by the api returning junk data like this:
[image: cdn.discordapp.com]
which has seemingly been resolved.