[Freedombox-discuss] problems connecting to Tor hidden service

[DJ]

Hi all,

some more information in case someone can help me.

Reminder: The problem connecting via Tor started after rebooting my
FreedomBox.

I can ssh into the FBX using the clearnet. I have disabled and
renenabled Tor from Plinth, as described in my email from yesterday (see
below).

Today I have restarted Tor in my FBX with the following command as root:

root at debian:/home/fbx# service tor restart

I have checked the status of Tor:

fbx at debian:~$ systemctl status tor.service
● tor.service - Anonymizing overlay network for TCP (multi-instance-master)
   Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor
preset: enabled)
   Active: active (exited) ...
  Process: 9957 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 9957 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/tor.service

Finally, I have checked that the Tor service is running on port 9050:

fbx at debian:~$ ss -aln | grep 9050
u_str  LISTEN     0      128    /run/systemd/private 9050
  * 0
tcp    LISTEN     0      128       *:9050                  *:*

tcp    LISTEN     0      128      :::9050                 :::*

Is there any other information I should provide?

I really appreciate any help from the FreedomBox community!

Cheers,
DJ

P.s. Thanks, James, for the information regarding
/etc/apache2/sites-available/plinth.conf and Plinth access being
restricted to certain IP ranges. I hope to try and figure that out once
I get Tor working.


> Date: Fri, 17 Jun 2016 18:30:11 +0000
> From: DJ <dgj+lists at systemli.org>
> To: freedombox-discuss at lists.alioth.debian.org
> Subject: Re: [Freedombox-discuss] problems connecting to Tor hidden
> 	service
> Message-ID: <7f7f8b57-81dd-984b-af65-73aec78f914d at systemli.org>
> Content-Type: text/plain; charset=windows-1252
> 
> Hi,
> 
> I was able to log in to Plinth by creating an ssh tunnel (openvpn still
> doesn't work for me) and then disable and re-enable Tor from the Plinth
> interface. Before disabling I got "failed" almost exclusively for
> diagnostics, now I get the following:
> 
> Module: tor
> Test 	Result
> Listening on tcp4 port 9050 	passed
> Listening on tcp6 port 9050 	passed
> Listening on tcp4 port 9040 	passed
> Listening on tcp6 port 9040 	passed
> Listening on udp4 port 9053 	passed
> Listening on udp6 port 9053 	passed
> Connect to 127.0.0.1:9051 	passed
> Cannot connect to 192.168.1.105:9051 	passed
> Cannot connect to 10.91.0.1:9051 	passed
> Tor relay port available 	failed
> Obfs3 transport registered 	passed
> Listening on tcp4 port 34303 	failed
> Obfs4 transport registered 	passed
> Listening on tcp4 port 38162 	failed
> Access URL http://www.debian.org on tcp4 via Tor 	failed
> Access URL http://www.debian.org on tcp6 via Tor 	failed
> Confirm Tor usage at https://check.torproject.org on tcp4 	failed
> Confirm Tor usage at https://check.torproject.org on tcp6 	failed
> 
> However, I still cannot connect to the Tor hidden service. Any help?
> 
> Thanks!
> DJ
>