Okay guys… my development system took a nose dive a couple of days ago.
After upgrading to El Capitan PlexConnect is kind of non-functional. I again went through the signing procedure for python, double checked the firewall settings… everything seems to be fine.
What I know for sure:
- DNS server is working fine (logs are available, other aTV apps are working fine)
- WebServer (HTTP) works, too: I had no issues re-applying the certs to aTV (after removing them before)
- locally WebServer (HTTPS) works as well - triggering PlexConnect from Safari, and trusting the self-signed certificate, the oputput is as expected.
But then it gets lost…
- basically instantenious after selecting, aTV shows the unfortunate “trailers not available”.
- logs state DNS msgs “intercepting …” followed by - nothing.
It really looks like bad certificates. But then I reloaded them, tried freshly created ones, … only to end in the same, bad spot again. Does anybody know about neccessary changes for cert generation?
As other messages don’t indicate major issues with El Capitan, what am I doing wrong? 

