My web interface has been updated to 2.6.
Also my server is 0.9.16.4
But on another network I have a server on 0.9.16.4 and on on 0.9.15.6
No matter what I do none of my apps including the web interface can connect properly secure on the local lan and also not remote. SO I can no longer access the two servers on the other network and nor my local network can access secure. If I open the web interface on one of the remote servers using another account it does have access to those servers. But it seems my account does not.
It almost seems like my account is broken or something
What i tried, one server got updated, rebooted, log out, log in with server account, disconnected remote access, reconnected remote access. The remote access check checks green. Using an unsecure connection I can connect to one of them.
ok, the plot thickens.
I noticed my shared servers (3 in total from 2 different sources) all are missing in my server list. This problem is present in all my apps and web interface. But if I set force secure to never they do show up. I just remote connected to one of the external servers opend the browser there and connected to with my account, and look there is everything, secured and all, including my home server.
So from some networks it is working but not from my home network it seems nor from my mobile Phone.
Oh and my apps only see my own server, they seem to have lost that other servers have been shared with me. Even if I have the on Always fallback
Except my Xbox One app, that one does see the other server but only unsecure
From the windows Phone app I see these type of messages:
Get {plex host address for I think servername A}
Setting inactive {servername A} connection {interal ip of lan, also for remote servers} from unavailable to unauthorised
PlexException from {plex host address same as get above} connection to host {plex host adres} failed
And this goes on for all my shared servers.
My own server acts slightly different in the log
It does this thing twice, one more with a more internal address scheme.
But it seems clear that my user is no longer being able to get the host info from the https source on the plex server and because of that the system is failing.
Please please please someone help me with this. My kids actually use part of this content for school.
ok the host names I got from the logs are not being resolved on my home network while they are being resolved on the remote machine where it is working for,
So it starts to smell like my provider is blocking some dns traffic or something.
Anyone any idea how to check this?
yes, clearly its a DNS thing. On my network the nslookup to plex.direct replies non existing domain while on the network where everything is working it replies 82.94.168.7
So for that network it is existing, lets see if I can force my local routers dns to add this entry and see if that solves everything
ok, so it seems my nslookup now does respond the plex info again. But still no luck.
So it all seems to fail on the fact that the plex client is trying to connect to a domain like {my server public ip with - instead of .}.{server token}.plex.direct but failing.
Now I can not get these domains to resolve on any network, also not on the once that seem to work. So I still wonder how this part is supposed to work.
Can anyone confirm that these domains are even part of the DNS server or is it a fake name that is only used to create the SSL certificate and than resolved by logic in the code of Plex?
I really need someone to help me out here. I am a bit dissapointed that no one is chipping in to help me figure this out. It still seems to be provider related since I can access my home server from other networks securely, even though I can not access any remote server securily not even my home server while I am on the lan
