Jason Landbridge

This might be fixed in: https://github.com/PlexRipper/PlexRipper/issues/269 Needs confirmation when the fix is live

Same here, a legacy version would have been welcome and an e-mail about these changes. I'm currently recreating everything as well but some features are gone

@AshotN , I would honestly prefer if this repo can be maintained instead of a fork due to the extra overhead. Let's see if @js2me responds and then it might...

@js2me Ping!

Ah thank you very much for this, I will fix this is the next release (0.9.1) which should be available by the end of this week. Apologies for the delay!

I can confirm this new api URL provides more servers and connections to communicate with the Plex server. So I'm currently working on integrating this. I also expect this to...

Update: It's been quite a bit of work but I hope to have it finished by the end of the week. The biggest change is that PlexRipper now receives multiple...

Yes! Finally I have resolved this issue, among many others, which is now released [v0.10.0-RC1](https://github.com/PlexRipper/PlexRipper/releases/tag/v0.10.0-RC1) on both the latest and dev Docker channels: https://hub.docker.com/r/plexripper/plexripper/tags

Yes indeed as @EricLauber mentioned, it's most likely due to the ports not mapped/exposed correctly. Will close this issue for now but re-open if you need more help

> No hard promise, but I will publish this new container this weekend and go from there. Well this aged quite badly :laughing: The new release is now available on...