@chop-shop said:
@sa2000 said:
@chop-shop said:
it is getting better and better : http://127.0.0.1:32400/web/index.html get me to:
This site can’t be reached
127.0.0.1 refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
I am sorry to hear that you have other issues - we can resolve such problems from log files. It could be for example that you have multiple plex accounts and the server is signed in to a different acccount and you did not realize that
If the server is signed in to plex.tv then all accrss - even through 127.0.0.1 must authenticate
Yeah well, I thought so too… Anyway, now, http://127.0.0.1:32400/web/index.html# gets me to the server on the Mac Pro but not one single device (AppleTV, Roku, iThis, iThat or Stupid TV (Smart seems a bit overrated to me)) on the network detects the server…? It says: “Direct connection unavailable (chop-shop)” and it keeps trying to no avail…
I don’t understand what is going on, it was all working fine until God knows what happened and why?
You’ll find the logs attached to this message.
One more thing, before this happened, I had to get rid of my Plex music library because Plex would only scan the music library, not the movies or the tv shows even after adding movies and asking it to scan Movies A-L for instance, it would scan it for like 2 seconds, not changing a thing and immediately go back to scanning the music library… I have a huge music library that I don’t listen to so much anymore because I have both Apple Music and Spotify that allows me to listen to anything from any device so I don’t miss it but so you know…
Thanks for your help, I appreciate 
Thanks for the logs
Can’t see any requests from within the local network to the server. It could be DNS Rebinding Protection blocking local access and because server is not available for remote access, there is no alternative secure connection route to the server.
To establish if there is DNS Rebinding protection on the local network, try this in a terminal session on the Mac Pro
nslookup 192-168-1-100.20cc502aaa1745689fac5741b969c713.plex.direct
nslookup 192-168-1-101.20cc502aaa1745689fac5741b969c713.plex.direct
These should translate to 192.168.1.100 and 192.168.1.101 respectively
If they give an error, try with Google DNS
nslookup 192-168-1-100.20cc502aaa1745689fac5741b969c713.plex.direct 8.8.8.8
nslookup 192-168-1-101.20cc502aaa1745689fac5741b969c713.plex.direct 8.8.8.8
The logs show that may be you are going through a vpn and have a double NAT
Extracts from the log (I have masked parts of your WAN IP addresses)
May 31, 2018 13:00:24.717 [0x700000631000] DEBUG - PublicAddressManager: Got public IP from http://plex.tv: 14.207.xxx.xxx
May 31, 2018 13:00:27.728 [0x700000631000] DEBUG - NAT: UPnP, public address is 183.89.xxx.xxx
May 31, 2018 13:00:27.728 [0x700000631000] DEBUG - PublicAddressManager: got WAN IP 183.89.xxx.xxx from router
May 31, 2018 13:00:27.728 [0x700000631000] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
May 31, 2018 13:00:30.112 [0x700000acc000] ERROR - MyPlex: mapping failed due to potential double NAT configuration
This would impact availability of remote access route to the server and if there is DNS Rebinding Protection blocking local IP access plex.direct urls, remote access route would avoid the issue. Some plex apps do have means of getting round that, though.
You could try signing the roku out and in within the app settings and if problem persists get log from the roku as well server log to see why it is not getting through
See https://support.plex.tv/articles/201377603-roku-logs/
There is a general support article about apps not finding the server
https://support.plex.tv/articles/204604227-why-can-t-the-plex-app-find-or-connect-to-my-plex-media-server/