Who else is getting the 403-Blocked response on every request?

Reddit API

I'm getting 403 on every single request. Even if I add a new script app to a non-bot account, I get the 403 (via Snoowrap) response. Nothing seems to work. It started up this morning.

Posted Nov 29, 2021, 9:20 PM UTC

4330
umbrae•

Hey folks. We believe we've tracked down the issue that was impacting some of your bots. There may be some lingering 403 issues as we hash it all out over the next day or so, but if you see anything in particular let me know here.

11
AJohnnyTruantOP•

Thank you! Best of luck with squashing this. Are you able to disclose what the issue was after you’re finished? It seems to have been with NodeJS users, at least that’s the speculation around here

2
zoozla•

Seems to be working for me now, thanks u/umbrae!

2
techsin101•

created new app and still getting "BLOCKED"

1
Bspammer•

People are getting blocked again, seems like almost every firefox user judging by the speed this thread is growing: https://old.reddit.com/r/firefox/comments/s3zn2p/is_reddit_broken_on_firefox/

1
[deleted]•

[deleted]

1
[deleted]•

[removed]

3
[deleted]•

[deleted]

3
topofsocialmedia•

Same issue for me, it started this afternoon (~18:00 GMT), worked fine before.

Tried waiting a couple hours, rebooting my pc, new reddit dev app but nothing.
Using snoowrap v1.23.0 with Node.js, response body contains only the text "Blocked"

3
StreetEffective398•

I have a similar situation. I get a 403 (Blocked) response, but only on the first request, if I immediately send a second request, then everything works. What is the reason? (Node JS, axios and got)

3
tyler_church•

I was getting them earlier today but a restart of my Node.js process fixed it 🤷‍♂️

2
[deleted]•

[removed]

2
AJohnnyTruantOP•

I dove into it and ran new node processes to try to figure out what’s going on, no dice. I even tried a new script bot. Same thing.

2
[deleted]•

[removed]

2
AJohnnyTruantOP•

Tried my VPN, tried a new user agent, tried a new script bot entirely, tried using Oauth tokens. It seems fully blocked out from my vantage point on all things node

1
FoxxMDContextMod•

This seems to start with the modmail issues this morning. I can confirm now (7pm EST) that I have access to the api again (no longer getting 403)

EDIT: back to 403'ing at 8:30pm

2
[deleted]•

[deleted]

2
Hot_Humor9532•

Oh boy and I thought I am getting insane. Trying to fix this by rewriting my script the tenth time now and still nothing.

Doesn't make a difference if I use snoowrap or access the json directly.

Hope this will get fixed but good seeing I am not the only one.

2
cgtinker•

facing the same issue since last week. didn't use my scripts for some time..

1
zoozla•

I'm facing the same issue, nothing helps - creating a new app, restarting node, running under different users. Looks like we're back in stoneage for a while.

1
kombuchafueled•

i'm calling the API via firebase cloud functions (not Snoowrap, but also NodeJS) and have the same issue – 403 with an error message of "Blocked"

1
hallofstairs•

Best of luck!

2
kombuchafueled•

Thank you brother

1
OmgImAlexis•

Same here. Seemed to be working for a few hours and now it's broken again.

Guessing it's related to the devs fixing the modmail. Would be nice to see an admin say if that's the case.

1
[deleted]•

[deleted]

1
simulation_goer•

Same here. Not even the RSS feed is working, 403s all across the board

1
cgtinker•

I had the same issue and it was due to missing flairs.

Many subreddits require a flair id now. Also many subreddits don't give you access to their flairs (the following code may results in 403 error)
reddit.subreddit("NAME").flairs()

By accessing an old submission I was able to get the available flairs of the subreddit:
submission.flair.choices()

Adding the submission id to my submission solved it for me.
Dunno if that's your problem swell.

1
StellarTabi•

Good to see it's not just me. I guess it'll get fixed soon?

1
AJohnnyTruantOP•

It happened right after I pushed a commit. And I was ripping my hair out like I TESTED ALL OF THIS!! Terrible timing for my sanity. I couldn’t find anyone talking about it here or on GitHub. Hopefully this post saves some brain cells for people

3
dedmercy•

Yes happening to me too. Even a normal fetch to subreddit.json is returning 403. But it does provides response sometimes. It feels like it is trying to block the request but fails sometimes.

1
JBHUTT09•

I'm getting this all of a sudden on my main account in Firefox. I'm able to load reddit through Chrome (how I'm commenting).

1
fistful_of_ideals•

Ditto, Firefox is bricked, Chrome works.

1
JBHUTT09•

Okay, so it's not just me. That's good. I submitted a post in r/bugs if you want to chime in there, too:

https://www.reddit.com/r/bugs/comments/s3zqon/403_blocked

1
fistful_of_ideals•

Looks like we're back in bidness. Thanks for the report!

2