No remote access on 1.18

Plex Media Server Remote Access
1

Server Version#: 4.4.1.1146 (TS-453A) / PlexMediaServer-1.18.4.2171
Player Version#:

So I made a post a few months back, but it was closed automatically.
I had the same issue back then, but when I downgraded to 4.3.6 + 1.17 my issue went away.

Because Plex will require at least 1.18 going forward in order for artwork to properly work, I am forced to re-visit my issue, and try to resolve it.

I was able to upgrade to 4.4.1.1146 and while on 1.17 everything works as intended. But every time I upgrade to 1.18, remote access stops working.

Now here is where it’s strange: I am still able to play my media, using PlexKodiConnect, but every official app/web app won’t access the server. If I downgrade to 1.17 it works again.

Accessing the web app via local LAN (http://192.168.1.100:32400/web) doesn’t work either while on 1.18.

Some support would be appreciated.

@dane22 was helping me prior, and I have the plex library share app installed still. However, the folder is huge now, so I wonder if I can clear it and run it again?

My previous topic is this one:

2

I do not have any answers, just recommending you also include your non verbose log files, it may help

3

Don’t I need the remote access for those?

4

Found this within the forums…

5

That’s a person running Plex on a windows server it would seem?

6

plex_99
plex_991115Ă—448 47.7 KB

Also, Plex is running the CPU to 99% - even though nothing is playing.
And again, 1.17 doesn’t display the same issues.

Logs.7z (4.9 MB)
EDIT: think I managed to add the correct logs now :slight_smile:

7

You are picking up 4 months of changes with a big one concerning music. Depending on how many files you have that little processor is going to be busy for a while. Monitor the Plex Media Server.log and be sure that no SQLITE error messages are there or corruption.

8

I have zero music files. Would this still affect me?

9

There was also the transcoder update that caused the files to be re-analyzed.

10

That would perhaps explain the CPU load, but what about the fact that I can’t access the server remotely?

11

Symptom of the High CPU load. Don’t have 7zip on the machine so I can’t look at your logs but you should be able to search for errors.

12

I can re-submit it as zip if that helps?

13

That would help.

14

Logs.zip (7.1 MB)

Here you go, slightly larger file.

15

If you decide to kill it and go back to 1.17, repair and optimize your database before you try to upgrade.

16

Are you referring to this procedure?

17

Yes. With it being a NAS I suppose you could try to Optimize first and see if it will upgrade before going through the effort of copying the file off to a pc and doing the repair.

18

I must say this is where it starts being a bit over my level of expertise. Does the optimization require me to SSH or is there some built in app or function I can use?

19

If the server is responding.

https://app.plex.tv/desktop

Server Settings> Troubleshooting

There is also
Download Logs & Download database.

Did you upgrade your QNAP version to 4.4.1 before/after QNAP re-released it?

I don’t know if this is your problem but some others have had their databases grow with large amounts of statistics.

20

Firstly, thanks for taking your time trying to help me :slight_smile:

As for your questions, yes I upgraded to 4.4.1 as soon as the first public release came, then downgraded to 4.3.6 and now upgraded to 4.4.1 again. I have always updated to the latest version of Plex as well as soon as it came out, though not quite sure if I updated QNAP or Plex first that time.

Sadly the server is not responding. I could downgrade to 1.17 to do the optimization, but is this equivalent to the Linux SSH repair?