I still get the same error when using the plex app on qnap:
This site can’t be reached
74.137.233.39 refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
ok… I think i’m catching on… Miscommunication for which I apologize
- That’s your external IP.
- The app / browser appears to be attempting to connect from the outside.
- The issue here is we’re not at that point until you can:
- Get into the browser on the LAN IP (192.168.1.77:32400/web),
- Go to Settings - Server - General and make sure it’s signed into your account
- After that’s all good, Settings - Server - Remote Access will enable access from that WAN IP (75.x.x.x)
Are you saying that I should change where it says “manually specify public port” to 75.x.x.x whatever it was instead of what it is now? Right now it’s 32400. Should I change that?
Since you are seeing that page, it tells me you’re in and connected to Plex/Web in the browser. Perfect.
You don’t put your IP address anywhere in PMS. It goes out to the internet, looks up your IP address for you
On that Settings - Server - Remote Access page,
It will look like this if you let it enable and connect itself automatically Notice the port number (shown on the right side, is not 32400
If it’s unable to ‘connect automatically’, then you’ll need to make a manual connection. Before we do that, I’d like to look at your log files after you attempt automatic. To get me the log files Click Settings - Server - Help - Download Logs. It will give you a ZIP file . Please attach that when you reply and I’ll be able to see what your QNAP isn’t happy with.
Thanks again for your help. It seems a lot of qnap owners are having problems with the latest update from Qnap.
From your logs:
Sep 29, 2017 17:25:06.965 [0x7f0d2c1d2800] DEBUG - Network interfaces:
Sep 29, 2017 17:25:06.965 [0x7f0d2c1d2800] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
Sep 29, 2017 17:25:06.965 [0x7f0d2c1d2800] DEBUG - * 3 eth0 (192.168.1.77) (loopback: 0)
Sep 29, 2017 17:25:06.965 [0x7f0d2c1d2800] DEBUG - * 8 docker0 (10.0.5.1) (loopback: 0)
Sep 29, 2017 17:25:06.965 [0x7f0d2c1d2800] DEBUG - * 9 lxcbr0 (10.0.3.1) (loopback: 0)
As said in Q21 on QNAP FAQ, when you have a machine with several NIC’s (real or virtual) you need to have certain precautions.
Do you really need docker0 ? Do you really need lxcbr0 ? Your best option in this case may be to run PMS as docker instead of normal app so it sees one, and only one NIC.
I don’t know what docker or lxcbr, are. So, maybe I don’t need them? I’m very new to all of this. I just got the Qnap and plex. I thought plex would work just by clicking the app but after searching google, it appears something changed on qnap’s end when they updated their OS to 4.3.
Did you install Container Station in your QNAP ? Do you really need it ? If not, remove Container Station, restart PMS, and the problem should be solved. If not pls post new logs.
If you really need Container Station, then you should install PMS’s docker version and not the QNAP one.
That didn’t work. I guess you have to have container station to use browser station. I downloaded the logs again, not sure if it matters but I’m downloading them from my laptop rather than my qnap since I can’t access it there.
Your network is good now as far as PMS is concerned.
Something between the QNAP and the internet is a problem.
It’s having trouble getting outside.
Error ‘28’ is a time out (no reply in allotted time)
Sep 30, 2017 10:17:46.032 [0x7f6169623700] DEBUG - PubSubManager: Updating best ping time for 45.79.11.43 to 974 ms.
Sep 30, 2017 10:17:47.803 [0x7f61609a1700] DEBUG - IVA: Downloaded 50 trailers for source 2.
Sep 30, 2017 10:17:48.770 [0x7f6161559700] ERROR - Error issuing curl_easy_perform(handle): 28
Sep 30, 2017 10:17:48.770 [0x7f6161559700] DEBUG - HTTP simulating 408 after curl timeout
Sep 30, 2017 10:17:48.793 [0x7f6166fff700] ERROR - Error issuing curl_easy_perform(handle): 28
Sep 30, 2017 10:17:48.793 [0x7f6166fff700] DEBUG - HTTP simulating 408 after curl timeout
Sep 30, 2017 10:17:49.673 [0x7f61677ff700] ERROR - Error issuing curl_easy_perform(handle): 28
Sep 30, 2017 10:17:49.673 [0x7f61677ff700] DEBUG - HTTP simulating 408 after curl timeout
Sep 30, 2017 10:17:55.005 [0x7f6167fff700] WARN - NAT: PMP, timed out waiting for response.
Sep 30, 2017 10:17:55.005 [0x7f6169911700] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
So I can’t use browser station with Plex, right?
Also, any thoughts on a fix for this? Contact qnap?
I don’t know if you can but definitely a “Contact QNAP” question.
This might be a case where a TeamViewer session with them is best.
Will do. Thank you for all of the help.
I would suggest to get rid off browser station and container station. If you really need to access the QNAP UI (and/or other services) from abroad I would suggest to use QVPN instead (parametrized for OpenVPN). The OpenVPN client can be installed on several portable devices (windows, android, linux, ios, etc) and works like a charm. And it provides something very important when it comes to security -> certificates. Therefore the chances to have your QNAP hacked are much lower with OpenVPN.
Don’t trade security for simplicity, your harm can be enormous (I’m trying to help a QNAP user in the spanish forum whose system was hacked, so this is very present for me). Non-trivial passwords is the first rule, certificates the next one, and blacklisting IP’s after 2-3 failed login attemps a must.
I’m fine with getting rid of both once the plex app works. Right now, browser station is how I access my library on the qnap though. I submitted a ticket with qnap this morning but haven’t heard anything. Probably will not hear from them until Monday.
I’m good to go now!! I wanted to post it here hoping to help someone else that may experience this. I did get into a team viewer session with a qnap tech and they changed made me a new static ip and then used that ip to connect to my qnap. It was not using the static ip that I had created for some reason. I hope that makes sense and I hope that helps someone. Thanks again to those of you who tried to help me.
