Tor exited during startup this might be due to an error in your torrc file - Исправление ошибок и поиск оптимальных решений проблем

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

Closed

birdofprey opened this issue

Dec 18, 2020

· 3 comments

Comments

OS：Debian Gnu/Linux 10.7
Tor: 10.5a6
error:
Tor exited during startup. This might be due to an error in your torrc file, a bug in Tor or another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start.

I updated to Tor ver. 11.0.3 on Microsoft Windows [Versión 10.0.19044.1415], no logs, no errors, only in console browser:
«Could not load engine blockchair-onion@search.mozilla.org: Error: Extension is invalid SearchService.jsm:609:17
Resource of root-node was not found. 2 resource-command.js:724:17
Tried to send a ‘target-destroyed-form’ event on an already destroyed actor ‘watcher’ Actor.js:58:15
Error: _initWorker called too early! Please read the session file from disk first. SessionFile.jsm:375:15
NS_ERROR_CONNECTION_REFUSED: Component returned failure code: 0x804b000d (NS_ERROR_CONNECTION_REFUSED) [nsIScriptableInputStream.available] tor-control-port.js:81
onInputStreamReady resource://torbutton/modules/tor-control-port.js:81
«

Related with: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40679

on macOS : delete lock folder in
~/Library/Application Support/TorBrowser-Data/Tor/
it. will solve the issue

Источник

Содержание

Tor exited during startup. This might be due to an error in your torrc file, a bug in Tor or another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start. #541
Comments
Footer
Linux Mint Forums
Tor Browser Refuses to Start No Matter the Download Format
Tor Browser Refuses to Start No Matter the Download Format
«Tor exited during startup» on fresh install
Summary
Steps to reproduce:
What is the current bug behavior?
What is the expected behavior?
Environment
Relevant logs and/or screenshots
Additional context
Tor exited during startup. #403
Comments
Tor Browser 6.5a3 is released
Comments

Tor exited during startup. This might be due to an error in your torrc file, a bug in Tor or another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start. #541

The text was updated successfully, but these errors were encountered:

on macOS : delete lock folder in

/Library/Application Support/TorBrowser-Data/Tor/
it. will solve the issue

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Tor Browser Refuses to Start No Matter the Download Format

Post by Zickamenx » Sun Nov 08, 2020 5:04 am

Hello, everyone. This is my first post here, so I apologize if I’m doing this wrong. I did find one or two other posts on the forums about the Tor Browser, but none seem to tackle this particular issue. In case it matters, I am presently dual-booting Linux Mint 20 64-bit with Windows 10; I’m a relative Linux newbie, having only tried one distro before this one. In any case.

I downloaded the Tor browser some time ago using the official tarball. It was working well at first, but started running slowly; as a result, I deleted the files in the directory into which I extracted said tarball, and sought to perform a fresh install, just in case that would help. However, upon learning that the Mint repositories feature the Tor Browser Launcher, I figured I would give that a try; the download went smoothly, and I ran the launcher in the normal way.

Unfortunately, that was when things started to go south, as I was met with the message: «Tor exited during startup. This might be due to an error in your torrc file, a bug in Tor or another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start.»

I attempted to reinstall the launcher through the option in its accompanying settings file, yet this did nothing. I uninstalled the launcher, then attempted to re-download it directly through the software manager, thinking I may have borked the installation somehow; yet the problem persisted. I tried uninstalling that, only to try the tarball one more time. No luck. I should note that in all cases, I made sure to perform

just to be sure.

After doing some research, I figured out that system clock issues can stop Tor from opening properly; since I was having some issues with my system clock between OSs, I figured I should check that first. After having tried Tor via both Local and UTC timezones, using

I have still had no success.

I also attempted to check if there were permission issues via ls -l (though I only tried this with the most-recent tarball), as this is apparently a common problem, too. However, this does not seem to be a problem, as it seems not to be installed under root. Weirdly, however, the date provided for said file seems to be wildly outdated:

I’m starting to get pretty disheartened by this point. Any assistance would be appreciated. (I’m particularly worried that all the successive installations might have created conflicting files, partial updates, or something.)

Источник

«Tor exited during startup» on fresh install

Summary

I encounter «Tor exited during startup» error even on a fresh install of Tor Browser and profile.

Steps to reproduce:

Clean all existing installs and profiles of Tor Browser
Download the latest stable version of Tor Browser
Run start-tor-browser

What is the current bug behavior?

