Double NAT thought

Hi all
I am trying to explain my situation.
We are living in an area where we can only get limited DSL speed and no other internet connection is available.
LTE coverage is perfect.
Since a German manufacturer (https://en.avm.de/products/fritzbox/fritzbox-6890-lte/) announced a combined router (DSL and LTE) we are using it and are happy about the overall speed.
Not regularly but quite often we have connection problems to our PLEX server. Checking in that moment the PLEX app shows a connection error and the “path” shows a connection through the Carrier-grade NAT of the LTE provider.
The manufacturer of the router confirmed my empiric impression that the router always makes the DynDns connection over the public Ip4 address of DSL.
Why can PLEX not check the Ip4 address related to the domain?
In cases of breakage of connection, I can always access the PLEX app with my domain which proofs that the server is accessible over the internet resp. from outside.
What’s your opinion?

This is indeed tricky. It’s not really Plex’s fault - if the router sometimes routes traffic over DSL, sometimes over LTE, then Plex can only detect the external IPv4 addres of the connection that it is given by the router.

Is there a setting somewhere on the Fritzbox where you can force certain clients over 1 connection?

As you’ve found out, using your own domain name pointing towards the DSL IPv4 address will work. You might also try to add to the Custom Server URL list: https//123-123-123-123.2e6297f47a94e23b.plex.direct:32400 (replace 123-123-123-123 part with your DSL IPv4 address, with dashes instead of periods, and replace the .2e62... part with your server id), then clients should always have the correct dynamic DNS address to connect to, or at least: until that DSL IPv4 address changes.

You can tell PMS which address to publish (the DDNS FQDN address) in Settings - Server - Network using

Custom server access URLs

In fact: PLEX is working perfectly also behind this Double NAT router since the domain with certificate is implemented properly.
Great!

Somebody any idea what could be the reason that it does not work anymore from outside our network.
Really nothing changed…
Using it fro outside our network (over the internet) does not work anymore.
Worked for around 1,5 months…

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