I just don't understand how this isn't working. I have tried re-doing this whole installation process half a dozen times, and it simply isn't working. Plex Media Server works fine, but Plexconnect doesn't :(
Thanks for all those who have tried to help, but it looks like I am stuck air playing from the iPad for now :(
I have a $10 tip/donation waiting in my paypal for anyone who can solve this.
Just tried re-installing Plex Media Server, even killed my meta data cache just to make sure it wasn't a strange setting I have saved on my PMS setup.... it's currently re-downloading 4 gig og meta data :( And still nothing. Re-installed Python. Nothing. Re-generated a cert. Nothing. Tried using older versions of Plexconnect. Nothing. Although the 0.1 version makes the ATV hang on the finding trailers app screen for about a minute...the newer versions all go straight to a error in the title.
I've actually run out of ideas of things that I could have done wrong. It just doesn't work.
I would think it is likely cert or firewall related.
Add an INBOUND rule for both TCP and UDP for Python.exe in your firewall.
0.1 doesn't work any more, it is pre-https stuff.
Do you have a second computer on hand?
Take a browser, set it into developer mode, edit the UserAgent to contain "AppleTV" and browser to
http:///js/application.js
https:///js/application.js
What are the responses you are getting - should be the main js file, not the 403 error.
I tried DMZ'ing the ip that Plex connect is on to eliminate the possibility that it was a firewall issue. And I still had the issue.
When i use my laptop to browse with AppleTV as the user agent I can see the application.js files both in http and in https. It renders the code of the JS files and not he 403 error.
I tried DMZ'ing the ip that Plex connect is on to eliminate the possibility that it was a firewall issue. And I still had the issue.
When i use my laptop to browse with AppleTV as the user agent I can see the application.js files both in http and in https. It renders the code of the JS files and not he 403 error.
Make sure you remove that from the DMZ, you do not want the DNS server part exposed to the world.
Just tried re-installing Plex Media Server, even killed my meta data cache just to make sure it wasn't a strange setting I have saved on my PMS setup.... it's currently re-downloading 4 gig og meta data :( And still nothing. Re-installed Python. Nothing. Re-generated a cert. Nothing. Tried using older versions of Plexconnect. Nothing. Although the 0.1 version makes the ATV hang on the finding trailers app screen for about a minute...the newer versions all go straight to a error in the title.
I've actually run out of ideas of things that I could have done wrong. It just doesn't work.
If you generated new certs ensure you delete the profile on the ATV before installing the new one or it will not work.
If you generated new certs ensure you delete the profile on the ATV before installing the new one or it will not work.
Yes, I have been removing and adding the profile each time I make a change.
I tried DMZ'ing the ip that Plex connect is on to eliminate the possibility that it was a firewall issue. And I still had the issue.
When i use my laptop to browse with AppleTV as the user agent I can see the application.js files both in http and in https. It renders the code of the JS files and not he 403 error.
Well, that says Windows is NOT blocking those addresses. Right.
Question: Did you ever do a reboot or something to aTV after installing the cert? I have no idea at which point aTV starts using it... but the last log I saw is -> serving cert directly followed by -> entering trailers.
Well, that says Windows is NOT blocking those addresses. Right.
Yeah totally, so why isn't it working on the Apple TV ? :(
Question: Did you ever do a reboot or something to aTV after installing the cert? I have no idea at which point aTV starts using it... but the last log I saw is -> serving cert directly followed by -> entering trailers.
I often throw in a reboot every now again, just to check. Tried again just now. Still no luck :(
Hm... PM me your latest cert files. I will check if I get them to work on my machines... if not most likely there is something wrong with your generation process...
-> https://forums.plex.tv/topic/94044-trailers-is-unavailable-try-again-later-error/?p=548532
Did you have issues installing openssl?
-> https://forums.plex.tv/topic/94044-trailers-is-unavailable-try-again-later-error/?p=548532
Did you have issues installing openssl?
No, I didn't, although, I used the 32 bit version on my 64 bit machine.
So I just uninstalled it, installed the 64 bit version and made some new certs. Copied them into the assets folder, removed the old profile, added it again, restarted everything. Tried again, very hopeful this time, and nothing..again.
I seem to have the same issue as Pingable.
PlexConnect was working great for a couple of weeks and then about 4-5 days ago it just quit.
I've redone the entire process but still end up with the same result....Spinning Wheel that says "Accessing Trailers"....
I'm also running Apple TV3 6.02
New PlexConnect
New Plex Media Server
New Python
New Certificates
New Settings.cfg
I can post this into the Official Format later tonight, but just wanted to let everyone know that Pingable isn't alone with this issue.
Thanks for ever ones assistance in trying to solve.
Solved. Thank you Baa for all your help, and anyone else who has tried to help. For me it turned out to be the path to the cert in the config file. It needed to be in full, and in windows format, with slashes the correct direction and having no strange characters in the folder path (Dashes, spaces etc)....I had it as Plexconnect-master and the .\assets\ etc format.
C:\PlexConnect\assets\certificates railers.pem