The following message is displayed, and Tor Browser cannot open webpages:

Tor exited during startup. This might be due to an error in your torrc file, a bug in Tor or another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start.

What is the expected behavior?

Tor should not crash.

Environment

OS: Arch Linux x86_64
Tor Browser version: Both 11.5.2 (stable) and 12.0a3 (alpha) do not work.
Installation method: Running directly from torproject.org’s binary tarball, installing tor-browser AUR package, and using torbrowser-launcher all do not work.

Relevant logs and/or screenshots

I have checked the «View the Tor logs» in Tor Browser and the console, but there is no log.

Additional context

Yesterday I can still use Tor Browser without any problem, and Tor Browser is connected to Tor network directly (no bridge is used, ISP is not censoring Tor).
However, today Tor Browser suddenly cannot start Tor (even though I haven’t updated any packages). I tried using bridges, using Tor Browser over VPN, and running a fresh install of Tor Browser, but it is still not working.

Running ./tor in the tarball returns ./tor: symbol lookup error: ./tor: undefined symbol: evutil_secure_rng_add_bytes .

If I follow the «Using a system-installed Tor process with Tor Browser» section in the start-tor-browser script, then Tor Browser can open webpages.

Источник

Tor exited during startup. #403

Hello there, I’m receiving the following error message trying to start the Tor Browser:

Tor unexpectedly exited. This might be due to a bug in Tor itself, another program on your system, or faulty hardware. Until you restart Tor, the Tor Browser will not be able to reach any websites. If the problem persists, please send a copy of your Tor Log to the support team.

Restarting Tor will not close your browser tabs.

There’s a button under it, Restart Tor. Clicking on it flashes the window (it must have closed and reopened quickly). Also, there’s another button Copy Tor Log to Clipboard Clicking on it makes the following message appear:

Copy complete. 0 Tor log messages are ready to be pasted in a text editor or an email message.

Alongside this window there is another one where it reads,

Tor exited during startup. This might be due to an error in your torrc file, a bug in Tor or another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start.

There are two buttons in this window, Ok and Restart Tor. Clicking on either one dismisses the window.

I tried reinstalling the Tor Browser using torbrowser-launcher —settings , but got the same results.

Specifications

Tor Browser Launcher version: 0.3.1-2
OS: Linux parrot 5.1.0-parrot1-3t-amd64 #1 SMP Parrot 5.1.3-1parrot1.3t (2019-05-20) x86_64 GNU/Linux

The text was updated successfully, but these errors were encountered:

Источник

Tor Browser 6.5a3 is released

by boklm | September 20, 2016

Tor Browser 6.5a3 is now available from the Tor Browser Project page and also from our distribution directory.

This release features important security updates to Firefox including the recently disclosed extension update vulnerability. All users should upgrade as soon as possible.

This release bumps the versions of several of our components: Firefox to 45.4.0esr, Tor to 0.2.9.2-alpha and OpenSSL to 1.0.2h, HTTPS-Everywhere to 5.2.4, NoScript to 2.9.0.14. Additionally we are adding Unix Domain Socket support on Linux and OSX, the about:tbupdate page giving information about the update has been improved, the referrer spoofing for .onion domains has been moved from Torbutton to C++ patches.

Note: Due to bug 20185 Tor Browser on Linux and OS X will not work correctly if the path where it is installed is too long. As a workaround you may need to move it to a directory with a shorter path.

Update (9/22 07:15 UTC): We got reports about updates failing on OS X systems. We are still investigating the problem but this is likely due to a combination of issues. For one we might have introduced a permission problem by trying to get our incremental updates working again. Secondly, unix domain socket paths for the control port that contain spaces are not working. See comment 5 in bug 20210 for a preliminary analysis and workarounds. We are sorry for the inconvenience.

Here is the full changelog since 6.5a2:

All Platforms
- Update Firefox to 45.4.0esr
- Update Tor to 0.2.9.2-alpha
- Update OpenSSL to 1.0.2h (bug 20095)
- Update Torbutton to 1.9.6.4
  - Bug 17334: Move referrer spoofing for .onion domains into tor-browser.git
  - Bug 17767: Make «JavaScript disabled» more visible in Security Slider
  - Bug 19995: Clear site security settings during New Identity
  - Bug 19906: «Maximizing Tor Browser» Notification can exist multiple times
  - Bug 19837: Whitelist internal URLs that Firefox requires for media
  - Bug 15852: Remove/synchronize Torbutton SOCKS pref logic
  - Bug 19733: GETINFO response parser doesn’t handle AF_UNIX entries + IPv6
  - Bug 14271: Make Torbutton work with Unix Domain Socket option
  - Translation updates
