this post was submitted on 11 Feb 2025
10 points (100.0% liked)

Lemmy Apps

6056 readers
33 users here now

A home for discussion of Lemmy apps and tools for all platforms.

RULES:

An extensive list of Lemmy apps is available here:

LemmyApps.com

or lemmyapps.netlify.app

Visit our partner Communities!

Lemmy Plugins and Userscripts is a great place to enhance the Lemmy browsing experience. [email protected]

Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. [email protected]

Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. [email protected]

Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. [email protected]

founded 2 years ago
MODERATORS
[email protected]
10
lemmy.ml: 403 Forbidden (lemmy.ml)
submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]
5 comments fedilink hide all child comments
 

Does anyone know why I'm getting this when making requests to the lemmy api?

<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>

The request in quesiton is a GET request to https://lemmy.ml/api/v3/post/list?community_name=asklemmy. It only happens when making the request to lemmy.ml, not to other instances. When I paste the url into my browser address bar it works.

top 5 comments
sorted by: hot top controversial new old
[–] [email protected] 5 points 2 months ago (1 children)

All I know is that nothing of value is lost.

[–] [email protected] 7 points 2 months ago (1 children)

Just like nothing of value was gained from either of our comments.

[–] [email protected] 2 points 2 months ago

You're right. I just couldn't contain myself...

[–] [email protected] 4 points 2 months ago* (last edited 2 months ago) (1 children)

Well, you've got a good and a bad case. So you probably have all the parts you need to solve the puzzle.

So the next step is probably to narrow down what precisely it is that breaks it.

I'd probably see what headers are being sent for each of your requests, since that's a source of difference, and then add them in one by one to the non-working case until it starts working.

I mean, could be anything. Could be that they restricted the User-Agent of the client you're using for the request due to someone spamming them or something.

[–] [email protected] 1 points 2 months ago

Good point. Yeah, I guess I just have to narrow it down from here.