Server settings and Setup Wizard don't appear when connecting over IPv6

Plex Media Server Desktops & Laptops
1

Server Version#: 1.25.2.5319-c43dc0277
Player Version#: Chrome, Firefox and Edge on Win 10

Hi all,

Running Plex, installed from the repository, on Ubuntu 20.04.3 LTS x64.

This afternoon I updated a bunch of stuff and noticed I could no longer connect to my Plex server from any of my devices, or the Web Player, on the local network. I can connect to the locally hosted (port 32400) instance of the Web Player, and so I know Plex is running, but none of the server configuration options appear. I’ve subsequently purged the plexmediaserver package, deleted all the remaining configuration data I can find, and when accessing the local instance I don’t get the Setup Wizard, just the Web Player with no server settings or any of my media.

Things I’ve done:

  • Ensured the server and the client machine are on the same, wired network
  • Disconnected all VPN connections
  • Disabled DNS rebind protection on my router
  • Flushed the DNS resolver cache on Windows
  • Signed out and back in to all instances of the Web Player
  • Tried it in Chrome, Firefox and Edge
  • Created a new user account via the locally hosted instance of the Web Player
  • Done sudo apt purge plexmediaserver, also removed everything under /var/lib/plexmediaserver, rebooted, and then added the latest plexmediaserver package as described here
  • torn out some hair
  • done a lot of googling
  • had a beer
  • remained stuck without access to server settings or the setup wizard
  • posted here

Please help! My kids are going to be sad that they can’t watch movies!

2

James,
Is the server another computer on your LAN or are you attempting to connect to it from the server’s keyboard session ?

If another computer in your LAN, is your LAN RFC-1918 compliant ? (192.168.x.x, 10.x.x.x, 172.16.x.x-172.31.x.x)

Did you install from the Ubuntu App Store or manually instally after downloading the DEB file from Plex.tv/downloads ?

1 Like
3

2 posts were split to a new topic: New installation Synology - DSM 7

4

Hi Chuck. Thanks for getting back to me.

It’s another computer. My server is headless.

Both machines are in the 192.168.1.x IP range.

Having said that, I do also run IPv6 on my local network. Hmm. Do I need to ensure the initial connection is via IPv4?

I installed from the Plex repo after adding it in /etc/apt/sources.list.d/.

5

Well, there we go! I’ve now connected via the server’s IPv4 address as opposed to using its hostname, and the setup process is working as planned.

So is this an IPv6-related bug? I can’t be the only person running IPv6 on their home network!

6

@jamesherbert

Use of IP address vs hostname is tricky.

If the URL you use to connect to the hostname is a FQDN – it’s retreated as non-local because Plex doesn’t know the FQDN is local until AFTER you add your cert to Plex AFTER claiming.

You must have IPv4 enabled in the host’s stack. 127.0.0.1 (the loopback) is required for Plex to work.

It’s weird way of doing things but not a bug. All this stems from the clients working in WiFi cafes and making sure the server isn’t compromised. I don’t understand it and therefore don’t understand why the strictness.

7

Surely it cannot be intended behaviour to have to manually determine the IPv4 or IPv6 address of the server in order to perform first-time setup?

If so, I feel that the documentation is rather lacking on this detail. I spent several hours getting increasingly frustrated over this.

Thank you again for your support.

8

@jamesherbert

The main problem is that Plex.tv is not fully IPv6 supporting.
(the main provider – AWS – doesn’t have dual-stack for Plex)

It’s a known problem… and a big problem at that.

Plex has always been IPv4 until recently when IPv6 LAN support was added.

IPv6 WAN brokering through Plex.tv for Remote Access / Authentication is where it is still deficient and being developed.

9

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