Error Connection Refused

Did you ever find a solution to this Dane22? I am having the exact same issue. Very frustrating. I am only trying to access the server locally in my network

Mine:
Ts-431
Version: 0.9.12.13.1464-4ccd2ca_arm-x31
Static: Yes,
Port: Port forward 32400 to the static IP
(although, I am only trying to access locally not sure this matters)
ISP: I am accessing locally
QTS: 4.2.0

** I am using PFSense as a firewall. Not sure if this matters since I am only trying locally.

After a reboot, I can access it (sometimes) . Sometimes for minutes, sometimes for hours. But at some point it always becomes unreachable. No difference using IP# or Name.

Sadly not there yet :frowning:

/T

Hi, I had this problem, and solved it.
Solution:
On QNAP apps center go to PMS and download package manually and install it
In my case: PlexMediaServer_0.9.12.8.1362-4601e39_x86

I was on 9.12.8.x with this issue. I waited for the upgrade and deleted PMS from Qnap and installed v0.9.12.13 last week… same issue.

I’m having the same problem, but PMS is running on a Mac Mini…

Today I noticed that Plex had crashed on the mini, so I hit reopen. After that I haven’t been able to load the page at all, either on the Mini directly or via another laptop on the lan. I’ve quit it and restarted the app a few times (not the Mini yet).

I just left it running for 5 mins (couldn’t get to the page at all during this time) and the app has just crashed again.

Opened it again and noticed that ā€œPlex Media Scannerā€ is using 99% of the CPU (or a core anyway) so I guess it’s trying to do something, but ultimately failing.

If I ever get it going again (I’ll try a reboot I guess) I’ll turn on the logs, but it had been running for a full week or so before this so who knows when it’ll happen again.

EDIT: Right, looks like it was Plex Media Scanner that was the problem. It had been running out of control for a while it seems. I force quit it and things are back to normal now…

I was having the Error Connection Refused problem on a QNAP 459 firmware version 4.2.0 build 20161103 with Plex 0.9.15.3 t

This problem started about a month ago, prior to this the Plex server ran on this QNAP for months without problems. Eventually (in frustration) I manually upgraded to Plex 0.9.16.4 and thought the problem was solved but alas it was not. However this time I was able to get a work around. The problem manifested itself when the QNAP powered up after a power failure (unclean shutdown). I tried turning the PLEX service on and off several times without success. I also tried rebooting the NAS without success. I finally succeeded by turning off the PLEX service, rebooting the QNAP and restarting the PLEX service.

My turn (I guess I need to save up for a UPS). Yesterday I suffered a power failure and had my connection refused. After many NAS reboots and turning the service on and off I ended up removing PMS entirely and manually installing (as ever) the app. Is took me right back to the beginning (i.e. building my libraries from scratch, matching all my content, etc.). I lost my modified cover art, my collections, any customisation. However, it was slowly all coming back until another power failure today (I think my dLAN is tripping my fusebox). I am currently refusing connections again so, before I go right back to the beginning again I turn to you for help.

I am not the most proficient at this (surprise) so shall need help to find answers to some of the stock questions! Attached is the error message. I can access my QNAP admin interface (running 4.2.2 on my TS-251)

Version of Plex Media Server? 1.1.2.2680
Is the QNAP on a static IP? How can I tell?
Are you using uPNP, or manual forward? How can I tell?
Do you have a static IP from your ISP? How can I tell?

I’m sorry to be so hopeless but I had everything working so well and now this goes and happens. Once I find out how to fix it I’ll know for the future as I’m sure this will happen again until I can get the UPS.

Thank you so much in advance, and HELP!

Streaky

I should add that I am running PMS on my NAS but controlling/configuring from my MacBookPro running l Capitan. I have made no configuration changes before or since the first power failure and everything was running fine beforehand. I cannot access PMS via my QNAP’s web interface at all so cannot check any settings there. I have reset the router, modem, NAS and Mac various times.

Well I’m scootered! I just got access to the PMS web interface via the normal IP address (http://192.168.1.22:32400/web/index.html#!/settings) after rebooting Mac and NAS, stopping the PMS app and reinstalling the same version. I can’t access the actual server but I can access PMS settings. What now?

But not server settings (unsurprisingly).

This is what it says about last contact with the server (7 hours ago):

1.1.2.2680-09e98fb
Plex Media Server
PC
Linux 3.12.6 (#1 SMP Tue Aug 23 00:56:07 CST 2016)

I think my Mac player and server are on different sub-nets of the same network (from an earlier error message I recall): how do I check that?

@jmaas28 Open a terminal on your Mac, and type ā€œifconfigā€

Then post the output

/T

Thank you dane22. Still exploring how to fix it. Here’s the output:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=1
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 14:10:9f:d4:10:2f
nd6 options=1
media: autoselect ()
status: inactive
en1: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
options=60<TSO4,TSO6>
ether 32:00:15:df:d0:a0
media: autoselect
status: inactive
en2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
options=60<TSO4,TSO6>
ether 32:00:15:df:d0:a1
media: autoselect
status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
ether 06:10:9f:d4:10:2f
media: autoselect
status: inactive
awdl0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1484
ether 96:2f:4f:23:df:5f
nd6 options=1
media: autoselect
status: inactive
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether 40:6c:8f:52:0c:5e
inet6 fe80::426c:8fff:fe52:c5e%en5 prefixlen 64 scopeid 0x9
inet 192.168.1.204 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=1
media: autoselect (100baseTX )
status: active
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 16:10:9f:4d:2e:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 5 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 6 priority 0 path cost 0
nd6 options=1
media:
status: inactive

@jmaas28 said:
Thank you dane22. Still exploring how to fix it. Here’s the output:

en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether 40:6c:8f:52:0c:5e
inet6 fe80::426c:8fff:fe52:c5e%en5 prefixlen 64 scopeid 0x9
inet 192.168.1.204 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=1
media: autoselect (100baseTX )
status: active

So your IP Address is 192.168.1.204 with a subnet of 255.255.255.0

Now for your QNAP, go here:

/T

Thank you. I don’t have a TCP/IP or Wi-Fi or other options, I have this:

Do I need to activate the network & virtual switch?

I hate QNAP and their ā€œNew and fancyā€ versions :wink:

Click on the information icon to the right

Like this?

Here’s what’s behind the info icon for the connected adaptor;

And that answers your Q then regarding subnets…
You are in the same IP Net.

Now my turn to ask questions :wink:

If you browse to 192.168.1.22:32400/web you are seen what excatly?

/T

I’m liking this help!

This is what I see: