I would very much like to see one.
You deleting them is fine but doesn’t address the issue of them causing the failure in the first place.
Does some specific text need to be inside of the nfo? Can I just make a blank placeholder file or put some random text in it?
@ChuckPa want’s one of your original nfo files, as it is.
If you already deleted them, then that’s too bad
@ChuckPa did you get a chance to review the logs I attached? I’ve just been stopping and starting the Plex app each day to prevent the memory from getting everything hung up again.
Not trying to be pushy, just want to make sure I didn’t miss your response among all the posts.
@ChuckPa I can’t get my PMS to work either. I was using the older version of PMS 1.23 that wasn’t working. I did the incognito window thing which worked, but wouldn’t connect to my NAS after taking ownership. I then updated PMS to 1.25, and now I’m back to square one where it doesn’t work with the incog window either.
The PMS log says:
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] ERROR - [CERT] PKCS12_parse failed: error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] ERROR - [CERT] Found a certificate, but couldn’t install it.
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] DEBUG - MyPlex: mapping state set to ‘Unknown’.
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] DEBUG - Relay: read 0 cached entries from hosts file
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] ERROR - HttpServer: Error binding acceptor: Address in use
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] ERROR - HttpServer: Error opening acceptor on IPv6, falling back to IPv4: Address in use
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] ERROR - HttpServer: Error binding acceptor: Address in use
Dec 26, 2021 10:10:13.538 [0x7fc50fe56d48] ERROR - Error: Unable to set up server: listen: Address in use (N5boost10wrapexceptINS_6system12system_errorEEE)
I don’t know how to PM you on this forum. I clicked the messages thing, clicked on your name, but it doesn’t have an envelope or anything to PM.
I have the logs in tar’d and zip’d format.
Did you add your own certificate to Plex?
As for the remaining snipped about the “Address in use”.
I have a ‘hot fix’ I can give you here in the forum which will remedy that if you’re interested.
The only limitation is that it will be overwritten if you change PMS versions (the new install will overwrite what I give you).
I’m getting the same issue now with a restart. It all started when I could not access my Plex server the browser was saying the page was insecure and yet it showed https. All my apps, including my phone was saying the server was offline. On advice from the help pages, I shut down the Plex Server and restarted but it does not finish. It just hangs…starting… and never finishes. I am trying to re-install to see if that fixes it.
Reinstall just hangs as well. I read someone was successful by starting his Nas 8 times. I try something like that before trashing the server and starting over.
Restart once, everything showed active but upon clicking the Plex app to log in I get “connection not secure” but it shows https? Any thoughts?
firefox says: The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Did my SSL from Qnap fail? This just happened, is it some new code written in Plex?
Well, I was able to access the server and claim it by removing the s, and just do http. It now show up in almost all my devices. Laptop, roku, iphone, so far and accessed as https.
So I ended up buying a TS-453D and Plex is still crashing either daily or every other day. 
Logs attached.
Turned “send errors to Plex” off after the first crash, but the crash that just happened didn’t generate an error log.
Logs.zip (7.2 MB)
Shoot, I deleted all the NFOs after the first message, ha. I think my NAS also purged the recycle bin since then but i’ll check when i get home and if possible do a test. However, it has not crashed since I purged the NFOs, so that’s something.
Hi, the same problem here since i update my Plex Server to 1.25.2
Can you help please
Logs.zip (5.1 KB)
Please clarify (in light of bug fix from two days ago),
- Is EAC-3 audio being played?
- Does the playback crash or does PMS itself crash?
- No
- The PMS itself crashes
Please look at your Databases folder.
Specifically look to see if you have any backup copies of com.plexapp.plugins.library.db.
The one you have is very damaged.
I’m still getting the following error when I type the nas ip address in the address bar or try to open Plex within the QNAP app canter:
http://192.168.0.43:32400/web
Not Found
The requested URL was not found on this server.
I have uninstalled Plex rebooted the NAS and reinstalled Plex.
It still gives the same error. I’m using the newest version of Plex and the current version of QTS on my server. My server is configured with 3 NIC GbE ports in Bond0 (192.168.0.44) and and the 4th GbE port as the primary IP address of the NAS (192.168.0.43). Both are Static IP addresses.
What do I do next?.
If opened from QTS, are you sure above is not the URL it tries, but intead https://192.168.0.43:32400/web
Note https from QTS, and not http
If so, then note, that if a PMS is not claimed, then it’ll not listen on a secure connection, only on plain http
That didn’t work. Any other ideas?
I didn’t claim the server after reinstalling Plex, unless it was done automatically(?).
Are they connected to an intelligent switch that supports LACP?
Ref: Qnap faq.....read me first! Q21
And if not, disconnect all but one interface, and then reboot your QNAP
I’m using 52 port managed switch. I have the port trunking enabled through the qnap and configured the link aggregation through the switch. I’ll unplug the three cables that are used in port trunking configuration next week when I get home.
