Plex on Qnap not loading

Plex Media Server NAS & Devices
1

Server Version#: PlexMediaServer-1.24.2.4973-2b1b51db9-x86_64
Player Version#:

So I uninstalled the Qnap Plex app, reinstalled it, upgraded to the latest version and now it will not load in my browse with the url I’ve been using for years: http://10.0.10.4:32400/web/index.html#!/ It just never loads
I’ve been running Plex on this server for the past 4 years or so.

If I browse to https://app.plex.tv/desktop/#!/ Plex loads but does not seem to connect to the local version on my Qnap. Left col shows YOUR MEDIA and when I click that the main screen shows “Add your media to Plex” with a button to download the server installation file.
I’ve rebooted and cannot figure out what is wrong. @ChuckPa can you please help?
Thanks
Bob M.

1 Like
2

Here are teh log files. I do see the following errors:
Sep 09, 2021 16:03:25.571 [0x7f80413aed48] ERROR - HttpServer: Error binding acceptor: Address in use
Sep 09, 2021 16:03:25.571 [0x7f80413aed48] ERROR - HttpServer: Error opening acceptor on IPv6, falling back to IPv4: Address in use
Sep 09, 2021 16:03:25.571 [0x7f80413aed48] ERROR - HttpServer: Error binding acceptor: Address in use
Sep 09, 2021 16:03:25.571 [0x7f80413aed48] ERROR - Error: Unable to set up server: listen: Address in use (N5boost10wrapexceptINS_6system12system_errorEEE)download_2021-09-09_16-19-01.zip (191.3 KB)

3

Also browsing to http://10.0.10.4:32400/web/index.html it shows:

This site can’t be reached

10.0.10.4 refused to connect.

Try:

ERR_CONNECTION_REFUSED

4

Sorry looks like false alarm. Reading the post at Web not accessible after update to 1.22.3.4392 (plex pass) - #5 by TomCrawford I logged in to the server via SSH and rant netstat -lpn | grep 32400 then killed the PID for that process, stopped/started the Plex service and now it is running

5

which pid was stuck?

Is that something I need address? (i kill twice)

6

Sorry I don’t recall.

7

How is this done? I don’t know how to I log into the server via SSH and rant netstat . Please help! I cant access Plex since updating my Qnap firmware.

8
  1. Control Panel - Network and File Services
  2. Enable “Telnet & SSH”

Using PUTTY or ssh , open the connection to the QNAP, signing in as admin with the admin password. Do not use “an administrative user” . Such users do not have the necessary privileges at the Linux level.

9

Is there any other way around this? I am not that technical. I am having issues accessing Plex from outside my network. I didn’t have this issue before. I’ve tried just about everything I can think of from uninstalling/ installing, port forwarding, automatic detection, rebooting my QNAP NAS, Router/ Modem. Thank you for your reply and advise.

10

There is one way to grab the log files for me.

  1. Create a shared folder named PlexData (named exactly this way)

  2. Place it anywhere you want

  3. Stop Plex

  4. Start Plex and let it run for 2 minutes

  5. Now stop Plex again

  6. Open File Station

  7. You will find a “PlexData” shared folder

  8. In that shared folder you will find Plex Media Server. Click it.

  9. Right-Click “Logs” → Compress to Logs.zip

  10. When that’s done, download it (click the zip file) to your computer

  11. Attach the ZIP file here for me to review.

11

I think I did it correctly. I had to reactive my admin account to do so.[Logs.zip|attachment]
Logs.zip (803.4 KB)

12

@salherrera57

Yes, you did that perfectly, Thank you.

you have two adapters on the same LAN. This will be confusing.

Your server is otherwise up and running normally.

PMS has selected 192.168.0.149 as the primary. It sounds like you’re expecting 192.168.0.150?

t 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG - Detected primary interface: 192.168.0.149
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG - Network interfaces:
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 2 eth0 (192.168.0.149) (loopback: 0)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 3 eth1 (192.168.0.150) (loopback: 0)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 7 docker0 (10.0.5.1) (loopback: 0)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 8 lxcbr0 (10.0.3.1) (loopback: 0)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 9 lxdbr0 (10.0.7.1) (loopback: 0)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 10 vethhole (253.253.253.253) (loopback: 0)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 2 eth0 (fe80::265e:beff:fe3f:fddb%eth0) (loopback: 0)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG -  * 3 eth1 (fe80::265e:beff:fe3f:fddc%eth1) (loopback: 0)
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG - Creating NetworkServices singleton.
Oct 28, 2021 14:48:46.016 [0x7fe68f7216e8] DEBUG - NetworkServices: Initializing...

If you’re going to run two adapters, they should be Bonded into 1 -OR- they should be on different subnets ( that’s how TCP/IP works best )

If you want PMS to listen to one adapter over another

Settings - Server - Network - Show Advanced - Select the Preferred adapter - SAVE

It will listen on that adapter / IP from that point forward.

15

Unfortunately, this did not solve my issue. I ended up resetting my qnap and so far things are working well.

Thanks for your help!

16

Hello.

I have the same problem, but cannot fix it with the provided solutions. This is what happens:

  • When I try to connect to Plex, I get the “This site can’t be reached” error.
  • I connected to my QNAP server with ssh, went to “/etc/init.d/”, and there I ran “sudo ./plex.sh start”.
  • The “Starting Plex Media Server…” message appeared, and after a few seconds, this message appeared: “./plex.sh: line 195: ./Plex Media Server: is a directory”.
  • I checked and noticed that the script is trying to run a “Plex Media Server” program that is not there.
  • I installed the version provided by Plex, but got the same results.
  • I also installed the version provided by QNAP, also with the same results.

How can I find out what is going wrong?

Thanks in advance.

17

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