Nope, but I did 
Use WebTools Tech Module, that’ll tell you a token
1 Like
publicAddress=“x.x.x.6”
Which is my IP
And port number is also correct?
Think so: port=“32400”
Hmmm…And currently, it’s down!
https://X.X.X.6:32400/identity
So above indicates a bad router…
Are you using uPnP, or a static map on your router, and the latest is STRONGLY recommended
Would it help if I just delete the token and copy paste the rest of the XML here? it’s also showing other stuff like:
<Connection protocol=“https” address=“10.0.5.1” port=“32400”
Which I have no idea where it’s taking the info from at all.
As for your question, actually this is behind a corporate firewall. All I know is that it is a mot “ASA 5506-X” 
If I need changes done to it then I will need to request those from the company that maintains it for me. Which I can do tomorrow. However, not sure what I need to ask them for
Isn’t it strange that this problem doesn’t persist on 1.17 though?
Just to be sure, delete your tokens, and then DM me the XML
Indeed, and clueless as to why as well
It looks at all the local IP addresses bound to your server
See: https://support.plex.tv/articles/200931138-troubleshooting-remote-access/#toc-1
Sent you the xml (I think) in a private message.
I can have the IT company look into the router tomorrow, but I actually already went through that with them the first time I updated to 1.18 a few months back. They actually made a valid point at that time, that when I am going through to the local IP 192.168.1.100 it goes past the firewall, but that the problem still persists. So it shouldn’t be a firewall issue. And again, then it should be doing the same on 1.17 too right?
Correct, but since I now can’t access it directly using IP and port, it’s 4 sure a firewall issue!
Also tell them to add a DNS Rebinding for the domain named plex.direct if possible
I will ask them to do that. But might the problems reaching the IP of the NAS be because of the CPU load?
If you can reach it from the inside, then outside should work as well
And by reaching it you mean just being able to access 192.168.1.100:32400/web right?
I disabled Plex just to try things out, and here is another peculiar thing. Even though the app is disabled it is still running in the background, taking upp full CPU load. That is why I have been rebooting the server prior to sending you logs before. Can this be something causing my issues?
Correct
Is DNLA enabled?
If so, and if not using that, disable it and reboot the QNAP
Since I disabled, then enabled Plex again, I can’t reach the local IP, it just says “waiting for 192.168…”
But I am not using DLNA, don’t even know what it does really. However, this is disabled in the Plex settings right? If so then I have disabled it there. Unless it needs to be disabled on the NAS too? Haven’t found any settings for that there.
Correct
Nope
Hmm…Wait 5 min, and if still not there, then try and disable/enable PMS again from the AppCenter
And regarding DLNA: It’s an additional mediaserver, that broadcast to the local network, making it possible for everybody to access medias, without authentication!
Disabling and Starting the app helped. Even removed the CPU load issue, but that usually starts happening a bit later after I start it up.
I am trying to find the DLNA setting, but correct me if I am wrong, I need to be able to access the server settings for that right? I believe last time I checked this was after the last downgrade to 1.17.
Correct, or manually access the file system and edit a conf file, which I don’t recommend
Server Settings/DLNA is where it’s located
I wont edit it, but I could view it just to check? If you can tell me where it is located? Or should I skip this?
Most likely located here, but can depend on the disk setup on the QNAP though
/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Preferences.xml
DlnaEnabled=“0”
