Unfortunately, no chance… Still no access to local media on my TV or Tablet when using UsernameB 
I somehow do think it has something to do with the Plexpass, since I still see a little crown on the old usernameA ? Looks like Plex still thinks the Plexpass belongs to usernameA ?
The crown means usernameA is the adminstrator
Ah ok.. but the weird thing is that I removed UsernameA for a while to see if that solved my problem, but it didn’t, and after adding Username A again, it became administrator again apparently?
Weird that apparently nobody knows the solution for this ? Problem is still the same and quite annoying.. I don’t dare to remove and reinstall my server since I’m afraid of losing all my playlists, which took AGES to compile! And I’m also not sure a backup will reinstate them if I did reinstall the server.. Just upgrading from a yearly pass to a lifetime pass caused this problem so I somehow suspect it’s got something to do with the Plexpass.
I also noted that using Plex on my iPad now is limited to 1 minute and that I’d need to buy a plexpass for that as well ??
I just want to be able to access all my media on my android phone and tablet an prefereably also on my iPad within my own network..
This wasn’t my idea of converting from a yearly pass to a lifetime pass… ending up only be able to access all my media on my actual server!
Clear out the “List of IP addresses and networks that are allowed without auth” field as this is likely causing confusion between UsernameB and UsernameA.
Restart the server, wait 3 minutes and provide a complete fresh set of server logs.
It also looks like you are running a mix of Legacy and New Experience apps. The Legacy apps had 1 minute limit without a Plex Pass/Activation Fee.
It is detecting Double Nat so you have some networking to look at/resolve.
Plex Media Server Logs_2026-05-12_00-46-06.zip (3.0 MB)Cleared the List of IP adresses and left it empty. Shut fown the server, restarted it and the logs are attached.
Double NAT has never been an issue with my former yearly pass? I could try to change that as soon as I find the password for my ISP modem.. :-S
Since my Router is set to a different subnet, that shouldn’t cause any problems? Most devices in my home are set with a fixed IP address as well. This worked flawlessly for years and so did the remote access. Everything got buggered when I bought the lifetime pass..
Another weird thing I just noticed… When i open Chrome on my Android tablet and try to connect to app/plex.tv with UsernameB, it can’t reach my server somehow…
“Unable to make a secure connection…”
The tablet is in the same network as my Windows 10 PC that runs the server, which has no problem connecting to app.plex.tv ?
Uninstalling and reinstalling will fix nothing and depending on how you do it can break many things.
Removing the bad entry has cleaned up the logs considerably and can now make sense of them.
Continuing to blame the Plex Pass is the wrong conclusion and I will try to explain.
Over a year ago Plex began enforcing secure connections for the server and clients. Legacy clients could be set to insecure and function where the “New Experience” clients would struggle and fail.
Currently your server is failing to setup remote networking and binding the server CERT to the local and remote ip address so secure connections fail with certain clients.
Two Issues:
You appear to have 2 routers between the server and the internet with the server using UPNP to obtain a port forward from the second router that can’t be automatically set on the first router. In order for this to work you need to manually set port forwarding using the same port on both routers. Ideally only have one router.
Second issue is related to DNS-Rebinding. The second router does not allow Plex to bind its CERT to the public ip nor the local ip. The fix usually is to add plex.direct to the private domains list in your router’s DNS resolver if that is possible.
Restating your Account issue:
- You had a server claimed with an email#1 and password.
- You bought a Plex Pass but used a different email#2 and password
- You are not able to claim the server with the new email#2 and password.
First of all: thank you for your reply, it seems we’re getting somewhere now..
I used to be quite handy with computers and networking, but after a severe burnout I’ve noticed it’s sometimes impossible for my brain to understand and process more complicated things, sorry about that.
I do have an ISP modem that also acts as a router, for some reason it seems to be impossible to configure that into bridge mode, possibly because my TV is also connected to it. So.. my TV and my home-network-router are the only 2 devices connected to the modem (and first router).
The reason I suspected the Plexpass to be the problem was that I can still access local data on my android (and iPad) devices by using the old UsernameA, although that causes playback limits because the Plex apps on these devices don’t see an active Plexpass.
In the past I’ve configured port forwarding in both routers with help from the Plex troubleshooting manual, and that has worked fine untill I went to the lifetime Plexpass.
> Restating your Account issue:
-
You had a server claimed with an email#1 and password. CORRECT, with a yearly pass
-
You bought a Plex Pass but used a different email#2 and password CORRECT
-
You are not able to claim the server with the new email#2 and password. INCORRECT, Well, AFAIK claiming the server isn’t/wasn’t the problem, since I can access the server from the PC running the server without any problems..
As a test I’ve now set my ISP Modem/Router into DMZ mode which has resulted in the following confusing situation when using UsernameB (the new username):
Windows PC: Still works fine including access to local media
Android tablet&Android phone: NO local media access in the Plex app BUT I DO have local media access via app.plex.tv !
Android TV: NO local media access in the Plex app (browser can’t access app.plex.tvsomehow)
iPad: Impossible to login (I can live with that, it’s an old device anyway)
In ALL cases except the iPad, I DO have local media access with UsernameA ! But because that’s no longer connected to a Plexpass, it seems to have restrictions and wants me to buy a Plex Watchpass despite being in the same network ??
Since I seem to be able to access local media through app.plex.tv it seems to me that port forwarding and/or DNS can’t be a problem?
I know it might be a bit too much to ask, but would it be possible to do a step by step check on my settings in my ISP modem/router (Let’s say RouterA) and my home network router (RouterB)? I
And.. I don’t think it’s a good idea to keep DMZ in my modem/RouterA activated?
Here are a few suggestions I’d offer:
- When you’re using two routers daisy-chained, you almost never want to have client devices behind (connected to) the upstream one (the one you’re referring to as RouterA). Everything should be behind (connected to) the second router. Otherwise, you will almost certainly experience routing issues, some of which you are experiencing.
- If you can’t configure your upstream ISP router (RouterA) to be in bridge mode, then configuring it with a DMZ pointing to your downstream router (RouterB?) is appropriate and presents no additional security concerns (mostly true, though exceptions may exist).
- Double check that your server is claimed using your new account with the life-time Plex Pass. (I’m not sure why you created an entirely new account for your Lifetime pass, but c’est la vie.)
- Sign out of all of your clients and sign back in with your new Lifetime account.
The takeaway here is that you create a situation which is expected to work; you’re not currently there (as far as I can tell).
- One router handling routing for all devices on your network; no exceptions. Move that TV behind your second router. This includes Wi-Fi. If it’s enabled on your ISP router, disable it, or at least don’t connect to it. Only use your second router’s Wi-Fi network.
- Server and client devices all signed into the same Plex account (your new Lifetime account), at least to begin with. More complexity can be introduced later, once this baseline works.
