jmaino

I missed some of the detail prior to my earlier comment. But, I now also have v2 working by following @Endling 's suggestions and edits to the config file. The 3 changes I needed to make in mine from v2's default were: targetHostname: host.docker.internal defaultProxyProvider: default tryDockerInternalNetwork: true Once these changes were made, I was up and running properly again using the :latest tag on TSDProxy.

I've also encountered the issues and have reverted back to :1.4.7 . It appears that :latest is using TS 1.98.1, as this is what my Tailscale dashboard shows for the machines when running v2/:latest of the proxy. The TS RN's say: Linux Note: 1.98.1 introduced a regression in the interaction between Tailscale and MagicDNS on Linux. The Linux release has been withdrawn pending a fix. I'm wondering if what we're seeing is related to this? Maintainer has already checked-in an update to TS to 1.98.2 as of last week, but it doesn't seem as if it's been released to :latest (yet).

OK - the above was probably user error - I had VERSION set to latest. Changing to "plexpass" seems to permit it to find the new release and update as expected. Sorry for the confusion. -Jim

Hi guys - on 2/29, plex released version 0.9.16.0.1754-23623fb. It seems that the auto upgrade capabilities of this docker rely on grabbing info from tools.linuxserver.io/latest-plex.json which still states: "last_checked": 1456925857, "version": "0.9.15.6.1714-7be11e1", I'm curious what level of automation exists (if any?) to make sure that linuxserver.io's version of "latest" that it keeps local to linuxserver.io gets regularly updated, and at what frequency? Thanks, -Jim