Project

General

Profile

Bug #1973

Plex - Blank Page or DNS Lookup Error

Added by crayserver about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Apps
Target version:
Start date:
03/01/2016
Due date:
% Done:

0%


Description

I get either a blank page when trying to access Plex from the Dashboard, or a DNS lookup error, depending on the solutions that I have tried.

Steps I have tried:
1. Tried localhost in \etc\httpd\conf.d\*plex*.conf, systemctl restart httpd. Result = blank page
2. Replaced hda with localhost, systemctl restart httpd. Result = 502 Proxy Error. The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /index.html. Reason: Error reading from remote server.

3. Per Wiki, commented out ProxyPass and ProxyPassReverse. Added below code. systemctl restart httpd.  Result = No Data Received. ERR_EMPTY_RESPONSE. Unable to load the webpage because the server sent no data.
        RewriteEngine On
        RewriteCond %{SERVER_PORT} 80
        RewriteRule (.*) http://%{HTTP_HOST}:32400/manage/ [R,L]
4. Per Wiki, tried option 2.

Create a text file called "index.html" and save that file in /var/hda/web-apps/plexms/html The contents of the file is a simple redirect. It should read:
<html>
<head><meta http-equiv="refresh" content="0; url=http://hda:32400/manage/" />
</head>
<body></body></hmtl>

Notes: Plex Media Server is running.

http://paste.fedoraproject.org/331957/14568728/ -> http://paste.fedoraproject.org/331957/14568728

History

#1 Updated by crayserver about 5 years ago

I should say also that I have uninstalled and reinstalled twice (from the App).

#2 Updated by crayserver about 5 years ago

Also ran chown -R apache:users /var/lib/plexmediaserver. Result = Unable to load web page because server sent no data.

[root@ /]# systemctl status amahi-plex
? amahi-plex.service - Plex Media Server for Amahi
   Loaded: loaded (/usr/lib/systemd/system/amahi-plex.service; enabled)
   Active: active (running) since Tue 2016-03-01 08:57:03 MST; 7h ago
  Process: 764 ExecStart=/usr/bin/amahi-plex (code=exited, status=0/SUCCESS)
 Main PID: 769 (runuser)
   CGroup: /system.slice/amahi-plex.service
           ?? 769 runuser -u apache -g users /usr/lib64/plexmediaserver/Plex Media Server
           ?? 772 /usr/lib64/plexmediaserver/Plex Media Server
           ??1155 Plex Plug-in [com.plexapp.system] /usr/lib64/plexmediaserver/Resources/Plug-ins-e0b7243/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.pyc --server-version 0.9.14.6.1620-e0b7243 /usr/lib64/plexmedias...
           ??1303 /usr/lib64/plexmediaserver/Plex DLNA Server

Mar 01 08:57:03 . runuser[769]: pam_unix(runuser:session): session opened for user apache by (uid=0)
[root@ /]#

#3 Updated by cpg about 5 years ago

  • Description updated (diff)

#4 Updated by cpg about 5 years ago

this smells like a bug in their app. would you like to test the latest?

if interested, please do this without reinstalling the amahi app:

rpm -Uvh http://alpha.amahi.org/tmp/amahi-plex-0.9.15.6-1.x86_64.rpm

please report how it goes if you test it out.

#5 Updated by crayserver about 5 years ago

Ran rpm -Uvh ...

Same symptoms. Tried both localhost and hda in the .conf file. localhost gives a blank page, and hda gives:

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /index.html.
Reason: Error reading from remote server

#6 Updated by cpg about 5 years ago

what is your client device and browser?

is your client device using your HDA for DNS?

plex media server has been misbehaving as it relates to this more and more. sigh.

#7 Updated by crayserver about 5 years ago

Been at this for hours, tried fresh install via Wiki instructions. Results are the same.

Using Chrome (also tried IE). Win 10. Using HDA for DNS. Everything else works fine. Too bad, this was the killer app for me.

#8 Updated by crayserver about 5 years ago

Next actions taken:

