> On 4 Mar 2018, at 17:50, peter.zehet...@liwest.at wrote:
>
> OK, but what is this:
>
> Mar 03 21:36:31.000 [warn] Failed to start child process "tor-fw-helper" in
> state 9: No such file or directory
> Mar 03 21:51:46.000 [warn] Failed to start child process "tor-fw-helper" in
> state 9: No
OK, but what is this:
Mar 03 21:36:31.000 [warn] Failed to start child process "tor-fw-helper" in
state 9: No such file or directory
Mar 03 21:51:46.000 [warn] Failed to start child process "tor-fw-helper" in
state 9: No such file or directory
Mar 03 21:56:51.000 [warn] Failed to start child pro
> On 3 Mar 2018, at 18:32, peter.zehet...@liwest.at wrote:
>
> Mar 03 00:05:38.000 [notice] Self-testing indicates your ORPort is reachable
> from the outside. Excellent.
> Mar 03 00:05:45.000 [notice] Performing bandwidth self-test...done.
> Mar 03 00:09:29.000 [notice] Self-testing indicates y
I've opend the ports in my router. Could anybody be so kind to check my log and
tell me wether it's ok or not?
Mar 03 00:05:38.000 [notice] Self-testing indicates your ORPort is reachable
from the outside. Excellent.
Mar 03 00:05:45.000 [notice] Performing bandwidth self-test...done.
Mar 03 00:0
Hi!
On Fri, Mar 02, 2018 at 09:34:02PM +0100, peter.zehet...@liwest.at wrote:
> OK, now I've set PortForwarding in Tor-Arm from "False" to "True", then
> restarted Tor:
Hrm, I'm not sure this will do what you want. In fact, this may do
absolutely nothing. Do you have administative access into yo
OK, now I've set PortForwarding in Tor-Arm from "False" to "True", then
restarted Tor:
...has not managed to confirm that its DirPort is reachable. Relays do not
publish descriptors until their ORPort and DirPort are reachable. Please
check...
I'm going to run a non-exit-relay and I'm going to
On Fri, Mar 02, 2018 at 07:42:11PM +, Matthew Finkel wrote:
> Are you running this relay at your home? If yes, then that is not
> recommended, but
For the record, it's running *exit* relays at home that is not
recommended. Running non-exit relays at home is typically fine -- the
most likely pr
On Fri, Mar 02, 2018 at 08:27:29PM +0100, peter.zehet...@liwest.at wrote:
> Hi, I'm still trying to run a tor delay. Here's the error:
>
Thank you for running a relay.
> Your server (81.10.248.112:80) has not managed to confirm that its DirPort is
> reachable. Relays do not publish descriptors
_Something_ is blocking port 80.
$ nmap -sT 81.10.248.112 -p 80 -Pn
Starting Nmap 7.01 ( https://nmap.org ) at 2018-03-02 11:38 PST
Nmap scan report for cm248-112.liwest.at (81.10.248.112)
Host is up.
PORT STATESERVICE
80/tcp filtered http
Nmap done: 1 IP address (1 host up)
There is no firewall installed.
Peter
Have you double-checked your firewall?
-Cody
On 03/02/2018 11:27 AM, peter.zehet...@liwest.at
mailto:peter.zehet...@liwest.at wrote:
>
> Hi, I'm still trying to run a tor delay. Here's the error:
>
> Your server (81.10.248.112:80) has not managed to confir
Have you double-checked your firewall?
-Cody
On 03/02/2018 11:27 AM, peter.zehet...@liwest.at wrote:
>
> Hi, I'm still trying to run a tor delay. Here's the error:
>
> Your server (81.10.248.112:80) has not managed to confirm that its
> DirPort is reachable. Relays do not publish descriptors unt
Hi, I'm still trying to run a tor delay. Here's the error:
Your server (81.10.248.112:80) has not managed to confirm that its DirPort is
reachable. Relays do not publish descriptors until their ORPort and DirPort are
reachable.
But canyouseeme.org said: Your ISP is not blocking port 80
Whats's
12 matches
Mail list logo
