Having a real battle getting Plex working again

Plex Media Server NAS & Devices
1

Hi,

I’m having a real battle with Plex. I have used Plex before on this NAS however I cannot get it working this time. I have installed 1.25.0.5282. When I try to add a library it’s not happy. If I select Movies as the type them browse to the folder and click on the ‘Add Folder’ button Plex says ‘Your changes could not be saved.’. If I change the scanner from ‘Plex Movie’ then it will add the library but won’t scan it. Just tells me to uprade it. If I try that then it says ’ There was a problem upgrading the library.’

So, I have a media server installed but it won’t pick up any media!!

I have looked in ‘Agents’ and ‘Plex Movie’ isn’t even listed.

I’ve tried to remove Plex and re-install but the same thin happens. I am kind of lost really.

Hoping that someone might have an idea.

Thanks

Simon

2

Simon,

If it can’t save changes, 99% of the time it is because there is no connectivity to Plex.tv.

  1. Network settings ?
  2. Server not associated with the account ?

Can you manually get the logs please ?

3

Hi, I have had all sorts of network access issues but thought that it was all ok. Initially I couldn’t claim the server but i’ve managed to do that now.

Log.txt (2.1 KB)

This is all the log file shows sadly.

Incidentally i’ve tried to setup the PlexData share with the link but can’t see what im supposed to do so pulled the log via SSH

4

Simon,

PMS restarted before it stopped.

Dec 05, 2021 16:39:04.041 [0x7fb13e4726e8] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.
Dec 05, 2021 16:39:04.041 [0x7fb13e4726e8] ERROR - HttpServer: Error binding acceptor: Address in use
Dec 05, 2021 16:39:04.041 [0x7fb13e4726e8] ERROR - HttpServer: Error opening acceptor on IPv6, falling back to IPv4: Address in use
Dec 05, 2021 16:39:04.042 [0x7fb13e4726e8] ERROR - HttpServer: Error binding acceptor: Address in use
Dec 05, 2021 16:39:04.042 [0x7fb13e4726e8] ERROR - Error: Unable to set up server: listen: Address in use (N5boost10wrapexceptINS_6system12system_errorEEE)

I found a problem with that. I just finished (last night) changes for QNAP which will fix it.

I can give you updated plex.sh script to use (if you’re ok putting that in place manually) -or- I can get a new package build.

For you , ( I am sorry ), Restart QTS :frowning:

PMS will restart properly

5

Hi,

If you’re able to tell me what I should do with the plex.sh then I am happy to have a go putting in place. Otherwise I guess a new package is the way to go.

I have been struggling with this all day so am pleased to be talking to someone who can help!

Thank you so much!!!

6

Give me a moment please to confirm what I WANT to do will work for you too :smiling_imp:

7

Here we go –

This is a temporary patch until I can get updated QPKG packages released.

  1. Take this file and place it in the Public share
    plex-sh.zip (2.9 KB)

  2. Unzip it. You’ll have plex.sh

  3. SSH into the QNAP. You need to be admin. You can’t be a ‘normal user’.

  4. cd /share/Public

  5. chmod +x plex.sh

  6. ./plex.sh stop – You’ll see it stop Plex

  7. Now, confirm it starts Plex for you – ./plex.sh start

  8. Confirm Plex is running normally :crossed_fingers:

  9. If that’s confirmed, we will replace the one from the package with the updated one.

  10. cp plex.sh /share/*/.qpkg/PlexMediaServer

  11. Now start and stop via the GUI. Normal operation should be restored.

8

Not sure that this is what you were hoping for sadly:

login as: admin
admin@x.x.x.x’s password:
[~] # cd /share/Public
[/share/Public] # chmod +x plex.sh
[/share/Public] # ./plex.sh stop
Plex Media Server hasn’t been enabled or started…
[/share/Public] # ./plex.sh start
Starting Plex Media Server…
[/share/Public] # Error: Unable to set up server: listen: Address in use (N5boos t10wrapexceptINS_6system12system_errorEEE)
[/share/Public] #

9

Simon,

Thank you for that.

Something else is happening to you.

Would you be willing to have a teamviewer session (we will arrange in PM) so I can determine what’s happening ?

10

Sure, happy to, thank you!!

11

Folks,

We solved it.

Simon is using a prototype script (pending release in the formal package after final QA approval).

We’ll see if it continues to work .

Anyone with similar problem is welcome to try this. (i don’t like faulty scripting so want this solved)

12

I’m having a similar error. I’m wondering if your script will help me out as well? I was having problems with previous version, just installed 1.25.5.5492 and see the following:

Feb 03, 2022 04:35:16.882 [0x7fd22094fd48] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.
Feb 03, 2022 04:35:16.882 [0x7fd22094fd48] ERROR - HttpServer: Error binding acceptor: Address in use
Feb 03, 2022 04:35:16.882 [0x7fd22094fd48] ERROR - HttpServer: Error opening acceptor on IPv6, falling back to IPv4: Address in use
Feb 03, 2022 04:35:16.882 [0x7fd22094fd48] ERROR - HttpServer: Error binding acceptor: Address in use
Feb 03, 2022 04:35:16.882 [0x7fd22094fd48] ERROR - Error: Unable to set up server: listen: Address in use (N5boost10wrapexceptINS_6system12system_errorEEE)

thoughts?

13

@HenryDB

Yes, My updated plex.sh will resolve that.

I apologize for it not having been included in this latest release.
There were some QA delays in approving it and getting it back to Engineering.

15

is it the same script from back in December? or is there an updated one?

16

@HenryDB

It’s the same one as above. There are no changes.

The QNAP scripting is very stable for the most part. This change is rare

17

Looking at my qnap, I see the Plex Media Server running, but not much is happening there. When I run ./plex.sh stop I get a message that Plex Media Server hasn’t been enabled or started…

Should I go further?

Macky.

18

@HenryDB

with the plex.sh file installed in /share/*/.qpkg/PlexMediaServer/plex.sh (owner is admin:admin),

Use App Center to manage it the first 2 cycles. The script gets control of things again by knowing it’s invoked from App Center.

19

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.