Server Version#: 1.41.3.9314
Player Version#: 4.142.2
I noticed that one of my test installs was using my wan-ip plex.direct link, and not a local one as it should. I checked console, to discover :
Access to XMLHttpRequest at 'https://10-0-40-6.c9edefdb7f3149e99ef96d1bc9f2c726.plex.direct:49374/media/providers?querystring' from origin 'https://app.plex.tv' has been blocked by CORS policy...
Specific Error:
Response to preflight request doesn’t pass access control check:
No Access-Control-Allow-Private-Network header was present in the preflight response for this private network request targeting the private address space.
This happens on newer chrome instances (though not on safari). I imagine it’s a newer addition to the CORS spec – i haven’t really kept up with that lately, so I’m not 100% sure, but that’d be my guess.
Just to be clear, you’re saying you experienced this behavior with a browser on a (local to your network) host connecting to your server via https://app.plex.tv, right? With Chrome you experience the above-referenced behavior, with Safari you don’t. Is that right?
Are these session showing as non-local/remote connections in your dashboard? Is that how you first noticed something was amiss?
Arc 131.0.6778.205 (Official Build) (arm64) Revision 81b36b9535e3e3b610a52df3da48cd81362ec860-refs/branch-heads/6778_155@{#8} JavaScript V8 13.1.201.19 User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36