Hi folks. Apologies in advance - I am very much a Windows person from a professional perspective, but am "tinkering" with ProxMox and VMs, etc. at home for a personal home setup - mostly as I wanted to set up a dedicated Satisfactory server (which is working perfectly fine - including the port forwarding), a NAS (which is now working fine with SMB shares, etc. across the network), and a Plex server - which is working perfectly fine internally.
However, I've been struggling with getting Plex to maintain(?) a stable connection externally. When logged into Plex, it will come up saying there's connectivity issues... I refresh and tell it to try again - without changing anything - and it goes green for a while (30s-1m) and then back to the good ole orange exclamation mark.
I've searched through the forums (and elsewhere) and have found a few things relating to it... but no real fixes. Main "solved" one I found on here, the OP simply nuked and re-installed his countainer... which I'd prefer not to do. Not because it's hard to do (I installed the container via the helper script), but because I want to work out what's wrong, and fix it...
So, about my environment/setup:
Main differences between the Plex container, and the Satisfactory dedicated server, is that the server is running on a full-blown VM running Ubuntu Server 24.04.1 - which also has ufw enabled and configured to allow the port(s) being used by Satisfactory in my setup.
I did a sudo ss -tuln within my Plex container, and can see where it's listening for my INTERNAL port number configured in Plex, which made me wonder if I needed to also forward the internal port number (in case Plex was forwarding the external port number to my internal one), so I added a forward for that on my router also - but that didn't help.
I've also done the usual restarting of services, server, etc.
Any suggestions on how to go about working through this one would be appreciated
Cheers,
bob.
However, I've been struggling with getting Plex to maintain(?) a stable connection externally. When logged into Plex, it will come up saying there's connectivity issues... I refresh and tell it to try again - without changing anything - and it goes green for a while (30s-1m) and then back to the good ole orange exclamation mark.
I've searched through the forums (and elsewhere) and have found a few things relating to it... but no real fixes. Main "solved" one I found on here, the OP simply nuked and re-installed his countainer... which I'd prefer not to do. Not because it's hard to do (I installed the container via the helper script), but because I want to work out what's wrong, and fix it...
So, about my environment/setup:
- Running ProxMox 8.2.2
- Firewall at the proxmox "node" level is on - BUT at the datacenter level it's currently disabled.
- Plex is running in an unpriv'd LXC container - no firewall currently enabled
- I can quite happily connect to the Plex instance from other machines on my internal network
- The Plex container has a DHCP reservation for the MAC, as well as a port forward for my custom external port set within my eero router config
- I've had my modem removed from the ISP's NATing setup the folks in our area were set on, so I have a direct connecting to/from external (and as mentioned, I am currently hosting a Satisfactory dedicated server which my friends are playing on regularly... so the external access, and port forwarding in general, are working fine
Main differences between the Plex container, and the Satisfactory dedicated server, is that the server is running on a full-blown VM running Ubuntu Server 24.04.1 - which also has ufw enabled and configured to allow the port(s) being used by Satisfactory in my setup.
I did a sudo ss -tuln within my Plex container, and can see where it's listening for my INTERNAL port number configured in Plex, which made me wonder if I needed to also forward the internal port number (in case Plex was forwarding the external port number to my internal one), so I added a forward for that on my router also - but that didn't help.
I've also done the usual restarting of services, server, etc.
Any suggestions on how to go about working through this one would be appreciated
Cheers,
bob.
