Hi I found on github that this issue was resolved and seems to be ready to install. But have no idea how to do this manually. There is add on labelled v3.0.5
Anyone can help with this?
Hi,
I already wrote a letter to a Frenck offering Patreon but he didnāt answer anything, I wrote it the first day when Tor stop working. I guess I was not able to make a contactā¦If anyone can establish communication with Frenckā¦count me in for support!
I had the same issue. Then I realized that Frenck did the corrections on Edge Repo, but those corrections are still not cascaded to official repo, neither to Beta repo.
So what I did was uninstall TOR, including on ADDONs page the EDGE REPO link and installing it again but from this repo. It worked for me, I hope it helps.
David
@dforco, can you explain what you mean a bit more? Iām having the same issues as others. Iād like to try out your fix, but Iām a little out of my depth. I understand that I need to uninstall Tor and any addons and then reinstall using āEdge Repo,ā but Iām not sure how to tell Home Assistant to install from a different repository.
Remeber first to uninstall the existing add-on, then installing the āedgeā version.
Other option is to wait the changes to be cascaded to the new package but this could take longā¦
Have a great day, David
Did anyone managed to get authorised clients working with the edge version? using the standard Home Assistant installation
Just to let you know, changes where cascaded to 4.0.0 and it is working fine again in official addon repo.
2 Likes
also interested in this question, will the ability to configure the bridges be added?
https://bridges.torproject.org/
Iāve used tor socks proxy to workaround russian torrents restrictions for radarr, lidarr, sonarr, prowlarr. And this setup has worked while some thing happens:
Add-on version: 4.1.1
You are running the latest version of this add-on.
System: Home Assistant OS 10.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.5.2
Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to WARNING
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-tor: starting
s6-rc: info: service init-tor successfully started
s6-rc: info: service tor: starting
s6-rc: info: service tor successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
May 09 21:23:17.648 [notice] Tor 0.4.7.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.8, Zlib 1.2.13, Liblzma 5.2.9, Libzstd 1.5.2 and Unknown N/A as libc.
May 09 21:23:17.648 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
May 09 21:23:17.649 [notice] Read configuration file "/etc/tor/torrc".
May 09 21:23:17.685 [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.
May 09 21:23:17.686 [notice] Opening Socks listener on 0.0.0.0:9050
May 09 21:23:17.687 [notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
May 09 21:23:18.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't.
May 09 21:31:44.000 [warn] Problem bootstrapping. Stuck at 5% (conn): Connecting to a relay. (Operation timed out; TIMEOUT; count 10; recommendation warn; host EF25C1F9BEF8C4A3F2859493C7C8C5148725B4E7 at 176.9.98.108:9001)
May 09 21:31:44.000 [warn] 9 connections have failed:
May 09 21:31:44.000 [warn] 9 connections died in state connect()ing with SSL state (No SSL object)
Google suggests to use tor bridge, so iāve forked addons and adjust it to configure an bridges, but still get some issue:
-----------------------------------------------------------
Add-on version: dev
You are running the latest version of this add-on.
System: Home Assistant OS 10.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.5.2
Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-tor: starting
[02:25:40] INFO: Setup obfs4 bridges:
[02:25:40] INFO: Bridge obfs4 blaalalla...
[02:25:40] INFO: Bridge obfs4 blabllabla...
[02:25:40] INFO: Bridge obfs4 blabla....
s6-rc: info: service init-tor successfully started
s6-rc: info: service tor: starting
s6-rc: info: service tor successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[02:25:41] INFO: Starting Tor...
May 11 02:25:41.673 [notice] Tor 0.4.7.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.8, Zlib 1.2.13, Liblzma 5.2.9, Libzstd 1.5.5 and Unknown N/A as libc.
May 11 02:25:41.677 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
May 11 02:25:41.678 [notice] Read configuration file "/etc/tor/torrc".
May 11 02:25:41.688 [notice] Converting FascistFirewall config option to new format: "ReachableDirAddresses *:80"
May 11 02:25:41.688 [notice] Converting FascistFirewall config option to new format: "ReachableORAddresses *:443"
May 11 02:25:41.716 [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.
May 11 02:25:41.716 [notice] Opening Socks listener on 0.0.0.0:9050
May 11 02:25:41.716 [notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
May 11 02:25:41.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
May 11 02:25:42.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
May 11 02:25:43.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't.
May 11 02:25:43.000 [notice] Bootstrapped 0% (starting): Starting
May 11 02:25:43.000 [notice] Starting with guard context "bridges"
May 11 02:25:43.000 [notice] Delaying directory fetches: No running bridges
May 11 02:26:30.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
May 11 02:28:00.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
May 11 02:28:00.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
May 11 02:28:30.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
But i donāt understand whatās wrong for now ?
UPD: Support obfs4 bridges by akrigator Ā· Pull Request #170 Ā· hassio-addons/addon-tor Ā· GitHub