- Update Tor Launcher to 0.2.10.1
  - Bug 14272: Make Tor Launcher work with Unix Domain Socket option
  - Bug 19568: Set CurProcD for Thunderbird/Instantbird
  - Bug 19432: Remove special handling for Instantbird/Thunderbird
  - Translation updates
- Update HTTPS-Everywhere to 5.2.4
- Update NoScript to 2.9.0.14
- Bug 14273: Backport patches for Unix Domain Socket support
- Bug 19890: Disable installation of system addons
- Bug 17334: Spoof referrer when leaving a .onion domain
- Bug 20092: Rotate ports for default obfs4 bridges
- Bug 20040: Add update support for unpacked HTTPS Everywhere
- Bug 20118: Don’t unpack HTTPS Everywhere anymore
- Bug 19336+19835: Enhance about:tbupdate page
Android
- Bug 19706: Store browser data in the app home directory
Build system
- All platforms
  - Bug 20133: Don’t apply OpenSSL patch anymore
  - Bug 19528: Set MOZ_BUILD_DATE based on Firefox version
- OS X
  - Bug 19856: Make OS X builds reproducible again
  - Bug 19410: Fix incremental updates by taking signatures into account

Please note that the comment area below has been archived.

Источник

Fix Problem has occurred and the system can’t recover in Linux

You probably came across this error after upgrading packages or performing a full system upgrade. This could probably be termed as the “black screen of death” in Linux operating systems. This exception is thrown immediately after the boot process ends, when the ‘Gnome Display Manager’ is being loaded to display the login screen. The error is as a result of an error in configuration of unpacked packages!

NOTE:// For purposes of proof of concept, I use the famous Kali Linux OS. This however, doesn’t mean that this concept cannot be applied to other Linux OSs. What will vary in case of a different Linux OS is the commands!

This error to most means that they have to reinstall Kali Linux from a USB stick all over again, losing all their data. Data loss is probably one of the most painful feelings that one can experience, knowing that all your meticulously consolidated data is just gone. Gone!. Word of Advice: Always Backup your data Regularly! In case a backup exists, even reinstalling a fresh Kali distro is one of the viable options!

Fortunately, instead of going through all the trouble of a fresh installation, you could just find a way around this error. Follow the stepwise instructions to land at your Desktop again. Trust me, there will be no better feeling in that moment!

Step 1: Recovery Mode

When you install Linux operating systems, they come bearing recovery options. In case of Kali Linux, the recovery mode can be found under: ‘Advanced options for Kali Linux/GNU Linux’

Click on the option with ‘Recovery Mode‘, to boot to Kali Linux Recovery Mode.

NOTE:// After successfully booting to the Recovery Mode, note that there is No GUI, so you are limited to the “TeleTYpewriter” or “TTY“, which means that all operations are done via text commands. Worry Not, if you haven’t interacted with TTYs before, because all you need to fix the error is in this article.

Step 2: User Password in TTY

The first thing that you are prompted for in the TTY recovery mode is the user Password, which you must enter correctly before proceeding.

NOTE:// After entering the correct password, the next thing you note is that you are actually in a Terminal session. Therefore, you can enter any commands here as you would in the normal terminal, which is the direction we will take from here (Terminal Commands).

Step 3: Fixing the Error

Enter the following commands in the order they appear!

NOTE:// The sudo prefix can be omitted if you are working in a ROOT session!

This command configures all packages that have been unpacked but are unconfigured.

This command attempts to perform a full system upgrade.

This command attempts to fix a system that has existing broken dependencies.

Step 4: Confirming that the Error was fixed

After the step above, the error “Oh no! Something has gone wrong. A problem has occurred and the system can’t recover. Please contact a system administrator”, should be fixed.

To confirm this, we need to shutdown the system and then boot into the normal Kali Linux boot option. To shutdown in TTY, use the command:

The boot process should now go through to display the login screen, and after entering the correct details (username && password), you should land in your desktop.

«Tor exited during startup» on fresh install

I encounter «Tor exited during startup» error even on a fresh install of Tor Browser and profile.

Steps to reproduce:

Clean all existing installs and profiles of Tor Browser
Download the latest stable version of Tor Browser
Run start-tor-browser

What is the current bug behavior?

