Nov 12, 2021 11:46:21.345 [0x7f969f5d8b38] DEBUG - Request came in with unrecognized domain / IP '192-168-50-60.hadiahmedk.direct.quickconnect.to' in header Host; treating as non-local
You clicked the “Open” button in Package Center after installing – AND – are signed into Quick Connect. (notice the URL it shows is not your LAN IP ?)
Thank you for your quick response! But I just so happened to figure it out after hours and hours of searching and troubleshooting.
I think I read in one of your other threads what my issue was.
I am running 7.0. And I was using quick connect. When I logged in to the NAS IP directly, not using quick connect, that finally allowed me to launch the Plex media server without the error message, and for the first time it led me through connecting to my server. Thank you! And now that I did that, it is allowing me to access PMS through quick connect as well. There needs to be a major public service announcement about this simple solution that is easier to find. Maybe a video on YouTube addressing this issue for all the 7.0 users.
LAN IP addresses are NOT routable so you’re safe to share them openly.
I can share my workstation is 192.168.0.13, my wifi AP is 192.168.0.8, my NAS is 192.168.0.20. It doesn’t do anyone any good because they aren’t connected to my LAN. They first need my WAN address (Public IP) and then break through my firewall which is a tall order.
Per RFC-1918 , which is the specification for Private Network, the address ranges you can use are:
– 192.168.x.x
– 172.16.x.x → 172.31.x.x
– 10.x.x.x
This is the chart at Wikipedia which summarizes the RFC-1918 specification Plex uses.
It sounds like you need to go into your modem/router and change your LAN segment base subnet address to be compliant.
If you use DHCP, confirm the DHCP lease addresses are also going to be changed to the new subnet value.
Then, Restart the modem/router and all devices so they pulll (get) a new IP address.
Obviously, your bookmarks for things on your LAN will need updating.