1) Rebuilt Amahi server from scratch.
2) Installed Plex App
3) I still get this error when going to plexms.mydomain.com
Proxy Error. Reason: DNS lookup failure for: hda
4) Tried http://localhost:32400/web. Result = Error, connection refused.
5) Tried http://192.168.0.10:32400/web. Result = GOOD! I can now access the dashboard.

Not sure why the name is not resolving though.

#9 Updated by bigfoot65 about 5 years ago

  • Assignee set to crayserver
is your client device using your HDA for DNS?

Please answer cpg's question. If you are not using the HDA for DHCP and DNS, then that is why it would not work.

#10 Updated by crayserver about 5 years ago

Sorry, I guess I am a bit confused. Yes, I am using HDA for DHCP, and router DHCP has been disabled. But I am not sure how to answer the DNS question.

#11 Updated by bigfoot65 about 5 years ago

Check your client machine for DHCP and DNS servers. If they are not point to the HDA IP address, then something is amiss.

#12 Updated by crayserver about 5 years ago

Windows IP Configuration

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : mydomain.com
   Link-local IPv6 Address . . . . . : fe80::d445:6b4e:3e05:9b94%3
   IPv4 Address. . . . . . . . . . . : 192.168.0.106
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

Tunnel adapter Local Area Connection* 3:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:30d6:24d7:9e89:1fa4
   Link-local IPv6 Address . . . . . : fe80::30d6:24d7:9e89:1fa4%2
   Default Gateway . . . . . . . . . : ::

Tunnel adapter isatap.mydomain.com:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : mydomain.com


Is this what you need?

#13 Updated by bigfoot65 about 5 years ago

Do the following and post the DHCP and DNS info:

ipconfig /all

#14 Updated by crayserver about 5 years ago

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : mydomain.com
   Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection
   Physical Address. . . . . . . . . : C8-60-00-0A-83-77
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d445:6b4e:3e05:9b94%3(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.106(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, March 1, 2016 11:26:51 PM
   Lease Expires . . . . . . . . . . : Wednesday, March 2, 2016 6:22:57 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.10
   DHCPv6 IAID . . . . . . . . . . . : 46686208
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-E8-09-3F-C8-60-00-0A-83-77
   DNS Servers . . . . . . . . . . . : 192.168.0.10
                                       192.168.0.10
   NetBIOS over Tcpip. . . . . . . . : Enabled

#15 Updated by cpg about 5 years ago

ok, dns appears correct.
(also, thanks for using pre blocks properly)

next is to try with some other browser in your client,

1) using the full url (with your internal domain)
2) using the short name -- just http://plexms/ including the slash at the end.

#16 Updated by crayserver about 5 years ago

Trying IE11.

1) http://plexms.mydomain.com/ Result = 502 Proxy Error. DNS lookup failure for: hda
2) http://plexms/ Result = 502 Proxy Error. DNS lookup failure for: hda

Reminder this is a fresh install. Not sure if this is relevant, but using the App eZ Server Monitor, I get the following:

Unknown.domain - 192.168.0.10
SYSTEM
Hostname Unknown.domain

Shouldn't that have mydomain.com?

#17 Updated by cpg about 5 years ago

  • Status changed from New to Closed
  • Assignee changed from crayserver to cpg

Thanks to @crayserver for letting me hack debug into his machine.

Basically, the current release of Plex Media Server has a broken web interface. Again.

More precisely: their web assets are served from /web/* instead of /* as they should.

Their web interface is at /web, however, we, through apache, proxy it to / with our DNS name. We (well, apache) does the proper proxying, near as we can tell.

Their coders look like amateurs and don't know how to properly code something as simple as relative names for various assets.

There are a couple of work-arounds, none of the great:

1) use http://hda:32400/web/ as the entry point for their web interface and remember
2) change the apache virtualhost config file to remove /web from proxying and use http://plexms/web however, this requires a custom configuration (or we change the app for however long they ship the buggy app). The problem here is that we just allow for this, users going to http://plexms/ (without web) they will hit an XML page (which looks as if it's their API -- sigh)

It's dismaying to see such an arrogant (yet small and local to me) company, using shoddy coding like this (again).

Conclusion

Please use http://hda:32400/web/ as the entry point for the app web interface.

Also available in: Atom