Server Version#: 1.29.0.6244
Player Version#:1.55.0.3278-c6164b3c
How to update PMS with the new password set on Synology? There is no “PlexMedia” or “Plex” user group on the permission of this media folder, it never has one. PMS running off a different server (Windows Server) and access the library on NAS. Reverting the password back to old value fix the access issue.
Also since updating Plex to the latest version, often times its showing "Response code=“503” title=“Maintenance” status=“PMS is currently running startup maintenance tasks.” when starting up the server. It takes roughly 2-5 minutes before I can access it.
As the message says, Plex is performing maintenance tasks and is unavailable. For example, the PMS database schema frequently changes between versions. When this happens, Plex updates the db to the new schema and displays the 503 message as the system is unavailable when that is happening.
Wait for the message to clear. Do not interrupt the process. If you do, it will start over when Plex Media Server is restarted. Also, you risk corrupting the database.
The message is new, but the update process has not changed. Some users were interrupting the process and corrupting the database. Plex added the message to let users know what was happening and to wait until it is finished.
You should have a user account on the Synology with read-only or read-write permissions to the media folders. This can be any user account.
Use that account when adding the SMB shares to the Windows Server system where PMS is running.
If you change the password on the Synology user account you will need to change the password on the Windows Server system as well.
Thanks! I thought it was because the windows server is performing maintenance at that time. I unknowingly did a restart on the server and I guess it does pick up from where it left after the restart. Not sure if the database corrupted though but everything works normally after.
Too focused on Plex and I didn’t even think about its actually windows SMB issue. Updating password on the Windows SMB share folder solved the issue!
