Yeah I have the same problem.
Twitter always shows a connection error even if it's completely fine (cf images)

Trying with a proxy still the same problem

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

"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

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

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

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.