Plex Media Server on Ubuntu unclaimable and inaccessible

Plex Media Server
27

I believe so, let me double check.

Yep, completely up-to-date.

28

Good.

Let’s keep an eye on it

Please advise in the morning?

29

Sorry I’m a little confused, I’ll restart my server and it will automatically unclaim itself and I’ll have to go in and do it manually, is that supposed to happen? Do you want me to keep the server on and send updated logs in the morning?

30

Are you saying this will unclaim the moment you stop PMS?

If it does this:

  1. Get a set of logs now so we have good ones
  2. Get a fresh set again when you start it up

This gives us a solid comparison.

31

Yes, it will unclaim itself and I’ll have to manually claim the server again.

Give me a sec I’ll grab some logs.

32

On a completely non-related thought –

Was there a reason you installed from the Ubunutu app store and didn’t use the native app from Plex.tv/downloads ?

33

Nah, I installed the latest version of Ubuntu and it popped up during the installation menu as one of the recommended apps from the snap store, I saw it was verified from Plex so I figured it would be easier to grab in the moment.

Here are those fresh logs.
Plex Media Server Logs_2022-08-30_02-01-14.zip (1.3 MB)
Plex Media Server Logs_2022-08-30_02-03-15.zip (1.3 MB)

34

Thanks for this.

I tend to use the native package because I find it easier to work with.

Snaps have their own environment within the normal Linux environment.

When I use native, I’m on the clean base Ubuntu

Regarding this problem, I will setup an environment and see if I can reproduce it.
If I can then I’ll discuss with Engineering.

If not, I’ll try to find a way forward

37

@lexi_plexi

I have found something which I need to discuss with Engineering.

39

@lexi_plexi

I have done some investigating here.

Do you have multiple subnets on your home LAN ?

If you do, is this PMS server on a different subnet than the default subnet the modem/router creates ? (e.g. default=192.168.0.x and this is on 192.168.5.x )

40

I don’t know how it got set up to do that and why it’s an issue now when it’s been working fine the past few months, but yeah I guess I do, just looked and the server’s IPv4 is different than the default.

I still don’t see how this would be an issue now when the server has been running smoothly prior.

41

@lexi_plexi

That’s what I’m trying to figure out too.
It seems as if double NAT ( a NAT VM inside your LAN ) triggers is.

I can confirm, when my VMs have regular LAN IP addresses, all is fine.

42

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.