It seems different people are having different problems with the latest 1.15.1.791 update. Those running Linux seemt to have issues where even devices within their own home network cannot connect, whereas Windows 10 users seem to have lost Remote Access.
Has anyone with Windows 10 and Remote Access issues where you can no longer keep Remote Access in the green for more than a couple of seconds had any success in rolling back to the previous version of 1.14.1.5488 and have had your Remote Access issues working properly again?
for unbuntu 16.04 plex looks like its running in status, but the web ui wont connect. rolling back to the previous version didnât fix the issue either.
Running that script now. The portion of the logs that you singled out are from March 18, pre-update. The update was installed 3/20 just about midnight, not sure if that helps or is unrelated.
Running command in step 3 now.
edit: backing up the entire Plex DB is going to take some time. I may have to continue this tomorrow if it does not finish within 30 minutes.
Same here. My usual DB backups take hours to complete so I imagine I wonât have an updated log until morning. I did reinstall plexmediaserver_1.14.1.5488-cc260c476_amd64.deb before getting you those logs to answer your previous question.
The package I have downloaded and used to previously update was this: plexmediaserver_1.15.1.791-8bec0f76c_amd64.deb
Will this suffice?
I also donât know what you mean by turning off Advertisement. Then lastly, I (stupidly) disabled debug logging shortly before midnight but I believe that setting was exclusive to the web app. In case Iâm mistaken, is there a way to turn that back on via terminal?
Please advise. The hour is late and we can pick this up tomorrow if you wish.
If you have a customized start (/etc/systemd/system/plexmediaserver.service), youâre probably overriding the LD_LIBRARY_PATH. 1.14.1 -> 1.15.0 changed LD_LIBRARY_PATH
We need to handle customizations per systemd spec.
I installed the package that I had installed before this all started. 1.15.1.791.
Where can I find 1.15.2.793?
Also, my previous post says that I stupidly disabled debug logging thinking âoh, Plex never has problemsâ and Iâm unsure if that was for the server or for the web client.
The file in /etc/systemd/system/plexmediaserver.service is the old ubuntu location. They had it wrong for a long time. Going to 1.15.0 exposed a bunch of folks caught by it.
If you customized any of it, You will need to transfer your customizations per:
Reason for this is:
Master copy is in /lib/systemd/system/plexmediaserver.service
Your customizations (overrides) go in /etc/systemd/system/plexmediaserver.service.d/override.conf
I donât recall customizing any of this. Iâll have to take a look at your article tomorrow.
cat /proc/1/comm
does return systemd. If I did customize anything I donât remember doing so. I did notice that my user is the owner of most files, not sure if that means anything.
I had that issue too but I think I found a fix for it. In the upper right hand corner where you have your account logged on that shows that two instances of things playing, the drop-down menu will let you change accounts or to sign out. I found that if you sign out and then sign back in that problem seems to correct itself. Give it a try.
Hey, for those of you having issues with the new update, I know this may sound stupid, but I âthinkâ it just solved some issues for me. When you have PMS running, click in your account initial in the upper right hand corner to get the pull down menu where you can see your Account, Users and all that including changing users and at the very bottom is SIGN OUT. Try signing out of the PMS and then sign back in. It may not help, but it got rid of several issues for me including having two instances of videos running and the No Soup For You Message and I think it MIGHT have also fixed my Remote Access issue. So just try SIGNING OUT and then sign back in. The worst that can happen is it wonât do anythingâŠgood luck.