Home Assistant Community Add-on: Tor

Andy_Nunes · February 25, 2019, 6:54pm

I also seem to be having the same problem with the Tor add-on.

Andy_Nunes · February 26, 2019, 7:43pm

Hi, need some help with this any suggestions?pls.this is my config;

{
  "log_level": "info",
  "socks": true,
  "hidden_services": true,
  "stealth": true,
  "client_names": [
    "haremote1"
  ],
  "ports": [
    "homeassistant:8123:80"
  ]
}


Log


[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 10-tor: applying... 
[fix-attrs.d] 10-tor: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Tor v1.6.1
 Protect your privacy and access Home Assistant via Tor.
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
 aarch64 / HassOS 2.10 / HA 0.88.1 / SU 145 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 20-dirs.sh: executing... 
[cont-init.d] 20-dirs.sh: exited 0.
[cont-init.d] 50-tor-log.sh: executing... 
[cont-init.d] 50-tor-log.sh: exited 0.
[cont-init.d] 51-tor-socks.sh: executing... 
[cont-init.d] 51-tor-socks.sh: exited 0.
[cont-init.d] 52-tor-services.sh: executing... 
[cont-init.d] 52-tor-services.sh: exited 0.
[cont-init.d] 90-hostname.sh: executing... 
INFO: -----------------------------------------------------------
INFO: Your Home Assistant instance is available on Tor!
INFO: Addresses & Auth cookies:
INFO: xxxxxxxxxxxxxxxb.onion gxxxxxxxxxxxxxxR # client: haremote1
INFO: -----------------------------------------------------------
[cont-init.d] 90-hostname.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Feb 26 16:50:46.149 [notice] Tor 0.3.3.7 (git-035a35178c92da94) running on Linux with Libevent 2.1.8-stable, OpenSSL LibreSSL 2.7.4, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Feb 26 16:50:46.149 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 26 16:50:46.149 [notice] Read configuration file "/etc/tor/torrc".
Feb 26 16:50:46.169 [notice] Scheduler type KIST has been enabled.
Feb 26 16:50:46.169 [warn] You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
Feb 26 16:50:46.169 [notice] Opening Socks listener on 0.0.0.0:9050
Feb 26 16:50:46.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 26 16:50:47.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 26 16:50:47.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't.
Feb 26 16:50:47.000 [notice] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.
Feb 26 16:50:49.000 [notice] Bootstrapped 0%: Starting
Feb 26 16:50:52.000 [notice] Starting with guard context "default"
Feb 26 16:50:52.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Feb 26 16:50:53.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Feb 26 16:50:54.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Feb 26 16:50:54.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Feb 26 16:50:54.000 [notice] Bootstrapped 100%: Done

HOME ASSISTANT LOG

2019-02-26 18:09:12 ERROR (MainThread) [homeassistant.components.http.data_validator] Data does not match schema: required key not provided @ data['client_id']

dave_sausages · March 4, 2019, 9:15pm

Just adding a +1 to having this error. After trying loads of different settings, with stealthmode off I eventually entered “192.168.1.1:8123:8080” in the ports option and it started working!..and then upon logging in gave me the same error as Andy_Nunes. There is a rather bizarre disconnect between the instructions and reality for Tor noobs like myself. Once this finally works I’ll post the instructions that actually worked for me.

Andy_Nunes · March 7, 2019, 1:43pm

TOR is now working with the latest update 89.0

Andy_Nunes · March 7, 2019, 1:47pm

Special thanks to all the guys behind the scenes

frenck · March 23, 2019, 8:04pm

Release v2.0.0

Full Changelog

Changes

Upgrades add-on base image to 3.0.1
Upgrades tor to 0.3.4.11-r0
Adds support for ARMv7
Removes custom log format override
Makes log_level optional
Updates documentation for ARMv7
Rewrite add-on onto Bashio

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

Luke15153 · March 24, 2019, 1:15pm

Hi,

I just updated to V2.0.0, but the addon won’t start if configured in stealth mode. In the previous version this worked without problems.

Here’s my config:

{
  "socks": false,
  "hidden_services": true,
  "stealth": true,
  "client_names": [
    "name123"
  ],
  "ports": [
    "8123"
  ]
}

When stealth is false, the addon starts as expected.

Any suggestions what I am doing wrong?

Thx Luke

Log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 10-tor: applying... 
[fix-attrs.d] 10-tor: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Tor
 Protect your privacy and access Home Assistant via Tor.
-----------------------------------------------------------
 Add-on version: 2.0.0
 You are running the latest version of this add-on.
 System: HassOS 2.11  (armv7 / raspberrypi3)
 Home Assistant version: 0.90.1
 Supervisor version: 150
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in e.g, GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 20-dirs.sh: executing... 
[cont-init.d] 20-dirs.sh: exited 0.
[cont-init.d] 50-tor-log.sh: executing... 
[cont-init.d] 50-tor-log.sh: exited 0.
[cont-init.d] 51-tor-socks.sh: executing... 
[cont-init.d] 51-tor-socks.sh: exited 0.
[cont-init.d] 52-tor-services.sh: executing... 
[cont-init.d] 52-tor-services.sh: exited 0.
[cont-init.d] 90-hostname.sh: executing... 
[14:00:34] INFO: Starting Tor temporarly...
[cont-init.d] 90-hostname.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.
 
 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

AhmadK · March 24, 2019, 2:10pm

same here, issue opened :\

Qua3952 · May 3, 2019, 6:37am

Is there an estimated date for when the fix for this issue will be published on the release version of this add-on? (I saw it was fixed already on a beta version or so)

AhmadK · May 5, 2019, 7:59pm

the only thing they said was basically “wait”… which is really sad considering the situation, but there we are :\

frenck · May 5, 2019, 9:22pm

It is not. That is the issue.
If that fixed it, I would have released it already.

I don’t have that. This is an open source project, which relies on my own spare free time that I can donate to the project OR contributors.

Feel free to contribute a proper fix is you have one. I’m happy to merge and release.

Qua3952 · May 6, 2019, 7:47am

Hi @frenck, reading the comments on this thread I got the impression it was solved but not merged to the release version. Apparently I was mistaken and I apologize.
I’m fully aware of this project being an open source and specifically to your amazing contribution to it and other projects. I wish I could help but it is a bit above my pay grade
Anyway, now it is clear the issue is still pending…
Cheers.

Maikl_Sh · May 19, 2019, 11:45am

Dear @frenck , Maybe it is possible to return the previous version, in which everything worked?

frenck · May 19, 2019, 11:46am

Nope, that is not possible.

HA_T · July 19, 2019, 7:29pm

Did the latest update (0.96 and 0.96.1) break the Tor add-on? Since the update I can’t get to a login page using Tor. It connects, then loads the blue background across the top, and the white background. View-source shows some html and loaded js, but I can’t actually get the ui to load. I can connect at home without Tor.

I’ve tried restarting the add-on and restarting my raspi.

AhmadK · July 20, 2019, 8:35pm

The latest version is 2.0.0 and it does not work if stealth mode enabled. but does work without it.
The previous version (don’t remember exact number) worked fine for me in both modes.

HA_T · July 22, 2019, 3:14pm

Thanks for the reply. I’m using version 2.0.0 of the Tor add-on without stealth enabled. It worked great until Home Assistant version 0.9.6. It connects, but nothing but the background appears.

AhmadK · July 23, 2019, 8:07pm

Mine works. Open a new issue on Github if yours doesn’t…

MArtin_br · July 24, 2019, 3:39pm

Hallo HA fans;
Same here with HassIO, 96.3 and 2.0.0.
First I used orbot and orfox and now single tor browser. Connection is much quicker and smoother but only a white HA background with empty blue top banner are shown. The HA-tor add-on log confirms connection!
It appears that the torrc file has been seen and taken bby Tor Browser from Otbot nnow uninstalled, is that a correct assumption?

Thanks in advance
Martin J

frenck · August 25, 2019, 8:47pm

Release v2.1.0

Full Changelog

Changes

Fixes client definitions for stealth mode (#13)
Fixes client names when in stealth mode
Sets missing HiddenServicesVersion
Fixes incorrect torrc configuration
Maintaince -> Maintenance
Upgrades add-on base image to v4.1.1
Upgrades tor to 0.3.5.8-r0
fixed client_names (#14)

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck