I did have issues initially after the upgrade from Hub 5 to Smart Hub. After manually forwarding the port 32400 on both PMS and the router and waiting a few minutes it did, and still is working (2months approx no issue). But there is something amiss. I had to repeat the procedure (manually forwarding and then un-ticking the manual box on PMS) several times.
this is still causing issues here too - tried both with 32400 as external and a random number (both with 32400 as internal), gave the server a static ip (as it had on the hh5 and worked) and tried tcp, udp and both
in between each setting I’ve been restarting (complete shut down and back up) of both my pc and router
bugger all working remotely !
even tells me cant get a direct access within the network
is there a proper fix for this - smart hub 6 still wont forward for me (hh5 did and still does work fine)
@SketchDes1gns said:
is there a proper fix for this - smart hub 6 still wont forward for me (hh5 did and still does work fine)
I have tried your public IP and port and managed to get to the server remotely - however, there is some mismatch with the security certificate for the server. Try and sign the server out and re-claim it (Settings / Server / General ) in Plex Web
So is 192.168.1.73 set as reserved / permanent in the Home Hub ?
With a port forward in place and the public port (32400 in your case) is manually specified on the server remote access settings page, it should be reliable and should stick. There are timing issues when switching back and forth between manual and uPnP ports - but once set as manual it should stick after the initial setting
@sa2000 said:
So is192.168.1.73set as reserved / permanent in the Home Hub ?
With a port forward in place and the public port (32400 in your case) is manually specified on the server remote access settings page, it should be reliable and should stick. There are timing issues when switching back and forth between manual and uPnP ports - but once set as manual it should stick after the initial setting
correct, I have set a static ip for my server via the router setup (I run a repeater to which the pc is connected but this has been the case for ages and worked fine with the last router).
I’ll try re-claiming it as suggested and get back to you
EDIT: it works when I disable the firewall all together (guess this is when you saw it) but would prefer not to leave it that way.
It didnt fix by re-claiming either and it was an allowed app through the firewall
confused
P.S. Also, do you know why my ps4 is the only device (all 3 of them) that wont show as a “player” to play to?
Fire stick shows fine, pc (web player) works, phone(s) do but ps4 never shows up in the drop down
@SketchDes1gns said:
@sa2000 said:
So is192.168.1.73set as reserved / permanent in the Home Hub ?
With a port forward in place and the public port (32400 in your case) is manually specified on the server remote access settings page, it should be reliable and should stick. There are timing issues when switching back and forth between manual and uPnP ports - but once set as manual it should stick after the initial settingcorrect, I have set a static ip for my server via the router setup (I run a repeater to which the pc is connected but this has been the case for ages and worked fine with the last router).
I’ll try re-claiming it as suggested and get back to you
EDIT: it works when I disable the firewall all together (guess this is when you saw it) but would prefer not to leave it that way.
It didnt fix by re-claiming either and it was an allowed app through the firewall
P.S. Also, do you know why my ps4 is the only device (all 3 of them) that wont show as a “player” to play to?
Fire stick shows fine, pc (web player) works, phone(s) do but ps4 never shows up in the drop down
Your post was 4 hours ago yet plex.tv info shows server named SketchPC was last seen by plex.tv 8 hours ago - How long before the timestamp of this forum post was the server signed out and re-claimed ?
With regards to the firewall, could you check that your network connection is showing as a Private Network in windows and not Public Network. Strict firewall rules apply if the network is interpreted by windows as a public network. And if it is this, google search for change local network from public network to private network will find you loads of hits to read and follow
In any case, it would be beneficial to also create through Firewall Advanced Settings, a port rule (not a program rule). In this rule you do not specify any program but just the following:
Select Advanced Settings
Select Inbound Rules
Select New Rule
Select Port as the Rule Type
Click Next
Select TCP
Select Specific Local Port and enter 32400
Click Next
Select Allow the connection
Apply to Private and Domain if you have a local domain
Give it a name
If you open the rule, you will see it has
All Programs
Remote Port: All Ports
Local Port 32400
TCP
IP Addresses: Any
If there is an issue claiming the server, please restart the server and try it and get logs and attach here
See https://support.plex.tv/hc/en-us/articles/201643703-Reporting-issues-with-Plex-Media-Server
https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
So it’s been a year since my original post and I’m still having issues.
Whether Plex Server is “Fully accessible outside your network” seems very hit-and-miss. I’m not sure what triggers my server to NOT be accessible but every so often I can no longer connect to it remotely, and it seems the only solution is to restart the Smart Hub. It’s not all that smart after all…
For what it’s worth - one thing I have noticed is that I haven’t needed to configure anything on the hub or in Plex Server admin, it’s all ‘plug and play’ - in the Port Forwarding section of the hub admin it automatically adds Plex Server. In fact there are two entries, one forwarding 15207 to 32400, and the other forwarding 27632 to 32400. I also have “Manually specify public port” unchecked in Plex Server admin.
When it works, it works. Then, for no reason that I can fathom, it will stop working. I restart the hub, and it starts working again. Go figure…
@mattbailey said:
So it’s been a year since my original post and I’m still having issues.Whether Plex Server is “Fully accessible outside your network” seems very hit-and-miss. I’m not sure what triggers my server to NOT be accessible but every so often I can no longer connect to it remotely, and it seems the only solution is to restart the Smart Hub. It’s not all that smart after all…
For what it’s worth - one thing I have noticed is that I haven’t needed to configure anything on the hub or in Plex Server admin, it’s all ‘plug and play’ - in the Port Forwarding section of the hub admin it automatically adds Plex Server. In fact there are two entries, one forwarding 15207 to 32400, and the other forwarding 27632 to 32400. I also have “Manually specify public port” unchecked in Plex Server admin.
When it works, it works. Then, for no reason that I can fathom, it will stop working. I restart the hub, and it starts working again. Go figure…
This is using uPnP automatic port configuration and it is known to be unreliable. Having a port forward that you configure is solid and does not rely and how routers respond to uPnP SSDP searches and requests
I would delete those two automatically setup port forwards and do the following
- make sure that 192.168.1.217 is setup as a DHCP Reservation in the router so it does not change
- Create a manual port forward to tcp port 32400 on 192.168.1.217. For simplicity use the same port as wan / public port. So create a port forward for tcp port 32400 to go to tcp port 32400 on 192.168.1.217
- On the server remote access settings, tick the box
manually specify portand enter the public port selected - which is the 32400 I suggested. and click connect. You may need a retry but do leave some time between clicks - suggest 30 seconds - you may need to restart the router and server
With BT Smart hubs you create an entry for Plex Media Server port forward under gaming under the router firewall 0- in the hub advanced settings and then you select that rule to attach to 192.168.1.217
I know this isn’t exactly the same scenario, but I’ve also moved to a Smart Hub / HH6 and having problems with Plex.
The difference is that I can’t even complete the Plex setup. On boot, I get the “This server is unclaimed and not secure” message but there seems to be an error when pressing the “Claim Server” button.
Having read through this thread, I’ll try disabling advanced uPnP and setting up ports manually when I get home tonight. But I thought I’d ask whether anyone else has had this problem.
If there is an error on the claim - find the server logs and zip and attach
Settings / server / help / download logs
Thanks sa2000. I’ll grab the logs when I’m home tonight.
Hi sa2000. Thanks for taking the time to have a look at this. I’ve attached the logs.
I think it might be something to do with the curl_easy_perform errors. Error code 7 (CURLE_COULDNT_CONNECT), followed by a bunch of error code 28s (CURLE_OPERATION_TIMEDOUT).
From that, I think it seems to be some kind of DNS issue. I can curl google.com and google.co.uk but not plex.tv. I’ll look into that first.
I do have port 32400 forwarded and uPnP enabled.
It was DNS. With my previous ISP I had a VPN set up, which was no longer required.
Uninstalled iptables and rebooted. One happy Plex server!
Thanks for the offer of help, and apologies if you spent much time on the log files!
@MMeldrum said:
It was DNS. With my previous ISP I had a VPN set up, which was no longer required.Uninstalled iptables and rebooted. One happy Plex server!
Thanks for the offer of help, and apologies if you spent much time on the log files!
I have only just looked - sot wasted much time
It was as you found - timeouts on requests going to plex.tv
Here I am again, over 2 years later 
So my issues over time with BT’s hubs and remote access have been pretty random. Sometimes it seems to work, and some times it doesn’t. However, I just spotted something today (after noticing it wasn’t working again) which may have something to do with it…
I’m using an old Mac Mini as my media server. It has a wired ethernet connection (naturally), but I spotted today that I had enabled wifi at some point. As soon as I disabled wifi, remote access worked again.
Go figure? I guess there’s some kind of clash between the two network protocols. Such a stupid simple fix if it is the cause of all the problems I’ve been having. I thought I’d post this here, just on the off-chance it helps someone else.
There are two other forum threads with recent issues to do with wifi on BT Homehub - as yet not understood and my thoughts are that it sounds like a recent BT Homehub change
See
I am a UK BT Homehub6 + Plex user and am having a similar (but not the same problem).
I have uPNP on. Both remote and local access works, but I constantly get the following 2 errors"
|Apr 25, 2019 12:01:02.719|ERROR|EventSource: Retrying in 15 seconds.|
|Apr 25, 2019 12:01:02.718|ERROR|getaddrinfo(192-168-1-252.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -2|
Some might say “it’s working, take the win” but these errors every 15 seconds annoy me. All I know is it is to do with reminding. I have factory reset my router (advice from the BT forums) but the errors keep coming.
Any ideas?
Those 2 errors are unrelated.
For the EventSource one, would need debug logs to see what it is relating to. It may be a shared server that your server is trying to communicate with and is harmless
For the getaddrinfo error this just means that your router has DNS Rebinding Protection and blocks any attempt to access the server within the local network through the https plex.direct domain url that Plex Media Server uses. BT Homehubs have been seen to do that and last time I looked into it, there was no configurable option for whitelisting plex.direct url’s for DNS Rebinding Protection
The impact of DNS Rebinding Protection is failure to use secure connections within the local network and client apps may end up finding a usable https route through the remote access public IP route
This should not affect remote access
The first error - EventSource error may affect remote access if it is relating to the Plex pubsub servers - but logs would be needed (DEBUG enabled) to investigate
1 Like
HI sa2000,
Thanks! …that makes total sense - one off my remote servers is offline and I do not access locally securely. I have added my logs.
Plex Media Server.log (456.2 KB)
Are you a brit with BT? …can you recommend a router setup that would be better or should I simply not worry about secure local access on my own network?
cheers,
James,
Thanks for the log. The log with debug logging was only for a very short while - just one minute of debug logging. So cannot say if all the EventSource errors were for same reason but from what i can see in this short period, there was an EventSource error logged to do with periodic connection checks with shared server Fenella’s MacBook Air - which was not responding
With regards to your server’s remote access, I see that you have automatic port mapping using uPnP and that this was successful and public port 19466 used.
You may find that switching to a manually specified port within server settings for remote access with a port forward in the router gives you more reliable outcome.
So first make sure your local IP address for the server 192.168.1.252 is setup as a DHCP Reservation in the router - i.e. assigned permanently within the DHCP Setting for that computer
Then decide on what public port to use - you could for example pick on 32450 a variation on the default port 32400 used internally.
Setup a port forward service in the router to port forward wan/public port 32450 to lan/local/private port 32400.
Then assign that service to the computer 192.168.1.252 within the router setting. Then in Plex Media Server Remote Access settings, click on Show Advanced and tick manually specify port and enter 32450 as the port and connect/retry. You may need to disable and re-enable remote access - ensuring manually specified port remains ticked and 32450 being the public port
Manual Port selection and port forward is more reliable because it does not rely on the router responding to SSDP searches for remote access to work. I have seen BT Homehub routers sometimes taking a long time to respond causing problems with setup
With DNS Rebinding protection on the BT Homehub. it becomes important to have remote access working as plex client apps could then connect securely within the local network using the remote access route.
I was with BT but I switched to Virgin. Virgin does not have DNS Rebinding protection but blocks access through the Public IP on the local network - this only affects use of Microsft Edge which has its own extra security blocks on access through plex.tv/web
In the past i used my own routers eg Netgear or TP Link and I had the ISP router in bridge mode and then my own router with the DHCP and NAT Routing setup. But currently just use the ISP router
1 Like
