Twitter API returns 404, downloading from it is broken #318

Closed
opened 2025-11-09 09:46:08 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @wukko on GitHub (Jun 15, 2024).

twitter's graphql api started returning 404 on every request from cobalt a few hours ago. all instances are affected.

update: the issue is not with request itself, same exact request works fine when done with curl. could be something related to fetch/undici?

Originally created by @wukko on GitHub (Jun 15, 2024). twitter's graphql api started returning 404 on every request from cobalt a few hours ago. **all instances are affected**. **update:** the issue is not with request itself, *same exact request* works fine when done with curl. could be something related to fetch/undici?
GiteaMirror added the bughelp wanted labels 2025-11-09 09:46:08 -06:00
Author
Owner

@Yumega commented on GitHub (Jun 15, 2024):

Both Instagram and Twitter are out of work

@Yumega commented on GitHub (Jun 15, 2024): Both Instagram and Twitter are out of work
Author
Owner

@lostdusty commented on GitHub (Jun 15, 2024):

instagram is not related to this; instagram also works, but cobalt can't get all links due of instagram/profile restrictions

@lostdusty commented on GitHub (Jun 15, 2024): instagram is not related to this; instagram also works, but cobalt can't get all links due of instagram/profile restrictions
Author
Owner

@wukko commented on GitHub (Jun 15, 2024):

turns out twitter blocked nodejs TLS client fingerprint, this is why curl worked fine while fetch got 404. now cobalt randomizes it just like chrome :)

@wukko commented on GitHub (Jun 15, 2024): turns out twitter blocked nodejs TLS client fingerprint, this is why curl worked fine while fetch got 404. now cobalt randomizes it just like chrome :)
Sign in to join this conversation.