Upgrade issue from 0.2 to 0.3.1+ on Centos 6.5

Dev Community Apps & Creations
1

With version 0.2, I definitely didn't have any issues. Apple TV3 version 5.3
Today, upgraded to 0.3.1+ from github.
Now it says "Accessing Trailers" and nothing happens. It seems that plexconnect can't answer the requests or cannot serve the file "utils.js" or something else. (screenshot added)

I tried to delete Setting.cfg, recreated and edited but no luck.
I am on Centos 6.5. I am using bind and dnsmasq for dns resolving so dns is not an issue. But also tried with dns server of plexconnect. It didn't work either.
Also tried with python 2.7.6 but no luck.
Tried 0.3.1+ on a Windows PC with python 2.7.6, worked like a charm.

Plexconnect log is here

 

Settings.cfg

[PlexConnect]
port_pms = 32400
port_webserver = 90
ip_plexconnect = 0.0.0.0
certfile = /usr/local/lib/plexconnect/cert/trailers.pem
ip_dnsmaster = 8.8.8.8
loglevel = High
enable_dnsserver = False
logpath = .
ip_pms = 192.168.80.5
enable_plexgdm = False
hosttointercept = trailers.apple.com
port_ssl = 453
enable_webserver_ssl = True
ip_webserver = 0.0.0.0
prevent_atv_update = True
port_dnsserver = 53
enable_plexconnect_autodetect = True

Any help will be appreciated.

Thank you.

 

2

Are you able to upgrade python to 2.7.x?

3

yes. I also tried with 2.7.6 but no luck. One thing I forgot to mention is I can reach plexconnect settings on ATV3. But Library or channels are unreachable.

Proof of version 2.7.6 is attached.

4

Where is your PMS located?

Does it have "require authentication" set?

Are you logged into MyPlex?

Also, set logelvel to High and provide the LOG. It should give more detail about GDM and stuff. Speaking of that...

Why did you disable PlexGDM?

5

Where is your PMS located?

Does it have "require authentication" set?

Are you logged into MyPlex?

Also, set logelvel to High and provide the LOG. It should give more detail about GDM and stuff. Speaking of that...

Why did you disable PlexGDM?

PMS is on the same machine, Centos 6.5

No authentication.

No, not logged into MyPlex

On first post I posted log file with high level to pastebin.

http://pastebin.com/GxsBfgkQ

The reason disabling gdm is when ATV sleeps and then wakes up it can't resume the conection to plexconnect and I always have to restart ATV. This option helped to overcome this behaviour.

BTW enabled gdm but same result.

With this settings version 0.2 works without any problem.

6

Baa, when was SSL requirement added, post 0.2?

Could it be port 443 getting blocked on the Linux firewall?

7

Linux firewall permits all connections from LAN.

8

If you copy the working folder from your Win installation, disable dnsmasq and run it does it work?


Edit: it may be best to throw the settings.cfg file away though.

9

Did that. Deleted settings.cfg, recreated it and edited it from scratch. Same result.

10

>>f00b4r - SSL requrirement

Check the WIKI. :-)

Had a quick look, release v0.1 says "(as of 27Aug13: defunct with Apple's switch to https)"

v0.2 is dated 24Sep13, I guess it was done when the SSL dust had settled...

11

msurg:

>>loglevel = High

Ah. Oversaw that "attachment".

Okay. What I find strange in that LOG is...

15:01:48 PlexAPI:

Why would PMS identify itself with 127.0.0.1? I guess I have never seen that... but then, I don't run it with GDM=Off either.

In the following lines, it _seems_ like the real IP is restored somehow. The question is: Seen from PlexConnect/NAS point of view, does PMS answer on 192.168.80.5 - or would it only respond to 127.0.0.1?

Are you able to ssh (or something) into your NAS and grab the response to 192.168.80.5:32400 versus 127.0.0.1:32400 - using curl or something?

12

[root@ ~]# curl 127.0.0.1:32400   
<?xml version="1.0" encoding="UTF-8"?>












[root@ ~]# curl 192.168.80.5:32400
<?xml version="1.0" encoding="UTF-8"?>












13

What’s the overview of your network (IP addresses and anything virtualised)?

Is it only playback that is the issue? Can you see the PlexConnect interface and navigate the screens?

14

Nothing virtualised.

Linux (Centos 6.5) has the IP 192.168.80.5 and plexconnect and PMS are installed on this device.

ATV's IP is 192.168.80.30. Both can connect to internet without an issues

The issue is ATV can connect to plexconnect, I can see the starting screen, I can choose settings and can navigate in settings, but when I choose Library or Channels it says "Accessing Trailers" and stays there. No library or channel content.

15

Hmm I have just seen you have your webserver port as 90, do you have a reverse proxy setup to account for not using port 80?

16

Yes,

Like I told this configuration works with 0.2 version like a charm.

17

Not really sure about the 0.2... but is it possible, that this issue is the one with "//" in the URL? We got to get rid of that...

The thing is, that PlexConnect codes the full PMS URL into aTV's request. With port forwarding it was seen, that the NAS server/forwarded needs typically a special setting to allow those double-"/" in the URL. Do you know about this setting, do you already have it set?

18

Not really sure about the 0.2... but is it possible, that this issue is the one with "//" in the URL? We got to get rid of that...

The thing is, that PlexConnect codes the full PMS URL into aTV's request. With port forwarding it was seen, that the NAS server/forwarded needs typically a special setting to allow those double-"/" in the URL. Do you know about this setting, do you already have it set?

I don't know what settings you are talking about. On ATV or on Linux? Could you be more specific, please.

19

On Linux - and I have no own experience. Based on that, I can't really be more specific, sorry... there should be some hints in the "PlexConnect on Synology" thread. I think, this is where I read about it...

20

See this thread, specifically the bit about the “AllowEncodedSlashes NoDecode” line (this is needed in the later versions of PlexConnect):

https://forums.plex.tv/topic/99876-followed-install-guide-stuck-on-accessing-trailers/?hl=%2Breverse+%2Bproxy#entry586713