-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Torpy not working on windows: socket.timeout: timed out / [WinError 10054] #20
Comments
Update: Working again but sometimes still displaying the same issue as in #19 : "unknown document received":
|
Update 2: It's really odd, sometimes it's only working on Windows, sometimes only on Ubuntu. Does anyone have an idea where the OS differences come from? |
I have a newly setup windows 10 installation and it returns a very similar error when I run your code block:
Does it currently work on Ubuntu for you? |
Around 18 hours ago it only worked on Windows and not on Ubuntu. Otherwise until now I noticed it generally works better on Ubuntu (if it works at all). |
Because of errors and not optimal logic inside torpy tor authority server was under high traffic load. And was trying to block torpy. See https://gitlab.torproject.org/tpo/core/tor/-/issues/33018 for details. 445bc22 should fix this |
do you guys still have the same issue ? |
Tor V2 is deprecated, this library won't work until it supports Tor V3 |
Torpy is not running anymore on Windows. The following minimal example always results in a timeout.
Returns:
If on Jupyter, it returns the Windows Error code as well
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
The text was updated successfully, but these errors were encountered: