I’m running Kubuntu, and my PMS has 2 network cards. 1 is connected directly to my modem and one is connected to the WAN. Reason for that is that I have double NAT (using Google Wifi).
In order to get remote access to work, I need to set the default gateway to the IP of my modem.
Using the command sudo route add default gw 192.168.0.1 makes it work, but after a restart I need to use that command again. How can I save my default gateway so I don’t have the remote access issue anymore?
Have you considered telling Plex which network interface to use (in combination with a manual port forward)? Settings > [Server Name] > Network > Preferred network interface
However, after a restart I still need to open the Plex web interface and go to the “Remote access” setting in order to make it work. Important note: I do not have to click on “retry”. For some reason I just have to go to this tab.
How can I solve this issue, so at start up I do not need to open the web interface?
Meaning you cannot access your server from a device outside your home network until you opened the remote access settings? Or is it just he remote access status indicator that takes a moment to “turn green”?
Meaning you cannot access your server from a device outside your home network until you opened the remote access settings?
Exactly this.
After I restarted I tried to use Plex with my phone on mobile data:
before I logged into the PC-> didn’t load my content
after I logged into the PC → didn’t load my content
after I opened the web interface and logged into my Plex account (using my PIN) → didn’t load my content
opened remote access settings → loaded my content
Edit:
Weird. I just tried to access my content and it didn’t work, although I didn’t restart my PC. Then I opened the remote access setting and now I am getting the " Not available outside your network" again. Clicking on retry doesn’t remove the message.
However, after clicking on retry I am able to access my content now outside my home network even though I have the “Not available outside your network” message…
I just ran the command again and now the remote access issue is gone again:
sudo ip route add default via 192.168.0.1
I had a Synology DS918+ where I had to utilize both ports as well. It worked there just fine. I basically just switched the device with a PC and adjusted the settings in the modem. So, I guess it’s more of a configuration issue on Kubuntu right now.
When you have a nice clean FLAT (one subnet) LAN,
only one router between you and the internet,
firewall port 32400 open on the server machine itself.
Remote Access will work.
If you have the Gnome desktop (most do), or any type of “Network Manager” app which will write the “Default Route” into the configuration permanently for you, do it.
Linux these days is very “Point & Shoot”.
DHCP gives you the default gateway & default route from the server if you’ve setup one (most ISP devices have DHCP services enabled).
Gnome - Settings - Network is the Network Manager app I just eluded to. In there, in the GUI, you set these parameters and they persist until changed.
Not connecting the PMS to the modem gives me issues due to double NUT. Not connecting the PMS to the G-Wifi WAN gives me issues playing media on the network. Before I build my own Server I used a DS918+ NAS, where I had the same issue. However, after connecting it to the G-Wifi WAN and choosing the default gateway (modem), everything worked like a charm.
I am not sure if can follow you. I guess what our are saying is to get rid of double NAT?
When I initially set up Google Wifi I had issues. After hours, I ended up using the Google Wifi’s subnet in this configuration above. This way the mesh network worked. Later on when I got my NAS I got the double NAT issues.
In order for you to help me, maybe the section "(Not Recommended) Enable Bridge mode on your Google Nest Wifi router or primary Wifi point " of the G-Wifi support page may get us further.
Internet service comes in to your main switch (which is what defines your local LAN)
From there, everything is a fan-out.
The mesh wifi is for the player/client devices still on the same subnet.
Configuration wise,
Yes, everything on 1 subnet . (some folks think different subnets make it more secure; it doesn’t.
In the same way the external internet looks like one great big “wide open space” to you , you must configure your LAN to appear the same to your devices… Everything on the inside is “one wide open space”. The modem/router knows when to go “outside the fence”
