PlexConnect keeps loading trailers - XML error PlexAPI: URL: %2F%2Fowned

Dev Community Apps & Creations
1

PlexConnect doesn't work anymore and seems to get an error connecting to plex, it get's an XML error 

The result is it keeps loading at the trailers screen and doesn't work anymore, i have no idea how to fix this.

Steps i've allready done: reinstalling PlexConnect, cleaning up the database in Plex.

Does anyone have an idea how to fix this? 

 

my data:

  •  Apple TV software):3   6.1

  • The DNS server set on the ATV (found under the ATV settings > general > network > DNS): 192.168.1.71

  • The local IP address of the device that PlexConnect is installed on:192.168.1.71

  • The device and operating system (including version number) that PlexConnect is installed on: server Ubuntu 12.04.4 LTS

  • The device and operating system (including version number) that the Plex media server (PMS) is installed on: server Ubuntu 12.04.4 LTS

  • The Plex media server (PMS) version number you are running (do not put 'latest'): 0.9.9.7.429-f80a8d6

  • The local IP address of the device that the Plex media server (PMS) is installed on:192.168.1.71

  • plexconnect version: git pull march 22 2014 (fresh re-install)

pastebin url : http://pastebin.com/cLm99Lca

 

[PlexConnect]
enable_plexgdm = False
ip_pms = 192.168.1.71
port_pms = 32400
enable_dnsserver = True
port_dnsserver = 53
ip_dnsmaster = 8.8.8.8
prevent_atv_update = True
enable_plexconnect_autodetect = False
ip_plexconnect = 192.168.1.71
hosttointercept = trailers.apple.com
port_webserver = 4500
enable_webserver_ssl = True
port_ssl = 4501
certfile = ./assets/certificates/trailers.pem
loglevel = High
logpath = .
2

Your log file has been uploaded as a private paste, if you could change or re-upload publicly please.

Also do you have the required reverse proxies set up for ports 80 and 443, seeing as you have changed the ports in settings.cfg?

3

I guess he might have the reverse proxy running, but missing that stupid "allow double slashes in URL"... or something.

I really got to get that "//" removed...

4

Pastebin has been fixed, the reverse proxy has been setup correctly, the // is probably the issue iĺl try and fix that, any tips?  

5

Fixed it :)

adding AllowEncodedSlashed On  & the nocanon option to ProxyPass seems to do the trick.

>>  Normally, mod_proxy will canonicalise ProxyPassed URLs. But this may be incompatible with some backends, particularly those that make use of PATH_INFO. The optional nocanon keyword suppresses this, and passes the URL path "raw" to the backend. Note that may affect the security of your backend, as it removes the normal limited protection against URL-based attacks provided by the proxy.

        ServerName trailers.apple.com
        ServerAlias atv.plexconnect
        SSLEngine On
        SSLProxyEngine On
        SSLCertificateFile /usr/local/lib/PlexConnect/assets/certificates/trailers.cer
        SSLCertificateKeyFile /usr/local/lib/PlexConnect/assets/certificates/trailers.key
        ProxyPreserveHost On
        AllowEncodedSlashes On
        ProxyPass / https://192.168.1.71:4501/ nocanon
        ProxyPassReverse / https://192.168.1.71:4501/
6

I guess he might have the reverse proxy running, but missing that stupid "allow double slashes in URL"... or something.

I really got to get that "//" removed...

Ok. We now got the need for "AllowEncodedSlashes On" removed.

Shoxnl, please grab the latest from github, remove that line, restart Apache and try again. :-D

Also, you can remove the "atv.plexconnect" line, that one is long gone.

Can you explain, what that "nocanon" does? Just out of interest...

7

Ok, got the update, removed "AllowEncodedSlashes On" and nocanon.

Seems to work fine now. :) thx again.

As i explained in the posting above ^ Normally, mod_proxy will canonicalise ProxyPassed URLs. But this may be incompatible with some backends, particularly those that make use of PATH_INFO. The optional nocanon keyword suppresses this, and passes the URL path "raw" to the backend. Note that may affect the security of your backend, as it removes the normal limited protection against URL-based attacks provided by the proxy. 

But seeing i'm using it only in "home" environment that wasn't a problem

8

Ah. Read that one the day before yesterday. Must have forgotten about it already. Thanks! :-)