PLEASE ask further if I’ve missed any points / questions.
From there, maybe we can make everyone else’s work?
Comcast ISP
– XB8 modem in ‘Bridged’ mode (turns off the LAN router & WiFi)
– ( XB8 still does the Comcast hidden things but not a factor)
Direct wire from XB8 (2.5G port) → WAN port of PfSense
– You configure an untrusted port and a trusted port when you install.
– ISP → Untrusted port
I always work from the modem/router → host and while at the host, test &
At the pfsense, I create a NAT / Port Forward rule
From: ANY address
From: ANY port
Whose destination: my WAN Address
Whose port: “Other” 31415 → 31415 (this is what we’ll tell Plex to use)
Redirect Target IP: 192.168.0.20 (My server LAN IP)
Redirect Target port: 32400 (Plex’s port)
SAVE the rule,
Enable it
With pfsense rule created.
At your computer -
– If using anyone else’s firewall – You MUST allow 32400/TCP
– I turn machine firewalls OFF. (If they get into my network, I have bigger problems
In Plex:
Remote Access – OFF
Remote Access – ON (let it fail)
Manually add the port - 31415
Retry
Beyond this, I further restrict access
Only known IP addresses (by IP, subnet, or FQDN)
I must also allow Plex to probe the machine – they need permission to do so
Adding this restriction means I have to add another set of rules and aliases.
Unless you’re in a very hostile area. A random port from 14000 → 65535 (except for Plex’s well-known ports) should be good.
I’ve used:
– sqrt(2) - first 5 digits
– sqrt(3) - first 5 digits
– Pi - first 5 digits
– Get the idea ?
It does.
Message from Can You See Me with IP x’ed out. Success: I can see your service on xxx.xxx.xxx.xxx on port (yyyyy )
Your ISP is not blocking port yyyyy
No. I even went so far as to turn off Defender briefly to verify it was not a local firewall problem.
I’ve had this configuration working for years. The problems just started with an update in the last few weeks, two months max. From what I have read on the forums, it sounds like it might be related to SSL certificate issues?