-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So it is on atlas and consensus, it is an exit node.
But the probability of being an exit has decreased in the graphs, but
it is constant now. What does that mean?
Now we'll try to contact other exit nodes in the territory and see if
there is a kind
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yes, that means is working, theoretically. The log won't say anything
for the next 6 hours, and after 6 hours it will just say how many
circuits it has running, uptime and relayed bandwidth. These are the
default log settings. You can increase the ve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hey!
basically with your setup and a little trick on haproxy it is working
now or at least the log is saying:
[notice] Self-testing indicates your ORPort is reachable from the
outside. Excellent. Publishing server descriptor.
[notice] Performing ban
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi again
I don't know anything about haproxy config and how it should look like
unfortunately.
As for torrc:
ORPort :3128
NoAdevertise
ORPort :3128 NoListen
remove Address line.
Leave the contact info and other settings. Let us know if it works
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/09/2015 03:35 PM, s7r wrote:
> If you are using the free nginx, community project, that will only
> allow you to deploy a http(s) proxy. Only the commercial (paid)
> nginx allows you to deploy a TCP proxy (handles all TCP traffic),
> which is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
If you are using the free nginx, community project, that will only
allow you to deploy a http(s) proxy. Only the commercial (paid) nginx
allows you to deploy a TCP proxy (handles all TCP traffic), which is
what you need for a Tor relay.
If you want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello tor ^.^
i'm trying to setup a tor relay behind a nginx reverse proxy...
i would like to know if it's correctly setup.
i have this warn in the logs:
[warn] Received http status code 404 ("Not found") from server
'85.14.240.188:443' while fetchi
