Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[-] Twitter: Error Connecting #1933

Open
5 tasks done
jlescalonap opened this issue Nov 3, 2023 · 5 comments · May be fixed by #2039
Open
5 tasks done

[-] Twitter: Error Connecting #1933

jlescalonap opened this issue Nov 3, 2023 · 5 comments · May be fixed by #2039
Labels
bug Something isn't working

Comments

@jlescalonap
Copy link

jlescalonap commented Nov 3, 2023

Checklist

  • I'm reporting a bug in Sherlock's functionality
  • The bug I'm reporting is not a false positive or a false negative
  • I've verified that I'm running the latest version of Sherlock
  • I've checked for similar bug reports including closed ones
  • I've checked for pull requests that attempt to fix this bug

Description

When queryng shows [-] Twitter: Error Connecting

DESCRIPTION
Twitter always have problems to connect, I´ve updated Sherlock re-cloned, tried many times but always shows that twitter has problems to connect.

@jlescalonap jlescalonap added the bug Something isn't working label Nov 3, 2023
@Piel-M
Copy link

Piel-M commented Feb 19, 2024

Yeah I have the same problem.
Twitter always shows a connection error even if it's completely fine (cf images)
Screenshot_2024-02-19-02-37-31-50_84d3000e3f4017145260f7618db1d683.jpg

IMG_20240219_023757.jpg

@joaomfbh
Copy link
Contributor

joaomfbh commented Mar 1, 2024

Trying with a proxy still the same problem
image

@joaomfbh
Copy link
Contributor

joaomfbh commented Mar 1, 2024

Doing a simple request with requests lib, I get the 400 status code and this message from content:

image
"Please switch to a supported browser to continue using twitter.com. You can see a list of supported browsers in our Help Center."

Following the link to the supported browsers: https://help.twitter.com/pt/using-x/x-supported-browsers

@joaomfbh
Copy link
Contributor

joaomfbh commented Mar 1, 2024

I found the problem. Just set a custom header with the User Agent parameter and the request will return 200 status code.

image

I'll work on a pr. Any idea to where to set this solution are welcome!

@joaomfbh
Copy link
Contributor

joaomfbh commented Mar 5, 2024

Of course the header has already implemented (silly me). So, investigating a little more I found that the front end alternative for Twitter, called nitter is dead and the Sherlock project are using in url prob request.

https://www.reddit.com/r/privacy/comments/1act8c5/nitter_is_dead/
zedeus/nitter#1155 (comment)

So, just making a direct request, without urlProbe param will work.

image

@joaomfbh joaomfbh linked a pull request Mar 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants