-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
TOR not working #104
Comments
First, check if you are using the proxy profile. A black or grey icon indicates that you are using direct/system profile instead of the profile you want. Use the dropdown menu to switch among proxies. You can also inspect the effective proxy settings at the URL |
|
I can also email you the .json if you want. |
@lemixtape Please upload the backup file to https://gist.github.com and paste the link here. |
Also, could you check |
Here are the two dumps you wanted: |
@lemixtape I'm sorry, but does Also, are you really using SwitchyOmega? (SwitchyOmega, not SwitchProxy)
|
I am using SwitchyOmega, yes. Here are the settings: Effective proxy settings Proxy server for everything else: socks5://127.0.0.1:9051 Please let me know if you need anything else. |
@lemixtape The proxy settings are showing you are already using the socks5 proxy as you want. Or, is it a problem with the TOR software or network? |
The problem is not with TOR software or the network as I did not change them. The only change I made to my system was moving from SwitchProxy to SwitchyOmega. Chrome tells me that I have a network issue i.e. that I am not connected to the Internet. Is there any other metric I can share with you? |
Please open any website. When Chrome shows you an error page, click on the "More" button to expand the details. Then you can just copy and paste the error message (or error code) here. |
I meet the same problem. when the extension in auto switch mode it fails. chrome error msg: This webpage is not available Hide details here is my config exported:
|
Here it is, sorry for the delay: |
@horsley Your issue is different than OP's. Please open a separate issue for that. @lemixtape I'm pretty sure a ERR_TIMED_OUT can only be caused by your network (or TOR) and is not related to this project. |
@lemixtape Tor's proxy port is usually 9050, not 9051. |
I was using SwitchProxy to connect to the TOR network using the Vidalia client and all was working fine. Ever since I moved to SwitchyOmega, it is not possible to connect to TOR.
I am sending the requests through SOCKS5, 127.0.0.1:9051.
The text was updated successfully, but these errors were encountered: