Thanks… Checking through that now.
All devices have been logged out locally and restarted to pull new credentials?
They have
Please stop plex.
Grab the log files manually, make a zip, and share them.
(The PlexData shared folder, if you have created it, will let you get the logs via FileStation)
Unfortunately I did not create the PlexData folder in the past, and without access to the web interface I know of no other way to access log files
- Create the shared folder
PlexData(exact caps) in the GUI - In App Center, Attempt to start PMS once. Stop it if is does start.
- Now you have the FileStation access via the back door to your logs
What files should be shared?
Crash Reports, Logs, etc.
All the Plex Media Server logs (including the 1,2,3,4,5) files
I did a full format and rebuild, the server worked for about 24 hours and now I am getting the same error all over again.
Full Format? You erased the entire QNAP?
Can I see the server logs please ?
If you have no access, we can use the PlexData shared folder and get them from filestation.
There are no logs as I did a full format of the entire server.
The 503 issue is no longer happening, but I am running into severe stability issues and any new media being added is receiving “file not found” errors in Plex.
Do you know of any location on Plex.TV that archives the previous server versions? My feeling is the latest version 1.28.2.6106-44a5bbd28 is causing my problems.
1.28.2 is being successfully used by many folks.
I can provide you with a QPKG from a limited set of older binaries.
Which NAS & PMS version? 1.28.0 ?
In the future, Nuking the entire NAS is not necessary.
Uninstalling Plex from App Center nukes ALL of Plex.
Unfortunately I attempted to uninstall Plex and reinstall it a few times and it did not solve the issue. The only resolution was to format the server (nothing but media is on that server so it was able to be done with no issues)
Qnap Intel/AMD 64 bit and the previous version to the latest one. I do not know the version control but either 1.28.1 or 1.28 would work.
Check your DM (Upper right corner)
I am beginning to suspect your machine is infected and will need a full factor reset.
This does include reloading fresh firmware
TO ALL HERE
I checked with one of the Engineering folks.
HTTP code 503 is NOT AN ERROR when PMS is starting or doing scheduled tasks.
The code is new.
HTTP 503 means “Not Available”.
During maintenance, when the DB is being upgraded, it’s temporily Not Available.
It should be in as a WARN.
I wish there had been more info about it.
This is totally OK.
It caught me by surprise too
1 Like
Thanks!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
