Plex auto update - loses custom server access URL's | PlexGuide.com

Plex auto update - loses custom server access URL's

  • Stop using Chrome! Download the Brave Browser via >>> [Brave.com]
    It's a forked version of Chrome with native ad-blockers and Google's spyware stripped out! Download for Mac, Windows, Android, and Linux!
Welcome to the PlexGuide.com
Serving the Community since 2016!
Register Now

antigravity

Experienced
Original poster
Apr 23, 2019
95
13
Hey everyone

I have Plex setup to run via Cloudflare - but every time Plex updates- I lose the custom server URL's I have entered (https://plex.domain.xyz:443)

As a result - Plex becomes uncontactable each time it updates.

Is there a way to stop Plex resetting these settings when it updates?

Thanks
 

antigravity

Experienced
Original poster
Apr 23, 2019
95
13
Does anyone have any ideas?

Every time Plex updates - I lose all my custom settings for Cloudflare CDN.
 

4mm4r

Citizen
Donor
Aug 2, 2019
14
1
Hey,

I am having the exact same issue. I ended up enabling 'Remote Access' as a temporary fix. I didn't bother asking on the forum since no one really replies and you're kind of on your own :/

Cheers!
 

drake

Citizen+
Sep 5, 2018
23
2
Same here. Plex works great with the Cloudflare guide, but on update the Cistom server access url is reverted back to default and that breaks CDN. Any way to integrate this to installer to respect custom services on Plex container update?
 

antigravity

Experienced
Original poster
Apr 23, 2019
95
13
There's some custom PGBlitz network settings added to the docker image - whenever there's an update- it reverts back to these.

Basically means you can't run Plex with Cloudflare with PGBlitz - as it shits the bed when it updates.
 

antigravity

Experienced
Original poster
Apr 23, 2019
95
13
No-one?

Plex updates when using a CIDN is broken at the moment.

Is there a way to edit the plex container config to stop reverting to http://plex.domain.xyd:32400 everytime there's an update?
 

Admin9705

Administrator
Project Manager
Donor
Jan 17, 2018
5,151
2,120
I'll test this in PG9. At the moment in a few, pushing out the first early BETA in PG9. Since other broke some areas within PG8 and I haven't used CF with it, my info is limited. Since I use CF a ton now for other stuff, this will be less of a challenge. Traefik is working in PG9, though nothing has changed other than adaption for now.
 

antigravity

Experienced
Original poster
Apr 23, 2019
95
13
  • Like
Reactions: 1 user

PlexPlex

Experienced
Staff
Aug 8, 2019
53
8
Thanks @Admin9705.

Basically the issue is the Plex container has a custom PGBlitz field under "Custom server access URL's" - that specifies http://plex.domain.xyd:32400

Problem is that doesn't work when using Cloudflare - it instead needs to be "https://plex.domain.xyd:443"

So everytime Plex updates- it refers to the original "http://plex.domain.xyd:32400" and breaks Plex.
Ah that makes it easier to tshoot. Once they test in PG9 they can backport the fix to PG8. I was thinking about trying CF for my other server.
 

drake

Citizen+
Sep 5, 2018
23
2
I have this same issue, and it is really annoying:( Hope there will be a fix for this anytime soon, as it works with CD really cool (except this update thing)
 

Edrock200

MVP
Staff
Nov 17, 2019
765
272
Open portainer, open your Plex container, click duplicate/edit, go down to the ENV variables section. For the variable called "ADVERTISE_IP" update it to what you want published. Click deploy and confirm you want it to deploy over the existing container.
 
  • Like
Reactions: 2 users

Recommend NewsGroups

      Up To a 58% Discount!

Trending