Overview: Support for Docker image joshgaby-to-relay.

Application: Tor - https://www.torproject.org/

Docker Hub: https://hub.docker.com/r/joshgaby/tor-server

GitHub: https://github.com/josh-gaby/tor-server

 

This docker will allow you to run a tor relay using the latest version of tor and obfs4proxy.

 

Initial Setup

1. Create a folder appdata/tor-data/config (this will be used to store the config between restarts)
2. Download sample torrc config file from here and edit as necessary (you can find details about possible configuration options here).
3. Save this into the config folder created above.
4. Create a folder appdata/tor-data/data (this will be used to preserve your relays keys/data between restarts)
5. Edit the docker parameters and run it.

 

 

Edited November 7, 20222 yr by josh.gaby

Do you know if there is an easy way to get nyx working?

@t3ch

Sorry for the late reply, I'm in the middle of moving so everythings a little hectic at the moment.

I haven't tried setting up nyx with the docker image yet but when I get some free time next week I'll see if I can get it working, if I can I'll add it to the image with an optional flag to enable it.

ooft yeah NYX would be nice trying to set up a relay to work with https://ator.io/ and a little command-line monitor would be nice

I installed tor-relay and followed the instructions but the docker application won't run and I get the following error when I check the log:

 

Jun 20 12:22:21.001 [notice] Closing partially-constructed OR listener connection (ready) on 0.0.0.0:9001
Jun 20 12:22:21.001 [notice] Closing partially-constructed Directory listener connection (ready) on 0.0.0.0:9030
Jun 20 12:22:21.001 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Jun 20 12:22:21.001 [err] Reading config failed--see warnings above.

 

Any idea what's going on or how I can fix this? I edited the config file and it looks fine, and port 9001 is set correctly (as far as I can tell) in the docker settings in Unraid. Attached is the full log image.

On 12/22/2022 at 6:43 AM, t3ch said:

Do you know if there is an easy way to get nyx working?

 

On 5/27/2023 at 11:48 AM, burgess22 said:

ooft yeah NYX would be nice trying to set up a relay to work with https://ator.io/ and a little command-line monitor would be nice

 

Are you wanting to enable the control port so you can run Nyx on a different computer or would including Nyx in the image be what your after?

2 hours ago, rexkwondo said:

I installed tor-relay and followed the instructions but the docker application won't run and I get the following error when I check the log:

 

Jun 20 12:22:21.001 [notice] Closing partially-constructed OR listener connection (ready) on 0.0.0.0:9001
Jun 20 12:22:21.001 [notice] Closing partially-constructed Directory listener connection (ready) on 0.0.0.0:9030
Jun 20 12:22:21.001 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Jun 20 12:22:21.001 [err] Reading config failed--see warnings above.

 

Any idea what's going on or how I can fix this? I edited the config file and it looks fine, and port 9001 is set correctly (as far as I can tell) in the docker settings in Unraid. Attached is the full log image.

 

I haven't got ipv6 enabled myself so I haven't run into this issue. 

 

Have you got Unraid setup to allow ipv6 in Docker and VMs how-to-get-ipv6-address-for-unraid-docker-application?

 

Looking at the log output, and without seeing your torrc file, I think you might have

 

ORPort 9001
ORPort [2a02:908:4c1:f560::ad0c]:9001

 

can you try this instead (replace IPv4.address and IPv6::address with the actual IP addresses)

 

Address IPv4.address
Address [IPv6::address]
ORPort 9001

 

 

19 hours ago, josh.gaby said:

 

I haven't got ipv6 enabled myself so I haven't run into this issue. 

 

Have you got Unraid setup to allow ipv6 in Docker and VMs how-to-get-ipv6-address-for-unraid-docker-application?

 

Looking at the log output, and without seeing your torrc file, I think you might have

 

ORPort 9001
ORPort [2a02:908:4c1:f560::ad0c]:9001

 

can you try this instead (replace IPv4.address and IPv6::address with the actual IP addresses)

 

Address IPv4.address
Address [IPv6::address]
ORPort 9001

 

 

That was it! Thanks so much for your feedback. Turns out I didn't even have ipv6 enabled on the server at all (and for some reason the option to enable ipv6 was greyed out and unavailable). Adding the correct ipv4 address to torrc fixed it and now the app runs.

Just fired this up and keep getting a warning that the install is obsolete, any chance you'll update it so it can auto update?

2 hours ago, MrTroll said:

Just fired this up and keep getting a warning that the install is obsolete, any chance you'll update it so it can auto update?

I've made some changes, I switched out the base image for Debian 12 and configured Unattended Upgrades to allow Tor to autoupdate.

However, I haven't been using docker for my Tor relay for a while now (I switched to a VM for higher performance) which means I'm unable to fully test the new the image. I know it starts up and Tor starts but I haven't confirmed traffic etc.

I've pushed it to DockerHub with a beta tag joshgaby/tor-server:beta, if you don't mind being a bit if a test subject you can try switching to that image and see how it works for you.

After doing a fresh install, I get this error on first boot;

grep: /etc/tor/torrc: No such file or directory
/usr/local/bin/docker-entrypoint: line 75: ulimit: open files: cannot modify limit: Operation not permitted

========================================================
changed ownership of '/var/lib/tor' from 99:users to tord:tord
mode of '/var/lib/tor' changed from 0755 (rwxr-xr-x) to 0700 (rwx------)
Setting chosen Nickname: Tormama
Setting ulimit...

After that its booted up completely, i'll monitor the logs for changes.

@MrTroll I've removed the ulimit increase section, it was left over from some experiments I had been doing with increasing the performance

@MrTroll how is your server looking looking, any issues with that beta image or is it running as expected for you?

Shes running well, i've just had to turn off ipv4 only mode but sweet otherwise. :)))

New issue after unraid 7.
Keep getting this error: Your server has not managed to confirm reachability for its ORPort(s) at MYWANIP:443
My network settings

User tord

ORPort 443 IPv4Only

ORPort 9001 IPv4Only

SocksPort 0

ExitPolicy reject *:*

It's impossible to accidentally become an exit node with this? 

No matter if I forget to change, or misunderstand a parameter, I can never become an exit node? 
I'd like to support the network, but really don't want to be an exit node. For obvious reasons. 

Hey man if you modify the icon URL to "https://gitlab.torproject.org/tpo/web/styleguide/-/raw/HEAD/assets/static/images/tor-browser/nightly/icon_512x512.png"

It'll actually load an icon. :))