The following message is displayed, and Tor Browser cannot open webpages:

Tor exited during startup. This might be due to an error in your torrc file, a bug in Tor or another program on your system, or faulty hardware. Until you fix the underlying problem and restart Tor, Tor Browser will not start.

What is the expected behavior?

Tor should not crash.

Environment

OS: Arch Linux x86_64
Tor Browser version: Both 11.5.2 (stable) and 12.0a3 (alpha) do not work.
Installation method: Running directly from torproject.org’s binary tarball, installing tor-browser AUR package, and using torbrowser-launcher all do not work.

Relevant logs and/or screenshots

I have checked the «View the Tor logs» in Tor Browser and the console, but there is no log.

Additional context

Running ./tor in the tarball returns ./tor: symbol lookup error: ./tor: undefined symbol: evutil_secure_rng_add_bytes .

If I follow the «Using a system-installed Tor process with Tor Browser» section in the start-tor-browser script, then Tor Browser can open webpages.

Vidalia: «Tor is not running»

I then started Vidalia and it said Tor is not running including an error message saying that Vidalia was unable to start Tor.

I searched a bit and I’ve found out that the problem can be that Tor is already running when Vidalia gets started.

These were my further steps:

Removed Tor from the runlevels

Killed all Tor processes

Vidialia still displayed the same error messages upon starting it.

The path to Tor in the settings should actually be correct:

I verified its existence.

However, I cannot click OK in the settings dialog because the ControlSocket path does not exist. It defaults to /var/run/tor/control

I then activated the Control Socket 9051 in Tor’s configuration file ( /etc/tor/torrc ) and edited Vidalia’s settings accordingly. I also reset Vidalia’s path to that Tor config file.

Unfortunately, I’m still getting the same error as above!

3 Answers 3

I tried to manually start Tor (by typing /usr/sbin/tor in the terminal) and afterwards Vidalia and it works perfectly.

From the documentation of Vidalia:

I Can’t Start Tor

The most likely reason that Vidalia could not start Tor is because Vidalia is looking for your Tor installation in the wrong directory. You can tell Vidalia where Tor is located by updating the Tor Executable option in the general configuration settings. Another possible reason that Tor cannot start is because there is already another Tor process running. Check your list of running process and stop the previous Tor process, if you find one. Then, try running Tor again.

If that did not help, check your message log to see if Tor printed any information about errors it encountered while trying to start.

Vidalia Can’t Connect to Tor

Vidalia manages Tor by communicating with it via Tor’s control port.

The most common reason that Vidalia cannot connect to Tor is because Tor started, but encountered an error and exited immediately. You should check your message log to see if Tor reported any errors while it started.

If Tor is listening on a different port than Vidalia expects, Vidalia will be unable to connect to Tor. You rarely need to change this setting, but if there is another service running on your machine that conflicts with Tor’s control port, you will need to specify a different port. You can change this setting in Vidalia’s advanced configuration settings.

Не взлетает Tor на ArchLinux

Хочу запустить в домашней сети небольшой сервер, который будет предоставлять Socks порт для подключений через Tor. Установленный дистрибутив — ArchLinux.

Для примера — адрес сервера и порта для подключения в локальной сети 192.168.0.27:9550

Соответственно в /etc/tor/torrc установлен параметр SocksPort 192.168.0.27:9550

Если запускаю Tor в консоли как systemctl start tor Все отрабатывает отлично, внешний порт доступен и через него работают приложения с других машин.

Но если включу автозагрузку systemctl enable tor.service то после перезагрузки сервера все рушится:

Что я делаю не так и как исправить? Наверное, это какой-то костыль и нужно перенаправлять все запросы с внешнего порта Socks на внутренний адрес сервера и убрать из torrc явный адрес 192.168.0.27 ?

Источник

I attempted to reinstall the launcher through the option in its accompanying settings file, yet this did nothing. I uninstalled the launcher, then attempted to re-download it directly through the software manager, thinking I may have borked the installation somehow; yet the problem persisted. I tried uninstalling that, only to try the tarball one more time. No luck. I should note that in all cases, I made sure to perform

just to be sure.

Code: Select all

timedatectl set-local-rtc 1 --adjust-system-clock

I have still had no success.

Code: Select all

-rwx------ 1 namehere namehere 12937 Dec 31  1999 start-tor-browser

P.S., I know Brave has a Tor option, but I can’t seem to get a clear answer as to whether or not it’s as secure as the real deal, so to speak.

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Источник