Remote access settings for IPv6 on Synology NAS and Router

1 Like

It’s not actually a server ID, it’s a certificate UUID; how you find it depends up the host on which you run your Plex Media Server:

  • Windows - In Regedit, navigate to HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server and find the value of CertificateUUID.
  • macOS - Run defaults read com.plexapp.plexmediaserver CertificateUUID.
  • Linux - Find your Preferences.xml file in your Plex data directory and locate the CertificateUUID parameter within.
  • NAS - Generally found in your Preferences.xml. Where it’s located depends on the NAS.
1 Like

Thank you. I will try it later. And provide you with the log files.

@ChuckPa
Attached you“ll find my log files.

Logs removed

Can yxou delete the files after downloading? Or isn“t there any personal data stored in it?

My current IPv6-address of the RaspberryPi is reachable from the Internet. I have IPv6 available on my mobile device, from which I am trying to access the server…

But I only get an indirect connection to the server with a 2 mbps transcoded stream. I“ve got an internet connection with 400 mbps down and 200 mbps upstream.

1 Like

@Knifte

Thank you for those logs.
Your logs don’t contain any personal data.
The only thing remotely personal is your IP address.

I’ve looked at them and see what PMS/Plex.tv are doing.
I don’t think it’s handling the CGNAT / IPv6 scenario well

To that end, i’ve asked both the Plex.tv & PMS teams to look at the logs.

2 Likes

Thank you in advance! I am really looking forward to get this problem solved.

If there is anything I can do (further testing and or logging) or something else, just contact me.

1 Like

Do you have control of your modem/router in a way that you could configure:

  1. IPv4 on the inside – to preserve your LAN as it exists.
  2. IPv6 only on the WAN – disable the CGNAT IPv4 part

I’m working with both teams on this.

While the work for IPv4 & IPv6 is complete, the handling of CGNAT preceding IPv6 (both stacks active) may need some correction.

This is what I’m working on now.

1 Like

I am using a FritzBox 7590 (German Router). I am not sure if it is possible to deactivate IPv4. I will try it tomorrow.

@Knifte

I’ve done the full investigation (formal) as much as I can from where I sit.

I’ve written it up, referenced your logs, showed excerpts which document what is being seen, and asked for feedback.

It does look to me as if it surrenders to the IPv4 failure prematurely.

we’ll know more when they’ve had time to review

2 Likes

@Knifte

I had a 2 hour conversation with the team this afternoon.

We verified a great deal of what is working correctly.

We did conclude that one of the apps is not asking for the IPv6 address or is not using it correctly.

We worked out what needs to be done in the interim.

If you’ll assist me, it will help so we can figure out the specific app and what is not happening as it should.

  1. Independent of what your Plex/Web app is showing you (Imporant)
  2. With Remote Access enabled
  3. For whichever app isn’t able to access remotely, enable the debug logging.
  4. Now recreate accessing via WAN ( normally through the app)
  5. When it fails, grab those logs.

Here’s the link to the support article for how to obtain the Debug logs for each of the different apps.

If you’d be kind enough to grab those logs which capture it not working, We can get this fixed.

2 Likes

Thank you very much, I just created the logs from my iPhone 12 plex app ( Vodafone as mobile carrier). Later I can provide you with iPad and/or Android logs.

Log removed

Here another log from my iPad with another mobile carrier (Dt. Telekom):

Log removed

Both mobile carriers are IPv6 capable and provide an IPv6 to my mobile device.

Edit:
Another log from the iPhone with the updated version of the Plex App:

Log removed

1 Like

Same here, days of testing and trial and error. Pages and pages of tutorials with the same steps, scanned ports 1 million times, 3 days. wasted life time, I’m done with it, I don’t want to do it anymore.
This should be much better prepared for end customers, more tools for testing.

I don’t need any preinstalled apps on a Synology if only Linus Torvald can get it running in a waking moment.

German Cable (Vodafone KDG)
AVM 6591 (Provider)
Syn 220+

@meickel maybe you could also provides some logs from your apps as explained above.

Vodafone Cable uses dual stack lite, as far as I know, which is quite similar to CGN (as far as I understand it - but I am no network specialist).

Hopefully the team will find a solution which will make it much easier to set up.

@ChuckPa I could also setup a Plex Media Server on a Nvidia Shield TV pro 2019 model. This seems to change its IPv6-address very often (I guess it has something to do with privacy extensions, but I am not sure). Because of that I switched to a raspberry Pi 4 als PMS, because there I have the full configuration possibilities for the IPv6-address, which I do not have on the Nvidia shield device.

@Knifte

Thanks for the logs. I’m going through them now.

Who is the megarena FQDN?

I can see an IPv4 address but am not getting an IPv6 address for it.

I can see where the app (iPhone) talks to it via IPv4 but has no connectivity via IPv6.

I’m not seeing ANY IPv6 references.

Further, I see this which is not a good sign.

PMKEventSourceManager.m:211 | Channel connection to Cloud (plex.tv) - server,cloud failed with error: Error Domain=NSURLErrorDomain

This is starting to look like the alternate URLs have a problem with IPv6 support.
Can you provide any information about the relationships?

The megarena FQDN is a Portmapper where IPv4 tcp-Traffic is forwarded to my IPv6-address of the raspberry. I tried this

I can provide you with logs without any alternative URLs if that would help you.

I have no idea, what this error message means.

@ChuckPa ok, I removed the alternative address with megarena and now it seems to work. I just used the abovementioned https://aaaa-bbbb-cccc-dddd-eeee-ffff-gggg-hhhh.serverid.plex.direct:32400 as alternative address and it seems to work.

Attached you“ll find the logs from my server and the iphone app. Maybe there will be a more intuitive solution?

Logs removed

If you want, i can try without any alternative address.

@Knifte

The more intuitive is ā€œfully automaticā€ & without custom URLs

It’s not wise to use your Plex private domain map URL when you publish.
That’s a major security hole being created.

Every app has the full list of IP addresses (v4 and v6) from Plex.tv
The app tests each for connectivity and then uses what does connect.

In your situation, IPv4, which is now CGNAT, will fail.
It should find the IPv6 address normally as it continues its scan.

The bad URL was pretty much killing the whole server externally because it doesn’t seem to support IPv6

OK, then I have to excuse me for my missunderstanding.

I will try to delete the alternative URL tomorrow and try if a direct connection will be possible. But I tried that several times before and it did not work.

If you can’t get normal to work then there might indeed be a problem with the applications.

This is the first step in my diagnostic process; Do the apps make their normal and proper scan of the addresses provided by Plex.tv

When you specify a manual URL, it bypasses all that.

@ChuckPa ok, understood. I just removed the alternative URLs from the networking section and stopped and restarted the server. So without these entries it isn“t working properly.

During the transcoded playback I receive a message in the app, that the connection to the server is very weak/slow and correct playback is not possible.

Connectiing via the iphone app is very slow then and only an indirect connection is possible. Please find attached the logs of server and client.

Logs removed