github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #642] Tor browser returns fatal error if using firejail and Tor's meek protocol #446

New issue

Closed

opened 2026-05-05 05:52:52 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:52:52 -06:00

Owner

Originally created by @igor2x on GitHub (Jul 23, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/642

SUMMARY
Test 1 - Tor using Firejail and Tor's meek protocol A PROBLEM.
Test 2 - Tor using Firejail and Tor's obfs4 protocol WORKS FINE.
Test 3 - Tor WITHOUT Firejail and Tor's meek protocol WORKS FINE.
Bellow are details how to reproduce a problem.

INSTALLATION
On Ubuntu 16.04 Desktop 32-bit I have downloaded Firejail from:
http://sourceforge.net/projects/firejail/files/firejail/firejail_0.9.40_1_i386.deb

I installed Firejail: sudo dpkg -i <deb_file>

Check the firejail version: firejail --version
firejail version 0.9.40

I downloaded Tor browser from:
https://www.torproject.org/dist/torbrowser/6.0.2/tor-browser-linux32-6.0.2_en-US.tar.xz

Untar the file to /opt/tor/ directory. It is not requirement to untar it there, you can untar it where ever you like.

TEST 1 - THE PROBLEM

Run Tor with Firejail:
cd /opt/tor/
firejail /opt/tor/start-tor-browser.desktop
When Tor wizard opens-up immediately select (don't wait to Tor browser starts up): Open Settings button
Configure button
Does your ISP block or otherwise censor connections to the Tor Network: select Yes and Next button
select: Connect with provided bridges and Transport type select: meek-amazon and Next button
Does this computer need to use a local proxy to access the Internet?: select No and Connect button

After few seconds the following error appears:

Tor failed to establish a Tor network connection.
Connecting to a relay directory failed (missing pluggable transport - 0.0.2.0:2)

Note: The same problem with meek-azure and meek-google protocols.

It does look like a Firejail problem. Why? See next two tests bellow.

TEST 2 - WORK-AROUND USING OBFS4 PROTOCOL WITH FIREJAIL
All steps the same as in TEST 1 except step 5: select: Connect with provided bridges and Transport type select: obfs4 (recommended) and Next button
Step 6 is the same.

Tor browser starts-up without a problem.

TEST 3 - WORK-AROUND USING MEEK-AMAZON WITHOUT! FIREJAIL

Run Tor without! Firejail
cd /opt/tor/
/opt/tor/start-tor-browser.desktop

All other steps are the same as in TEST 1.

Tor browser starts-up without a problem.

ADDITIONAL INFO
I tried to start-up Tor browser with Firejail with debug option like:
firejail --debug /opt/tor/start-tor-browser.desktop
I see firejail's default.profile is used.
But after step 3 in TEST 1 and TEST 2 there is no text displayed in terminal. So no what ever is selected in Tor wizard no info is displayed in terminal.

I don't know if this is Firejail version 0.9.40 regression or it is an old problem, because I have never used meek-amazon (and other meek-azure and meek-google) protocol with Tor before.

Originally created by @igor2x on GitHub (Jul 23, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/642 **SUMMARY** Test 1 - Tor using Firejail and Tor's meek protocol A PROBLEM. Test 2 - Tor using Firejail and Tor's obfs4 protocol WORKS FINE. Test 3 - Tor WITHOUT Firejail and Tor's meek protocol WORKS FINE. Bellow are details how to reproduce a problem. **INSTALLATION** On Ubuntu 16.04 Desktop 32-bit I have downloaded Firejail from: http://sourceforge.net/projects/firejail/files/firejail/firejail_0.9.40_1_i386.deb I installed Firejail: `sudo dpkg -i <deb_file>` Check the firejail version: `firejail --version` firejail version 0.9.40 I downloaded Tor browser from: https://www.torproject.org/dist/torbrowser/6.0.2/tor-browser-linux32-6.0.2_en-US.tar.xz Untar the file to /opt/tor/ directory. It is not requirement to untar it there, you can untar it where ever you like. **TEST 1 - THE PROBLEM** 1. Run Tor with Firejail: `cd /opt/tor/` `firejail /opt/tor/start-tor-browser.desktop` 2. When Tor wizard opens-up immediately select (don't wait to Tor browser starts up): _Open Settings_ button 3. _Configure_ button 4. _Does your ISP block or otherwise censor connections to the Tor Network:_ select _Yes_ and _Next_ button 5. select: _Connect with provided bridges_ and _Transport type_ select: _meek-amazon_ and _Next_ button 6. _Does this computer need to use a local proxy to access the Internet?_: select _No_ and _Connect_ button After few seconds the following error appears: **Tor failed to establish a Tor network connection. Connecting to a relay directory failed (missing pluggable transport - 0.0.2.0:2)** Note: The same problem with meek-azure and meek-google protocols. It does look like a Firejail problem. Why? See next two tests bellow. **TEST 2 - WORK-AROUND USING OBFS4 PROTOCOL WITH FIREJAIL** All steps the same as in TEST 1 except step 5: select: _Connect with provided bridges_ and _Transport type_ select: _obfs4 (recommended)_ and _Next_ button Step 6 is the same. Tor browser starts-up without a problem. **TEST 3 - WORK-AROUND USING MEEK-AMAZON WITHOUT! FIREJAIL** 1. Run Tor without! Firejail `cd /opt/tor/` `/opt/tor/start-tor-browser.desktop` All other steps are the same as in TEST 1. Tor browser starts-up without a problem. **ADDITIONAL INFO** I tried to start-up Tor browser with Firejail with debug option like: firejail --debug /opt/tor/start-tor-browser.desktop I see firejail's default.profile is used. But after step 3 in TEST 1 and TEST 2 there is no text displayed in terminal. So no what ever is selected in Tor wizard no info is displayed in terminal. I don't know if this is Firejail version 0.9.40 regression or it is an old problem, because I have never used meek-amazon (and other meek-azure and meek-google) protocol with Tor before.

gitea-mirror

2026-05-05 05:52:52 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:52:59 -06:00

Author

Owner

@netblue30 commented on GitHub (Jul 24, 2016):

I'll take a look, thanks.

@netblue30 commented on GitHub (Jul 24, 2016): I'll take a look, thanks.

gitea-mirror commented

2026-05-05 05:53:02 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Aug 19, 2018):

Is this still an issue @igor2x?

@chiraag-nataraj commented on GitHub (Aug 19, 2018): Is this still an issue @igor2x?

gitea-mirror commented

2026-05-05 05:53:06 -06:00

Author

Owner

@igor2x commented on GitHub (Aug 21, 2018):

I rechecked this ancient bug report and problem does not appear anymore.

@igor2x commented on GitHub (Aug 21, 2018): I rechecked this ancient bug report and problem does not appear anymore.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#446

No description provided.

Rows
Columns