![]() it does not answers requests in the local network, and in any public IP address in the "regular" Internet. Now we can setup a web daemon to answer for that IP adress:port and only binding for localhost e.g. So actually, what you have configured now, is that all visits to in the Tor network to will be forwarded to a daemon listening to 127.0.0.1:80 (localhost:80) on your server. There appears to be scripts for getting (using brute force?) a slighter less random name, I got an impression the added complexity is not worth the extra effort. The names are generated in negotiation with the actual Tor network, which also explains why sites/services in the Tor network have such strange names. $sudo cat /var/lib/tor/www_service/hostname The hostname file has a somewhat random name inside, which is your address in the. The directory will be created automagically, and inside the new directory, two files are generated, hostname and private_key. onion service in the Tor network is as simple as editing /etc/tor/torrc and adding: HiddenServiceDir /var/lib/tor/www_service/Īfter restarting the tor service with sudo service tor restart Please make sure your clock is set accurately, including the correct timezone. If you see lines like this in your Tor log, it means your system clock is incorrect. Tor requires an accurate clock to work: please check your time, timezone, and date settings. 00:04:48.800 Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. 00:04:48.200 Bootstrapped 10%: Finishing handshake with directory server 00:04:48.000 Bootstrapped 5%: Connecting to directory server If you see lines like this in your Tor log, it means that Tor failed to complete a TLS handshake with the directory authorities. (DONE DONE count 10 recommendation warn host at :xxx)ġ3-11-17 19:53:49.300 10 connections have failed:ġ3-11-17 19:53:49.300 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKEġ3-11-17 19:53:49.300 1 connections died in state connect()ing with SSL state (No SSL object) Stuck at 10%: Finishing handshake with directory server. Common log error #3: Failed to complete TLS handshake 13-11-17 19:52:24.300 Bootstrapped 10%: Finishing handshake with directory serverġ3-11-17 19:53:49.300 Problem bootstrapping. Please try connecting with bridges, and that should fix the problem. This could mean that you’re on a network that’s censored. If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. 21:11:45 PM.300 Failed to find node for hop 0 of our path. 21:11:44 PM.500 Bootstrapped 85%: Finishing handshake with first hop 21:11:44 PM.300 Failed to find node for hop 0 of our path. 21:11:44 PM.300 Bootstrapped 80%: Connecting to the Tor network Common log error #2: Can’t reach guard relays 21:11:43 PM.500 Opening Socks listener on 127.0.0.1:9150 If a SOCKS proxy is not required, or you’re not sure, please try connecting to the Tor network without a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly. ![]() If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. 09:24:08.900 Proxy Client: unable to connect to xx.:xxxxx ("general SOCKS server failure") 09:23:47.900 Bootstrapped 10%: Finishing handshake with directory server 09:23:47.900 Bootstrapped 5%: Connecting to directory server Internationalization Support (i18n) Python Support. Session Support (Use Redis Storage) Cookie(Secure Cookie) Support. You should see one of these common log errors (look for the following lines in your Tor log): Common log error #1: Proxy connection failure 09:23:40.800 Opening Socks listener on 127.0.0.1:9150 Advanced web application based on Tornado. Or to save the logs to a file (default: tor-browser.log) If you don't see this option and you have Tor Browser open, you can navigate to the hamburger menu ("≡"), then click on "Settings", and finally on "Connection" in the side bar.Īt the bottom of the page, next to the "View the Tor logs" text, click the button "View Logs.".Īlternatively, on GNU/Linux, to view the logs right in the terminal, navigate to the Tor Browser directory and launch the Tor Browser from the command line by running: Then paste the Tor log into a text file or other document. ![]() If you’re having trouble connecting, an error message may appear and you can select the option to "copy Tor log to clipboard". Descarga Navegador Tor para experimentar navegación privada de verdad sin rastreo, vigilancia ni censura. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |