I can’t get a my vizio tv to connect to the local server via local or external ip, even though its on the same network. I’ve done everything I need to with pfSense according to Plex. Every other device on the same network and off the network can access the server. Server is available for remote access, ports are forwarded properly. private-domain: “plex.direct” has been added to my resolver. I’ve messed with secure and insecure connections, no luck. Plex console shows nothing of the connection attempts made to it by the local TV. I have no problem pinging the device from the plex server locally. If I cast PLEX to the built in chromecast on the same device it has no problem establishing a local connection. I’ve even tried swapping the assigned IP’s between the native vizio address and the built in chromecast because they are seperate, and I wanted to make sure some artifact’ed policy wasn’t blocking the port, because ICMP isn’t having an issue in either direction. So I took it one deeper. Here’s packet captures from the plex app when attempting to connect to the local server via the local address manually added:
09:18:12.205646 IP 50.116.51.249.443 > 192.168.23.195.52858: tcp 31
09:18:12.208284 IP 192.168.23.195.52858 > 50.116.51.249.443: tcp 35
09:18:12.247656 IP 50.116.51.249.443 > 192.168.23.195.52858: tcp 0
09:18:17.092489 ARP, Request who-has 192.168.23.254 (ff:ff:ff:ff:ff:ff) tell 192.168.23.195, length 46
09:18:17.092506 ARP, Reply 192.168.23.254 is-at 8e:07:72:73:74:02, length 28
09:18:21.687588 IP 192.168.23.195.52858 > 50.116.51.249.443: tcp 40
09:18:21.727127 IP 50.116.51.249.443 > 192.168.23.195.52858: tcp 0
09:18:22.206108 IP 50.116.51.249.443 > 192.168.23.195.52858: tcp 31
09:18:22.208820 IP 192.168.23.195.52858 > 50.116.51.249.443: tcp 35
09:18:22.246572 IP 50.116.51.249.443 > 192.168.23.195.52858: tcp 0
09:18:22.514746 IP 192.168.23.195.52716 > 52.22.29.255.443: tcp 31
09:18:22.559429 IP 52.22.29.255.443 > 192.168.23.195.52716: tcp 31
09:18:22.561750 IP 192.168.23.195.52716 > 52.22.29.255.443: tcp 0
09:18:24.082384 IP 192.168.23.195.37166 > 142.250.138.94.80: tcp 0
09:18:24.087433 IP 142.250.138.94.80 > 192.168.23.195.37166: tcp 0
09:18:26.129950 IP 192.168.23.195.37072 > 142.250.138.94.80: tcp 0
The only warning I get from console reads something from the old vizio address before I reassigned it:
[HttpClient/HCl#b5] HTTP error requesting GET http://192.168.23.200:9080 (7, Couldn’t connect to server) (Failed to connect to 192.168.23.200 port 9080: Host is unreachable)
and the error:
SSDP: Error parsing device schema for http://192.168.23.200:9080
The app is querying dns for some plex relay I’m guessing. Perhaps that’s supposed to tell it to look locally for the server but it’s not I’m guessing… Idk. Simple ARP who-has would have been nice but I guess PLEX would rather reinvent the wheel with resolving servers or there’s some deeper issue. I don’t see any traffic actually looking for the server. This really works me up as there’s a new issue with PLEX every week and I don’t have a suitable alternative, really sad… Anyway I’m sorry for being upset, but this issue I refuse to tolerate as I can’t stream anything to the living room TV without using a relay server of PLEX’s since that’s all their pointing service can regrettably discover (in theory). TBH I don’t know what’s going on because the documentation doesn’t explain how this server pointing resolves.
Truly baffling to have this sort of issue. I believe I understand the issue somewhat but I have no idea the fundamental problem here. Why does the app not just broadcast ARP for the addresses? Why is it seemingly querying pop.ewr.plex.bz for a connection instead of just ARP who-has? Am I even interpreting this right? This is insane. I’m joining this in insanity.
Just to be clear, the issue is isolated to the vizio app. It started when I replaced my old netgear with a protectli pfsense router. (KEY POINT) It’s so isolated that the app experiences the issue while the built in chromecast on the same device does not. I’ve followed the normal walk through’s for pfSense on the available documentation. I’m not new to networking so if it’s preferred any advice can get right to the point. In a last ditch effort I’m going to reassign the old 200 host back to the vizio to see if I still get the error/warning in console… If that fixes the issue then there’s a caching issue not updating to network changes on the Vizio app. Understandable. If not I hope someone here can point me in the right direction. This seems to be over engineered, or perhaps the design approach wasn’t robust or valued premium service subs in the future… Idk.
Server is running on an ubuntu 22.04.3 LTS VM on proxmox-ve 7.4-17
Route between endpoints (vizio → server) include one cisco SG500-28 linked to one SG500-52 both managed atm. Protectli vault (pfsense router) is sidechain to the first switch.
Server Version#:1.32.6.7557
Player Version#:5.70.0
Edit: +5mins
One more entry I noticed in console once I rebooted the server:
[Req#12] Unable to find client profile for device; platform=Tizen, platformVersion=7, device=23_X22UD_UHD, model=UN55CU8000FXZA
Edit: +15mins
Solved:
I don’t think some of these changes in network configuration can take affect without restarting services server side. Once I had given everything a full reset to allow the protocol to sync up, it seems to have fixed the issue. What’s most interesting to me is that XML seems to have been the cuprite. I don’t exactly how the server handshakes clients, but before restarting and having the issue resolved, I noticed a lot of console entries about XML posts failing to parse. They seems to be out of sequence because of my troubleshooting. I hope someone with a similar issue or a developer looking for similar use cases finds my post useful. As for now things work, so I’ll be done with this thread.
