OK, so I'm trying to get this set up on my OpenWRT router. Everything APPEARS to be working correctly. I can even see that the ATV is connecting to the PlexConnect software. The problem is that I'm still getting the "Trailers Unavailable" message.
I've tried increasing my log level but it hasn't given me any additional information.
Again, everything is connecting, just not moving forward. I JUST downloaded the PlexConnect code so I don't think that's the problem. I can also see that the certificate is installed on the ATV.
I read a small post where someone mentioned that the SSL certs need to be cut on the machine that will be using them. Is this true? If so, it could be my problem as I cut the certs on my Mac and then uploaded them to the router.
>> I can also see that the certificate is installed on the ATV.
In the attached log? I can't...
I can't see any message of/for the DNSServer. Did you set up your own? Did you install "trailers.apple.com" as well as "aTV.PlexConnect" as hosts to reroute?
>> I can also see that the certificate is installed on the ATV.
In the attached log? I can't...
I can't see any message of/for the DNSServer. Did you set up your own? Did you install "trailers.apple.com" as well as "aTV.PlexConnect" as hosts to reroute?
Thanks for the response. I used the DNS server on the router. I set up trailers.apple.com (which is how it's finding the Connect instance in the first place) but I didn't do aTV.PlexConnect. Can you be more specific?
In the attempt to reduce the use of "trailer" throughout PlexConnect, we implemented a new virtual host: atv.plexconnect.
trailers is now ONLY used for accessing application.js, everything else is living in atv.plexconnect. You have to add a that new host along with trailers, pointing to the same machine.
In the attempt to reduce the use of "trailer" throughout PlexConnect, we implemented a new virtual host: atv.plexconnect.
trailers is now ONLY used for accessing application.js, everything else is living in atv.plexconnect. You have to add a that new host along with trailers, pointing to the same machine.
Ah, a second host! Ok, I'll try that when I get home.
Did I miss that in the wiki? I really tried to solve this on my own.
So, there's still a problem and I have no idea what it could be. Is there a way to try to narrow it down? Pieces I can remove to see what's working and what's not?
Is there a way to confirm that the machine (router) can access the Plex Server? Perhaps Plex is blocking it?
It is either an issue with your DNS or the certificate.
For testing... Use the PlexConnect DNS, point aTV DNS to it, and go from there (once you have it running, you can always cut corners and use your own DNS). If this fails the same way, redo your certificate stuff.
In the attempt to reduce the use of "trailer" throughout PlexConnect, we implemented a new virtual host: atv.plexconnect.
trailers is now ONLY used for accessing application.js, everything else is living in atv.plexconnect. You have to add a that new host along with trailers, pointing to the same machine.
* beats head on desk *
When did you guys introduce that? Hopefully it explains why recently I get as far as "serving application.js" but the ATV2 says "trailers unavailable". I'm using dnsmasq on OpenWRT to handle my own DNS rewriting as I wanted to limit the re-write to just my ATV2 (although I may never have got that part working...)
A lot of people are generating bad certs. The site was updated today. Try to delete your old certs and install your new certs. Plexconnect should not shutdown, obviously.
Rather than hijacking a thread how about starting your own with all the information as specified in the pinned read before posting thread and associated wiki page on how to report an issue.
This information is what helps the community and developers to help you