Server Version#: 1.21.1.3830
Player Version#: 4.47.3
I recently switched to fiber and am dealing with the headache associated with IPv6 and Double-NAT. I have already read this very useful thread on setting up Plex with IPv6, but I still can’t get mine to work. I am hoping someone can help with this. I’m using Synology NAS and Synology RT2600ac router.
Also, I am assuming that for port forwarding, I’m still supposed to use the IPv4 address to forward the specific port I have set up in Plex to my NAS IPv4 address. When I open Plex, the Private IP that shows up under “Remote Access” is IPv4 and not IPv6. Is this correct?
When converting IPv6 to replaced colons with dashes, I read that plex doesn’t support “::” So is it correct that an address like this “2654:2405:8:3430::lc26” should be written as “2654-2405-8-3430-0-lc26”? In other words, the “::” becomes “-0-”?
Finally, where I’m especially confused is about the Firewall setup. In the router, are we supposed to open the usual IPv4 address of the NAS with the 32400 port or is it supposed to be the IPv6 address of the NAS without a port? My understanding is that IPv6 addresses don’t have ports specified separately, but maybe I’m wrong.
I’ve spent two days on this and tried almost every combination of IPv6 addresses (router, NAS, external NAS address), but cannot get Plex to be accessible remotely. I’ve already enabled IPv6 in plex and am testing the setup with Plex mobile on android on cellular network.
Note that before switching ISP, my remote access worked perfectly on IPv4. I would really appreciate any tips.
The Custom Server Address you specify is the External address / DNS name you wish Plex.tv to advertise. This is typically the FQDN of the server.
https://1c42-724f-235-211-463a-jack-ab13-c123.123ab4c5678901234d567890e1f23g45.plex.direct:32400 is the Plex-internal DNS name associated with your certificate. It is overlayed onto your LAN. It has no applicability in WAN address space.
If your LAN is still IPv4 - which mine is also - then don’t change the inside.
Your modem/router will translate the external IPv6 address through the NAT to IPV4
Ok, so I’m assuming this is supposed to be the External IPv6 address of my Synology NAS. This is listed under the “DDNS” settings “External Address” in the Synology NAS
My LAN is IPv4, but I also had to enable IPv6. I don’t know how else could my NAS get a public IPv6 address to be shared online. Are you saying my LAN IPv6 should be disabled?
So is there is not firewall rule to set up for IPv6?
I think I am completely lost in this mess. I just realized even my router’s external access has terminated now as I have been playing around about getting this damn Plex fixed. I had barely gotten at least my router to be accessible with IPv6 before and now that’s a step backward…
Are there any services where I can just pay someone to fix all this? I don’t know who I would even try to find that knows both the Synology side and the Plex setup side. We really need much better directions from Plex about this since the request to support IPv6 has been pending since 2013 and obviously this doesn’t have high enough priority.
My ISP simply doesn’t support IPv4. They told me they are considering leasing out IPv4 addresses, but that’s not an option right now either. So my choices are to stick with crappy mediacom because I can’t get Plex working or ditch mediacom for Fiber, but have no remote access to Plex. This is the third day spending on this issue. If anyone is using Synology and is willing to share the details of their settings, I would really appreciate that.
After a lot of troubleshooting, I was able to fix most of my network. But I am back to where I had started - I cannot access Plex remotely.
When I go to IPv6 scanner and type in my external IPv6 address for the NAS (this is where Plex server is), it says that port 32400 is “filtered,” so presumably it’s not open. When I type [IPv6 address]:32400 in my browser on my local network, I am able to access Plex. But when I try to sign into my Plex, I get the error " We were unable to complete this request. You will be redirected automatically."
So once again, it seems like this is a firewall issue. Does anyone have any idea? Are we supposed to open the firewall for the external IPv6 address? I already have both port forwarding and firewall open for port 32400, but that’s with my local IPv4 address for the NAS server.
Yes, Synology NAS is completely behind my Synology router
The NAS has only one ethernet cable connected directly to the Synology router. It’s not facing the internet directly. But the IPv6 IP address that I use in Plex belongs to NAS’s “External Address” made possible by Synology’s DDNS server. Maybe this is incorrect. But the only other option would be to use the “internal” IPv6 address of the NAS that starts with fe80. Although I tried that too.
The Plex machine (my NAS) does have an IP reserved, BUT IT IS IPv4 and I am forwarding port 32400 from all external IP addresses to the NAS IPv4 address. But again, there are no IPv6 addresses in port forwarding rules or the firewall. I still have my ISP service with IPv4 active (haven’t disconnected it). If I switch my router to that modem, Plex works perfectly. So this is an IPv6 issue it seems.
Something to mention again - my ISP allows no public facing IPv4 addresses. Therefore, all my IPv4 addresses are unreachable and any ports associated with them are considered closed. The only way I can reach a device in my network would be by the IPv6 address.
I have configured IPv6 to be in Stateless mode in the router. I don’t know if I’m supposed to switch this to a Stateful mode perhaps to get an external IPv6 address (with my IPv6 “Prefix”). I’m worried about changing this setting since last time it messed this up, possibly. But I could try it perhaps as a last resort, unless there are other opinions on what I might be doing wrong here.
DDNS should only report, through that external name, the current IPv6 of your modem/router.
That’s where that stops.
Everything from the modem/route and internal can be IPv4. (it’s a Private Network)
I just got a new ISP 2 weeks ago. I was planning on stepping things up to include V6 for all LAN devices (the modem/router is already dual-stack V4 & V6).
If you’ll give me a bit, i’ll resolve the v6 stateful vs stateless. I suspect you’ll want stateful but please do wait until I learn more.
Thanks Chuck. After a lot of network pain, I think I have it almost working perhaps. Stateful was indeed necessary because the NAS must have an IPv6 address that’s public and it seems it wasn’t possible without specifying Stateful. My last issue right now seems to be that the remote connection to Plex has become unsecure, I did follow the instructions to get the Server ID from the HTTPS certificate. So I don’t know why I’m having this issue yet.
That does require a router with support for IPv6 → IPv4 port forwarding, which might be a sticking point. Many only support forwarding for IPv4 → IPv4.
@Excel, are you using the ISP-provided router, or have you added something additional? Can you share screenshots from the Port Forwarding and Firewall / “Open a Port” screens for that device?
I find it odd that Synology (using either this or their other: Synology Router RT2600ac ) doesn’t support V6-V4 forwarding. They have been pushing IPv6 for a long time.
I’ve confirmed stateful (sorry for being slow).
You want that control. Stateful == DHCP for IPv6 is a nice way to remember it since it depends on the upstream.
I have removed ISP’s router since I couldn’t access anything behind it. My RT2600ac is directly connected to the ISP’s ethernet port and feeds into their outside network (set up as 10.0… in addition to IPv6).
I can provide redacted scrrenshots if it is necessary. But to describe it, under Port Forwarding, I have opened a specific public port (directing Plex to use that as well) to point to 32400 port on a LOCAL IPv4 address of the NAS (location of Plex). Under firewall, I have opened 32400 port for both the local IPv4 address and the IPv6 address (received from Stateful).
I should have mentioned this early, but after getting Stateful figured out, I can now see my IPv6:32400 as “open” in the IPv6scanner tool. So I know I got that working. Plex is also showing Remote Access as green. Chuck, note that as I mentioned previously, canyouseeme.org cannot work for me because any IPv4 address is blocked regardless of the port. Only IPv6 addresses work.
So with the IPv6 port open, I still have an issue where the Plex remote connection is “insecure” and also when I try to log into Plex locally through the IPv6 address, I still get the " We were unable to complete this request. You will be redirected automatically." error. I know I’m closer to get this working than at any time before, but this is close, but no cigar.
Alright, still cannot access Plex remotely, despite all the apparent progress. Even tried enabling unsecure access just to see if it works, but it doesn’t. This is one &$^#-in’ problem.
I have disabled Relay in Plex. With Relay, I can of course access it. But that’s misleading. Since my NAS cannot transcode due to lack of CPU power and Relay always leads to transcoding, I’m keeping it off. I would think this only helps with troubleshooting these issues…
@ChuckPa, I also noticed that both the Plex IPv6 and the IPv4 addresses in the Router firewall are not getting any “hits.” If you look at the Hits=2 above, that is all from running an IPv6 port scan. But attempting to connect to Plex remotely or even disabling/re-enabling Remote Access in Plex web settings does not generate additional Hits. So I’m assuming those requests never even reach my router? The router’s IPv6 address contains a section that is “XXXX::XXXX.” I have put this into Plex as “XXXX-0-XXXX” and I’m pretty sure that’s correct because when I did “XXXX–XXXX” without the zero, Plex remote access became red.
Hmm, I don’t think I understand. I was simply following the instructions in this thread that say to replace “:” with “-” before entering the address into “Custom server access URLs” in Plex. Here is the quote from that thread:
I need check with Engineering tomorrow on that one.
I have never seen a plex.direct DNS name used in that manner.
plex.direct is intended for use on the LAN as an overlay domain, not WAN but, again, I will validate its viability tomorrow when they are in the office.
