I am running Plex on CentOS7 and originally did the quick and dirty port forward of Plex's port 32400 to the world.
I thought that I would try and harden that cowboy method by using WAF.
This is what I did:
Protect --> Web Server --> Add
Name: Plex
Host: My CentOS Box
Port: 32400
Keep Alive: On
Timeout: 300
Disable backend connection pooling: Off
Protection Policies:
Add
Name: Plex Port
Pass Outlook Anywhere: Off
Mode: Reject
Cookie signing: off
Static URL hardening : on to /web (as Plex is http://server:32400/web
Form Hardening: Off
Antivirus: On | Mode: Sophos | Direction Downloads | Block unscannable content: Off | Limit scan size: Off
Block clients with bad reputation: On | Skip remote lookups for clients with bad reputation: On
Common threat filter: On
Rigid filtering: Off
Skip Filter rules: Blank
Everything else: Ticked on
Firewall Rule: Business App Rule --> WAF
Hosted Address: Port2
Listening Port: 32400
HTTPS: uncheck
domains: plex.mydomain.com
Web Server: Plex
Allowed client networks: Any IPv4
Advanced:
Protection: Plex Port
IPS: Off (Tried it on too)
Traffic shaping None:
Disable compression support, rewrite HTML and pass host header: unchecked
When doing this, plex reports an indirect connection and uses a relay which in turn ruins streaming quality.
If I do the quick and dirty port forward, it works great.
I then read at: https://forums.plex.tv/t/only-have-indirect-connection-to-my-plex-server-on-my-local-network/206836/7
That this can happen if DNS rebinding protection is in place in your router.
I need somebody who understands WAF to assist me in resolving this issue.
Thanks
This thread was automatically locked due to age.