First make sure your clock, date, and timezone are set correctly.
Also check the log for any issues.
Many sites has gone down, and are not online anymore that are linked to all over the place.
Then try some of the sites that are hosted by big providers with the most amount of uptime.
Some examples are:
If these sites work, then I'd ...
Error 403 and CAPTCHA are appearing because the exit node you're using is not dedicated to you only: Many people are using it, including to access Google and other services.
It seems - on a website server's side - that one single IP address (the exit node) generates too many requests per time and a different requests/user sessions, so it can interpret it as ...
but almost every single onion site
If you can connect to one .onion address, then there is no reason on your end why you could not connect to all of them.
The Hidden Service itself could be down or overwhelmed. (Or moved on to a new .onion address)
If the above doesn't work, here are the longshots:
Try using a different computer. It could be a configuration error. While most issues stem from the clock/date/timezone as mentioned above, it could be something unforeseen. Never hurts to check. Try a library.
If that fixes it, double-check your requirements and try posting your log. There might be ...
You're starting it wrong. You perhaps want service tor start, depending on your OS.
What you're doing here is running Tor, as root, with commandline arguments of --service start. Tor has never heard of the --service option, so it says so and closes.
(That said, my guess is that your underlying problem is that your Tor daemon doesn't have permission to ...
It's a big probability that it was a clock skew: on reboot many OS'es and distro's are updating the local time using NTP protocol, so - once you've got rebooted you had an accurate time and was able to join the network successfully.
How did you upgrade? The directory layout of the Tor browser bundle has changed in version 4.0, so extracting the new bundle over the old directory probably won't work. (Instead move or delete the old directory and reextract version 4.0)
Tor needs an accurate clock to work correctly.
Please sync your time with an NTP (Network Time Protocol) server.
On Debian based machines use package ntpdate.
sudo ntpdate -v pool.ntp.org
w32tm /config /syncfromflags:manual /manualpeerlist:pool.ntp.org
w32tm /config /update
As per this suggestion
ifconfig lo up
and everything worked. I have zero clue what this does, and if someone writes this up better I will accept their answer, but until then I will leave this here to hopefully help people with the same problem
I only find links to a site that is no longer available
Are you running on a "virtual server" by any chance?
leads to 404
then another google gives in Tor installation guides :
Pay attemption in the URL that you are trying to access.
If the end has a ".city" (i.e.: afksldhfkhkejhks.onion.city/main_page/)in the URL's end, just delete the ".city" and retry.
Onion City is a mechanism to turn .onion sites accessible trough the clearnet via an unconfigured browser.
But the service is hosted in the (opressive) USA, so, they will deny ...
Sounds like shenanigans, but on whose end I'm not sure.
Find another computer, like in a public library.
Download Tor Browser Bundle again (from here: https://www.torproject.org/projects/torbrowser.html.en)
Open it and go to a reliable hidden service (Ahmia Tor Hidden Service Search: http://msydqstlz2kzerdg.onion/search/)
If this solves the issue, try ...
This is a linker error, meaning you're (probably) missing a library that's required for Tor to build properly.
Undefined symbols for architecture x86_64: "_SSL_set_session_secret_cb", referenced from: _tor_tls_new in libor-crypto.a(tortls.o)
These mean that the Tor code is trying to use _SSL_set_session_secret_cb, _EVP_aes_128_ctr, ...
What you downloaded is a DMG — a disk image. When it opens, it is a read-only filesystem like a CD or DVD. You have to copy the application out of the DMG before you can run it.
And then you have to run it on the same account that copied it out of the DMG, because it has to write to a file that is inside of the application. So, each user that is going ...
The "owner" conditional, as per the AppArmor wiki:
The owner keyword is used to make the rule conditional on object ownership. Specifically the task must have the same euid/fsuid as the object being referenced by the permission check.
The problem seems to be that the user that tor is running as (debian-tor is the default on ubuntu and other debian ...
It's trying to lookup a relay that seems to no longer exist, specifically whatever relay corresponds to the 58......88C fingerprint.
It's possible that it does still exist, it just wasn't found on the directory provided by x.x.x.x.
This error is just a warning, it's not a fatal error and Tor will continue to function normally if it's the only error you've ...
If you want to use Tor Browser's Tor instance you'll have to use TorPort 9150. Alternatively, you can install a global Tor instance.
This doesn't work if you're running the alpha version of Tor Broswer on a Unix-like system, it uses a Unix socket instead. You should also expect the stable series to switch to Unix sockets before long.
In another question you try to find the torrc for Tor Browser, if this is being run in a Tor Browser context then the directory likely won't exist and the tor process itself (running as your user) wont have the privileges to create it.
You should instead use a directory path that your own user could create/control instead of /opt/local/, second of all if, ...
These are threads, this is normal.
They're not multiple instances of firefox but instead a single instance that has multiple threads created for it. This may be more apparent if you press F5 to view it as a tree, you will see a main firefox instance with multiple children.
When a process wants to run tasks in parallel it will often create a new thread. The ...
Never run it as admin, nothing in Tor Browser requires administrator privileges. Running it as administrator greatly increases the damage that could be done if your browser was compromised.
The problem is where you are extracting Tor Browser to. Directories like C:\, C:\Program Files\ or C:\Program Files (x86) all have administrator requirements to edit (...
AVG deleted my Tor executable a few days ago. Just download the package and unzip, etc., again and see what happens. I told AVG to ignore it. I haven't had a problem with any scans since then, although I still do not know why AVG picked up on it in the first place. I've been using Tor for a few years.
OK solved the problem after a thorough research.
This update was required:
Update for Desktop Experience Decoder for Windows Server 2008 R2 (KB2483177)
Please file a ticket with code and the descriptor that reproduces this. You're right that the RouterStatusEntryV3 class has a measured attribute. First guess is that you might have a RouterStatusEntryV2 instance instead.
The problem is not with your firewall - your computer is only talking to the tor network.
The tor exit nodes actually access the servers you're asking for, and some of them refuse to accept connections from exit nodes (for whatever reason). That, or slow tor nodes on your path, causes this message. (I often get this for duckduckgo.com.)
I'm assuming you're trying to access hidden services.
It's pretty common for hidden services to be down and sites like the hidden wiki reporting them as still active.
If I'm right then there's nothing you can do about it, sadly, except waiting to see if they come back online later.