@jrhdzj said:
I was having the same issue. Windows App works but the beta app was an indirect connection. I found this to be similar https://forums.plex.tv/discussion/178406/windows-10-app-issue for me. I resolved the issue with http://loopback.codeplex.com/
It worked! Thanks man
Looks like this is default for windows universal apps?
For security reasons, a UWP app that is installed in the standard manner is not allowed to make network calls to the device it is installed on.
Deploying and debugging Universal Windows Platform (UWP) apps - UWP applications | Microsoft Learn
I found the same info while googling for a solution. The weird thing is that I had installed the normal Plex app from Windows store and never had this issue, only happens while using beta.
Also having the indirect connection problem. I downloaded the loopback white list app and Plex was already marked as having it.
Any progress on this? Or is it “unfixable” because of the UWP limitations?
@vladtapas said:
Any progress on this? Or is it “unfixable” because of the UWP limitations?
Have you tested the solutions provided on this thread? It worked for me!
@COBRAws said:
@vladtapas said:
Any progress on this? Or is it “unfixable” because of the UWP limitations?Have you tested the solutions provided on this thread? It worked for me!
Yes, the loopback stuff works, but I don’t want to have to do workarounds to get stuff like this to work. I was hoping there would be a fix for this from Plex.
Plex can’t fix this, it’s a UWP limitation, so the loopback exemption is the only way to resolve this. It’s been like this since Windows 8
@vladtapas said:
@COBRAws said:
@vladtapas said:
Any progress on this? Or is it “unfixable” because of the UWP limitations?Have you tested the solutions provided on this thread? It worked for me!
Yes, the loopback stuff works, but I don’t want to have to do workarounds to get stuff like this to work. I was hoping there would be a fix for this from Plex.
Only Plex beta for Windows 10 has this issue, the normal windows 10 Plex app works without any loopback fix.
@COBRAws said:
@vladtapas said:
@COBRAws said:
@vladtapas said:
Any progress on this? Or is it “unfixable” because of the UWP limitations?Have you tested the solutions provided on this thread? It worked for me!
Yes, the loopback stuff works, but I don’t want to have to do workarounds to get stuff like this to work. I was hoping there would be a fix for this from Plex.
Only Plex beta for Windows 10 has this issue, the normal windows 10 Plex app works without any loopback fix.
Yeah, that’s why I was thinking there was something Plex could do about it.
The solution for me is to keep using home theater and alternately switching to plex media player when I get around to getting myself a Plex Pass sub.
@COBRAws said:
Only Plex beta for Windows 10 has this issue, the normal windows 10 Plex app works without any loopback fix.
Are you saying that the Plex for Windows 8 app works correctly even when it is unchecked in the loopback exemption app?
@pombeirp said:
@COBRAws said:
Only Plex beta for Windows 10 has this issue, the normal windows 10 Plex app works without any loopback fix.Are you saying that the Plex for Windows 8 app works correctly even when it is unchecked in the loopback exemption app?
Nope, I was talking about Windows 10. I never used windows 8 so I can’t confirm.
What I meant was the Plex for Windows 8.1 app (the non-beta), compared to the beta (native Windows 10) app.
The Plex for Windows 8 (8.1 non-beta) app works for me perfectly without any problems. No loopback fix needed.
The Plex for Windows 10 beta app starts up slowly (~30 sec) and shows “Direct connection unavailable”.
If I activate “Remote Access” in the Plex server, the Plex for Windows 10 beta app starts up a little bit faster but shows the orange “!” on the Plex logo in the left bar.
When i press on it to show up the Server list it switch instant to the green lock for secure connection. After that the app works good, just a little bit slowlier than the Windows 8 app, don’t know if that depends to the connection or the beta app.
Server and apps on same computer.
@pombeirp said:
@COBRAws said:
Only Plex beta for Windows 10 has this issue, the normal windows 10 Plex app works without any loopback fix.Are you saying that the Plex for Windows 8 app works correctly even when it is unchecked in the loopback exemption app?
I had never used the loopback exemption app before now, but when I started it, Plex for WIndows 8 app was already checkmarked.
@pombeirp said:
What I meant was the Plex for Windows 8.1 app (the non-beta), compared to the beta (native Windows 10) app.
Yes, loopback exemption had to be installed/configured for the first time after downloading the native windows 10 app. Windows 8 app never required me to do that. Feel free to ask anything, since were are here to help with the beta!
OK, the mystery is solved: when the server is installed, it creates the loopback exemption rule automatically on behalf of the Plex for Windows app. Since it doesn’t do that for the beta app (which during beta has its own identity), that explains the difference in behavior. When the app is out of beta, it will assume the old one’s identity, and so this will be a non-issue.
@pombeirp said:
OK, the mystery is solved: when the server is installed, it creates the loopback exemption rule automatically on behalf of the Plex for Windows app. Since it doesn’t do that for the beta app (which during beta has its own identity), that explains the difference in behavior. When the app is out of beta, it will assume the old one’s identity, and so this will be a non-issue.
Great news! Thanks for checking 
