Server Version#: 1.19.1.2701
Player Version#: 1.8.2.1192
My Plex server just keeps transcoding all streams, even if I’m watching them locally.
Here’s the attempted playback from my Windows-client (via plex app for windows). As you can see, it shows a 91.-address - which is my WAN-address actually.
And this is when I access plex via dockerhost:32400 directly via browser (from the same windows PC: 192.168.1.144)
Is your server really running on Windows?
No it’s not. It’s running on OMV (Debian).
I created this topic in ‘server-linux’ - a mod just moved it to ‘server-windows’ - not sure why
Is there no update on this?
maybe some sort of firewall rule I need to set?
I’ve tried looking at the plex console output, but there don’t seem to be any errors
OMV isn’t supported.
the best which can be done is recommend searching the forums.
Logs would probably help to get some idea.
I’m not super familiar with looking at the logs but even though OMV isn’t supported per @ChuckPa, maybe someone from Plex can still at least help point you in the right direction based on the logs.
Also, based on the first screenshot, I’m wondering if you are on the relay which is limited to 2 Mbps I believe. I’m wondering if maybe you have an issue with DNS Rebinding going on. This link, https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/, has a section on DNS Rebinding.
Also, what are your settings for the the clients regarding streaming quality?
The more information given the easier it is to help out.
-Shark2k
You can’t be serious. It’s just Debian with some extra packages.
Also, I’m using the docker images!
This feels like such an arbitrary statement, just so you don’t have to deal with the problem.
“sorry, using portainer to start the containers isn’t supported - docker cli only”
my streaming quality settings are: ‘maximum for local’ and ‘2Mbps for remote’.
I’m guessing the problem stems from me using pfsense behind my ISPs router.
So I have a WAN-IP (on my ISPs router), which then has a LAN. My pfsense is a member of that LAN. But it also has another LAN internally - with my server in it (which is running plex in a container).
Internet --WAN-IP–> ISP-Router --Lan1-IP–> pfsense --Lan2-IP–> Server --Docker-IP–> Plex
the 91.x.x.x is my WAN IP. So I’m guessing pfsense doesn’t realize that it’s my ISPs Router, which is technically still local.
I have added
server:
private-domain: "plex.direct"
to my pfsense dns resolver. do I also need this setting on my ISPs router?
Yes, I am unfortunately. It’s more than just “debian”. OMV is a hypervisor with a whole lot of extras.
I’ve tried to make it work but do not have the time to dedicate to such an effort for such a small community.
Based on your network setup I’m not sure if what you added to your DNS resolver will help or not as the setup I run has pfSense directly connected to the internet and my network is behind that. When I initially set it up I added the same thing to my DNS resolver and have been fine ever since.
You can see if there is a setting in your ISP provided router that allows you to disable or modify DNS rebinding or if you can use a different DNS provider on it like the support article said.
-Shark2k
When running multiple subnets, the “other” subnet is “Remote”.
The best home lan topology is FLAT (single subnet).
It’s ok to make a 192.168.0.x and a 192.168.1.x IF the subnet mask is widened to /23
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
