Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plex is indirectly streaming and also not using aggregated upload speed #3738

Open
BATSO123 opened this issue Jan 4, 2025 · 5 comments
Open

Comments

@BATSO123
Copy link

BATSO123 commented Jan 4, 2025

Expected Behavior

Remote users should be able to directly connect to plex server and should have aggregated upload speed from both WAN's

Current Behavior

Plex shows an indirect streaming notification which suggests that port isn't forwarded properly. Also when the indirect connection isn't an issue the upload speed is not aggregated.
Screenshot 2025-01-05 004114

Specifications

  • OpenMPTCProuter version: 0.62-snapshot 6.6
  • OpenMPTCProuter VPS version: 0.1031.6.6.36-x64v3-xanmod1
  • OpenMPTCProuter VPS provider: Binary Lane
  • OpenMPTCProuter platform: x86_64

Current port forwarding setup
Screenshot 2025-01-05 004955

@BATSO123
Copy link
Author

BATSO123 commented Jan 5, 2025

Screenshot 2025-01-05 110311
This is while using remote streams. It seems that the TCP streaming is only getting used by the master WAN

@sieade245
Copy link

sieade245 commented Jan 5, 2025

I've had similar issues. In my case, not only could I not get secure connection. I couldn't get ANY connection on the LAN to the plex server sometimes. Worse, when it did work (insecurely), even though I was on the LAN, all the plex video traffic would go external out onto the internet and back via the Plex relay service which caps out at 2Mb/s. I've played around with the settings and not sure exactly which one sorts it out, here's a list:

I signed out of the plex app on my TV and added the plex server manually. This allowed plex to work as it bypasses all of the nonsense Plex have added in the past 10 years. You can rock Plex like its 2014 again.

I turned off DNS rebind protection in NETWORK>>DHCP AND DNS>>GENERAL SETTINGS. The plex support guide hints than rebind protection can cause the issues where it goes out onto the internet instead of staying in the LAN. I tried some troubleshooting but no matter what DNS settings I added, I couldn't get Plex to work with rebind protection left on.

I gave the plex server a static IP address in NETWORK>>DHCP AND DNS>>STATIC LEASES

I used the Plex interface remote access configuration page (server>>settings>>remote access) to manually specify an external port for port forwarding. UPNP doesn't seem to work properly at all in OMR. I used port 24080.

I used the Plex interface network configuration page (server>>settings>>network) to manually specify an ip range of addresses and networks that are allowed without auth (this was mainly so No 1. above would work but I left it on). My OMR uses 192.168.12.1 so in this box I put "192.168.12.0/24"

In NETWORK>>FIREWALL>>PORT FORWARDS, I added 2 port forwards:
-Incoming IPV4 from WAN to "this device" on Port 24080, forward to the static IP of the plex server on port 32400.
-Incoming IPV4 from VPN to "this device" on Port 24080, forward to the static IP of the plex server on port 32400.

I added both the WAN and VPN as some of my other port forwards need this (for example StorJ) to work properly. Not sure if plex needs the VPN one

NETWORK>>FIREWALL>>TRAFFIC RULES, I added 2 rules for plex
-Incoming IPV4 TCP/ UDP from WAN to LAN on Port 32400, accept forward.
-Incoming IPV4 TCP/ UDP from VPN yo LAN on Port 32400, accept forward.

Again, unsure if the VPN rule is needed. Now I have it working I dare not touch any of the settings as I've noticed there are several bugs with the firewall settings.

For example, if you have multiple VPS in the wizard, the updated firewall settings seem to only be sent to the VPS top of the list, even if this isn't your current VPS in use. After I discovered, this I removed all my secondary VPSs and just change them manually now in the wizard.

Next issue, if you make a firewall change, the settings don't seem to apply, even after a OMR reboot, unless you also make some kind of significant change in the wizard. I've been changing my proxy from Xray to V2ray and back again. This seems to do the trick but even this doesn't always work. This also affects OMR bypass too in the same way. The reason I mention this is this was the main problem which stopped plex working for me. I thought I had it correct in the firewall, but it didn't work so I made change after change after change before realising that none of the changes were actually being implemented by OMR server due to these bugs. Hence the reason I dare not touch it again!!

The good news is that after doing all of this, Plex does work properly with secure connection and be fully accessible outside of the LAN for internet streaming. I don't need to use No.1 above anymore, but to be honest I prefer using it this way as it removes all the Plex bloat they added.

Hope this helps.

@andrewmackrodt
Copy link

I turned off DNS rebind protection in NETWORK>>DHCP AND DNS>>GENERAL SETTINGS. The plex support guide hints than rebind protection can cause the issues where it goes out onto the internet instead of staying in the LAN. I tried some troubleshooting but no matter what DNS settings I added, I couldn't get Plex to work with rebind protection left on.

@sieade245 I came across this recently too, if you want to get this working:

  1. If Rebind Protection is enabled under Network > DHCP and DNS ensure that plex.direct is added to Domain whitelist
  2. Go to Services > Recursive DNS > Unbound > Advanced and set Filter Private Rebind to No Filter

@sieade245
Copy link

I turned off DNS rebind protection in NETWORK>>DHCP AND DNS>>GENERAL SETTINGS. The plex support guide hints than rebind protection can cause the issues where it goes out onto the internet instead of staying in the LAN. I tried some troubleshooting but no matter what DNS settings I added, I couldn't get Plex to work with rebind protection left on.

@sieade245 I came across this recently too, if you want to get this working:

  1. If Rebind Protection is enabled under Network > DHCP and DNS ensure that plex.direct is added to Domain whitelist
  2. Go to Services > Recursive DNS > Unbound > Advanced and set Filter Private Rebind to No Filter

Thanks for this info. I'll give it a shot!

@sieade245
Copy link

@andrewmackrodt You Absolute Legend!. That is working. I spent literally hours on that. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants