![]() I'll try to find and test older versions of Tor next. ![]() (Note that CIS does not (and apparently cannot) disable Windows Defender Firewall.)įWIW, I tested several more browsers in the Container and they worked OK: Brave, Chrome, IceDragon, Maxthon, SeaMonkey and Vivaldi. I don't know why this is a problem only when Tor is run in Comodo's container, though.īut Tor v11 (both stable and alpha) still doesn't work in the container. Its log also claimed traffic from Tor on that port was getting through. I also added a rule to Comodo's Firewall to explicitly allow traffic in and out on that port, although that probably wasn't necessary. Check your Internet Connection if it says Offline. The Connection Assist informs you about the state of your Internet connection if you click on Test. If your connection to the Tor Network is not established and it reads Offline the following steps can be helpful. ![]() Windows Defender Firewall's log file then claimed that it was getting through. Check your Internet Connection if it says Offline. I created an inbound rule and an outbound rule to allow that traffic. I suspect other network related programs do, too. The Tor browser uses the localhost address. The log file didn't show any other traffic being dropped. Tor Browser is built using Firefox ESR, so errors regarding Firefox may occur. I enabled Windows Defender Firewall logging and discovered that it was dropping both inbound and outbound traffic for the IP address 127.0.0.1 (localhost) A problem found, but Tor browser v11 still doesn't work: If selected, every time you open Tor Browser, it will try to connect with your previous network settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |