-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Last week I experimented with OpenSSL 1.0.1c and saw a huge increase in traffic. Unfortunately, my hardware was not up to the task and I started seeing timeouts and other errors.
I have decided to replace the server with a much beefier one in the very near future. Meanwhile, I installed nginx as a reverse proxy on the Directory Port.
nginx config:
server { listen 154.35.32.5:80; server_name _;
location / { proxy_pass http://154.35.32.5:81; } }
Tor: DirPort 80 DirListenAddress 154.35.32.5:81
It was very easy and nice to configure Tor Directory behind a reverse proxy. The DirListenAddress came super handy!! Nice design.
Currently the directory port is responding blazing fast: http://faravahar.rabbani.jp/tor/status/all.z
Can someone poke at the directory port and let me know if they can find any issue with serving Tor in this fashion?
If this works fine, I will try to configure the directory port on a fancy DDoS mitigation gear next.
All the best, SiNA
- -- First they ignore you, then they laugh at you, then they fight you, then you win ~ Mahatma Gandhi