I have concerns with the plan to drop IE 11 as a supported browser.
First, IE11 is the only built-in browser in Windows Server 2016 (and earlier releases). I have not validated if this is still the case for Windows Server 2019. As an industry security best practice, you want to minimize adding any additional software. Thus, installing a 3rd party browser is not desired.
Second, IE is supposed to be superseded by Edge on Windows 10, but this is broken as can be found in many posts on this forum. For me, Edge on Windows 10 versions 1803 and 1809 both exhibit the same issue that the hosted app cannot access the local servers. Again, I shouldn’t need to install yet another browser to access my Plex servers when I have two built-in browsers that should be able to work. Either the Plex Web App needs to be fixed to work around the Edge issue, or IE support needs to be maintained by Plex.
Even though Microsoft has announced it’s intention to migrate to the Chromium engine for Edge, that doesn’t mean that this issue will be fixed, nor is there a timeline as to when this will happen. The issue persists today with production releases and Plex should be trying to resolve the issue.
For completists, the issue I continue to experience with Edge includes allowing for insecure connections, and direct access to the local web app works; it’s just when the hosted app tries to connect that the issue occurs. If this issue is due to Edge baulking at the DNS rebinding, then perhaps Plex can add a workaround to use the internal IP address directly.
