josh.gaby

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

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

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.

Just tried the latest release (v1.33.1) and the problem seems to be have been resolved.

Its not Plex container related at all, the issue is when trying to use the actual plextv SSO to login to Overseerr, I am running your plexpass container though. I really don't see how this is a container issue so I'm going to dig into the Overseerr code to see if I can find any issue at their end.

@BrynPalmer They've just closed my issue on GitHub and stated that "This is an issue with the binhex container. Reach out to them for support." @binhex The 1.33 version fails to logon using a Plex account, not sure if there is a new port that needs opening for a websocket or something but signing in using Plex results in a 500 error from the https://{redacted}/api/v1/auth/plex endpoint with the following log entries. 2023-06-18T01:39:24.585Z [error][Plex.tv API]: Something went wrong while getting the account from plex.tv: Socket connection timeout 2023-06-18T01:39:24.586Z [error][API]: Something went wrong authenticating with Plex account {"errorMessage":"Invalid auth token","ip":"{redacted}"}

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

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?

@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.

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