Hosted Web App cannot connect to server on local network

Server Version#: 1.18.3.2156 [Ubuntu 19.10]
Player Version#: 4.18.1 [Hosted Web App in Firefox on Windows 10]

When trying to use app.plex.tv/desktop the app cannot connect to the local server.

When using the local ip address in the form https://local-ip-address:32400/web then it connects OK (with the expected warning about an invalid certificate). BUT server is treated as “remote”, which is not desirable.

Setting PMS to allow remote access works. This also identifies the server as “remote”.

Other apps connect successfully: Android, Amazon Fire TV.

From reading forum posts and help files, this looks like it might be a DNS rebinding issue. I have changed DNS settings locally on the Windows 10 machine that I am using to connect to use 1.1.1.1. This does not fix the issue.

I do not appear to be able to change router settings (BT Smart Hub 2).

Do I need to change DNS settings on the server or just the client?

Are there any other settings or diagnostics I can try?

Try 8.8.8.8 instead.

Thank you. Just tried that. I have the same issues.
I am not sure if my ISP is over-riding my local PC network adapter settings.

They could only do that if they have access to your router’s settings.
Yes, you are supposed to change the DNS server in your router. Otherwise you’d have to do it in every plex client on the network. On the other hand, if you can’t make the change in the router, this might be your only option.

May I inquire about the IP address block used for the local LAN; whether DNS rebinding protection (blocking) is enabled on the router?

Would it also be possible to obtain the DEBUG (not VERBOSE) ZIP log files; collected after attempting to access the server through the bundled app ?

Yes! UK ISPs are notorious for providing locked-down routers. I can’t see an obvious setting for changing DNS on the router and general Googling hasn’t shown any clear solution. Most people with my ISP (BT) appear to have to set up their own DHCP server and disable DHCP on the router. Or they use a third party router.
I’ll do a bit more digging. I can use the local network server name / IP address and alter settings. It is functional, just not “perfect”.

Not 100% sure what you mean by IP address block. Local IP addresses are 192.168.1.x.
There is no obvious setting in the router for DNS rebinding. From Googling, this appears to be an ISP (I am with BT in the UK) implemented thing through their DNS. There is no clear option on the router to bypass ISP DNS. If I set a local DNS entry on my client PC, I think this is still routed through ISP DNS.

Yep. I should be able to do this. Do you want the whole ZIP or just a specific set of log files from within?

I would like to see the full debug set. I always inspect the other agent logs (framework and system logs as well )

Cool. I’ve attached the log files. The last two things I did were:

  1. Log on from a Windows 10 client pc in Firefox using http://local server name:32400/web.
  2. Log on from the same client with https://app.plex.tv/
    Plex Media Server Logs_2019-12-21_08-07-14.zip (5.6 MB)

I see a lot of photos being processed.

I also see FireFox. There are a lot of reports about the current version of FireFox.
Have you tried with Chrome?

Hi. Yes. Tried with Chrome and Edge. Both report the same - cannot connect to server.

Let’s walk through this?

  1. Sign out local web client (Upper right corner)
  2. Open incognito window
  3. Open http://LAN.IP.of.server:32400/web?secure=0 in the incognito window.

See if this brings it back. If not, you might have to reclaim it.

Caveat: Both workstation and server must be on the same subnet.

Cool. That appears to work.
I have a new Chrome Incognito Window.
I have logged into the web app using address and forcing insecure as above.
My server is connected and recognised as being “nearby”.

This also works in Firefox.

That has made me realise that I missed an important issue in my original post.
I was actually using the address http://local-server-name:32400/web as the local address.
I had tried both IP address and server name. I left the server name version bookmarked.
With the local-server-name, the server was recognised as “remote”. But using the IP address leads it to be recognised as “nearby” - both secure and insecure.

Sorry. It looks like I gave bad info and that simple change may be the cure. Apologies. And thank you for taking the time to help.
I am going to assume that the hosted web app is affected by something to do with my ISP’s DNS service. I am happy to set-up local bookmarks on laptops in the house with a local IP address.

Local server name should be using your own LAN DNS.

I figured that. Partly why I didn’t think there would be a difference between https://local-server-name:32400/web and https://local-ip-address:32400/web. But those two do work differently, so there’s something going on. At least I have a workable solution now.
Thank you for the help. Much appreciated.

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