Plex - Changed Plex password and updated claim token, can't access Plex.domain.com or access remotely | PlexGuide.com

Plex Changed Plex password and updated claim token, can't access Plex.domain.com or access remotely

  • 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

b101marc

Active
Original poster
Donor
Donor
Jul 11, 2018
47
9
Hi all,
Basically the title. Had to update my Plex password and re-claimed my Plex via Portainer update, however I'm unable to access y server remotely or via website. I'm able to login at Plex.tv but no access to the server.
 

Edrock200

MVP
Staff
Nov 17, 2019
726
260
Hi all,
Basically the title. Had to update my Plex password and re-claimed my Plex via Portainer update, however I'm unable to access y server remotely or via website. I'm able to login at Plex.tv but no access to the server.
When you redeployed did you select remote server when askede if remote or local?

Go into portainer, dupe/edit plex container, under env make sure the IP_ADVERTISE URL is correct, e.g. https://plex.yourdomain.com:443
Generate a new claim code and put it into claim_code
Under labels if you have a traefik protocol label and it's set to HTTPS, try changing it to HTTP or vice versa. Deploy.
 

b101marc

Active
Original poster
Donor
Donor
Jul 11, 2018
47
9
I've gone through a fair few troubleshooting steps, including reinstalling Plex and ensuring it is a remote install and updating the Plex Claim.

Currently the IP_ADVERTISE_URL is correct and has not changed and I've tried a new CLAIM_CODE to no avail.

What FINALLY worked was your suggestion of changing the protocol label. Does changing from HTTPS from HTTP open me up to any potential security risks?

Truly my friend I appreciate your help.
 

Edrock200

MVP
Staff
Nov 17, 2019
726
260
I've gone through a fair few troubleshooting steps, including reinstalling Plex and ensuring it is a remote install and updating the Plex Claim.

Currently the IP_ADVERTISE_URL is correct and has not changed and I've tried a new CLAIM_CODE to no avail.

What FINALLY worked was your suggestion of changing the protocol label. Does changing from HTTPS from HTTP open me up to any potential security risks?

Truly my friend I appreciate your help.
Once you sign in and it grabs a cert you should be fine. In Plex network settings you can change secure connection to required then change it back to https. This communication though is only between traefik and Plex. If you have 32400 published to the host, and secure connection set to preferred, then there is a chance that people can try accessing over an unsecure pipe, but they would need to know your IP.

My suggestion would be to try changing it back to https and see if it works now (assuming you are allowing secure connections in Plex.) If not, leave it as http but publish 32400 in container to 127.0.0.1:32400 on host and deploy. This will prevent any unsecure connections from the internet while still allowing the host to access Plex if needed for any 3rd party apps like Plex autoscan. If you don't have anything on host that needs direct access to Plex, you can unpublish.
 

Recommend NewsGroups

      Up To a 58% Discount!

Trending