Server Version#:1.32.5.7349-8f4248874
Player Version#: 1.77.3.3966-a5ddb215
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Hello
I have recently the following problem
I can no longer access my Plex server although the port is set to listen and nothing else really happened.
but I always get the message No secure connection possible neither via the Mac app nor via plex.tv nor via the server IP itself I get access to the plex interface
i need help to fix this.
unfortunately i could not find any errors in the log files.
So I have checked everything again I have enabled port 32400 in the firewall as well as both IP addresses of plex according to HAT article enable in firewall as well as fail2ban I don’t understand why this is spinning lately until the last update this was no problem.
I run plex on a dedicated storage server in the datacenter without nat or anything like that
unfortunately the remote access is still spinning it sometimes works for a while but then it doesn’t work anymore.
For Remote Access, the only port you’re concerned about is host port 32400/TCP
Port forwarding from the router redirects the wan port (whatever it may be) to SERVER_IP:32400
Starting Nmap 7.94 ( https://nmap.org ) at 2023-09-27 03:19 Central European Summer Time
Nmap scan report for storage1.nl.euroservers.com (94.75.211.138)
Host is up (0.22s latency).
PORT STATE SERVICE
32400/tcp open plex
Nmap done: 1 IP address (1 host up) scanned in 0.31 seconds
port 32400 is open but even though the port is open no direct connection is possible through plex but only through the relay and plex often shows no connection.
the funny thing is that I can access directly through the browser.
plex is running on a Debian10 server with plex panel in the data center in Amsterdam without extra nat or anything else there is the port 32400 free I have no other. traffic blocked
I’m not sure why I need to forward port 32749 to 32400 it worked until 2 months or so ago without.
I have that, that’s the strange thing. I don’t understand where it comes from. I have plex on a dedicated Debian 10 server without a block or something similar. In my opinion, the error happened in one of the last updates. Can I somehow roll back plex?
Currently, despite manual port 32400, no block public IP without nat, no access is possible, not even via relay service
So I had just installed an available update and then had to manually define remote access and port 32400 again and now it is online, see screenshot. I will keep an eye on it over the next few days
I have unfortunately after an update from you that I downloaded about 1 hour ago again the same problem plex has problems with the remote connection partially see screen shot.
Furthermore, the server was completely unusable error message plex Failed to load preferences.xml although I have not changed anything there.
I have completely removed plex according to your instructions and it is accessible again, but the A problem with a core component of the Plex Media Server was discovered.
I would like to know how I can get the Plex media server running perfectly again without any problems
