Hi,
I am new to the DXP4800plus (got mine 2 weeks ago) and I’ve been working with linux containers in proxmox a lot, but I am very new to Docker as well. So I’ve been trying to get docker to work, the platform is running properly AFAIK, but the apps are dreadful, so I must be doing something wrong. I am not sure about the networking portion of the docker containers. Please forgive my ignorance, I’m trying here! I’m doing all this in the GUI, should I be using yamls (docker compose) instead?
So I want to try Plex and some other dockers.
linuxserver/plex
The problem here is that after deploying (using the youtube guide from ugreen) Plex is running alright, no errors in the docker log, and I am able to add libraries through volumes based on NAS-folders. So far so good. However, none of the apps (my google tv, android phone) are able to connect whilst on the same LAN/WLAN. It just keeps saying “unreachable” and the server is marked with an icon with an exclamation mark. I am able to connect to Plex at any given time using the Plex local website. I have tried the Plex troubleshooting guide, and it says something about clients having to be on the same subnet, but how does that work in Docker? It is currently connected through a virtual bridged network in the 172.16/24 range, my actual lan is in the 192.168/24 range. Is that why this isn’t working? Or is there something else I’ve done wrong? I’ve tried creating a new network in docker, and specifying my 192.168/24 range, but that errors out due to a conflicting subnet. So my guess here is that the current situation should be fine. Then there are ports, by following the same youtube guide, the AI narrator states no port overlap can exist on the NAS (duh), so this gives me all kind of random ports on the NAS ports portion of the portmap. To my understanding these are ‘random’ ports and I cannot imagine my clients just being able to guess those, hence the connection would not work. Should you align the NAS ports to the docker ports for as far as possible to prevent this? Is this common knowledge (which I’m lacking obviously?). Please let me know!
Linuxserver/wireguard
Another docker that’s been hurting my head is the wireguard one, which I’ve been using as a LXC on proxmox for years as well, but translating it to Docker seems to mess with my logic. I am able to set up the docker using the guide provided. It creates a docker with no errors in the logs and in the attached volume I get 2 peers (as specified in the peers environment variable). Scanning the QR codes on the clients works, but when trying to connect it clearly fails. Some bytes are sent from the clients to the server, but 0 bytes are received from the server. I’ve forwarded the NAS port on my router to the ugreen host ip, but still nothing. I can’t seem to be finding any logs regarding this either.
openvpn gateway
Last but definately not least, my openvpn gateway. So you must have guessed it, I’ve been running this on a linux container in proxmox for quite some time now, and I use this for specific clients on my LAN (the 192.168/24 network). However, after setting everything up using several guides provided - in Docker, I can use the ugreen host IP as my gateway, but it fails to provide any kind of internet. I still have the linux container for this matter, when comparing them everything seems in order. I then decided, I have a 2TB SSD and 64GB DDR5, why am I not just creating a thin VM? I did, but guess what, exactly the same; no internet connection through the gateway whatsoever.
So I’m pretty sure all my issues are coming from my lack of true network understanding of the Ugreen and Docker. Could anyone PLEASE point me in the right direction?
Many thanks (you truly have no idea) in advance.
PS: I forgot to add, i am able to get homeassistant as a VM to work (i have several USB passtrhough issues where I cannot find my zwave stick AT ALL, but that’s not a network issue). I have qbittorrent running (not that I’m using it at all, but as a simple test and that works). I also have adguard home as a docker running that’s working properly. So not everything fails ![]()



