Problem sorted on the Synology - was down to the change and required entry to my vhosts in Apache. Down to it running on Port:81 perhaps. Added entry as follows to correct (all working now) - my bad for not understanding the impact of the change and reference to DNSServer
Both Synologie? Both using an "own" DNSServer?
Synology uses a virtual host for PlexConnect Webserver because port 80 is already in use, now I have to add an additional vhost reference for atv.plexconnect in the installer (alias for trailers.apple.com)
will need to make a new installer, can do that because it will also work just fine with the 0.1 codebase, and it will allow others to do git pull's to stay up to date
yes... was thinking about an impact along these lines - just too late :-)
It is definitely related to latest 'git pull' because when I restore an old version it works again. Now trying to find out which changed file of PlexConnect causes this issue...
Henri... well those guys already found it. We installed a virtual host called "aTV.PlexConnect". You got to add an forward for this one to - same as "trailers.apple.com".
It is definitely related to latest 'git pull' because when I restore an old version it works again. Now trying to find out which changed file of PlexConnect causes this issue...
Check your web server (Apache?) configs on your Debian setup. You'll need to add forwarding for aTV.PlexConnect or it won't work
I checked the previous GIT commit (6d76aaf85fad66a1bf763e45a94130fba791f793) and indeed detected that biggest change was in *.js file for trailers.apple.com => aTV.PlexConnect. When reversing this change it was working again, so I was sure it was not related to anything else on my Debian Server. Now trying with the latest update again.
Because I am using another port-number (4500) I was already using Proxy. See also my blog (http://eye-vision.homeip.net/1408/plexconnect-en-appletv-met-debian/) where I described all my steps. Now trying to add atv.plexconnect as well to /etc/apache2/sites-enabled/000-default.
When I get it working I will update my blog.
Still struggling :-(.
Because I was using listen-port 4500 for the webserver of PlexConnect I already had a ProxyPass in /etc/apache2/sites-enabled/000-default:
SSLEngine off
ServerName trailers.apple.com
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:4500/
ProxyPassReverse / http://127.0.0.1:4500/
I now thought that just adding an 2nd entry would fix the issue
SSLEngine off
ServerName atv.plexconnect
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:4500/
ProxyPassReverse / http://127.0.0.1:4500/
But this seems somehow not working (I did restart apache2 after this change). Busy sorting this out now.
AAAARRGGHHH, rookie mistake :unsure:
Replace 127.0.0.1 above with real IP-address of Server for ProxyPass and ProxyPassReverse and it works!
I am having the same problems with the Master PlexConnect release running on a Mac with PMS 9.8.4—it works fine with the release before Master. I enclose the Log file—like the above poster, it looks like the the system is running OK, but it just gives the endless Trailers unavailable messages. Something has bugged in the Master release.
Baa, This is not just a Synology issue; it is also affecting my standard Mac setup with both PMS and PlexConnect running on the Mac (log files above). It started as soon as I started using the Master release and it is fixed as soon as i go back to the release before Master. This was not a git pull but a full Master.zip download.
I had this problem to. I managed to get it sorted though using the following settings.
[PlexConnect] logpath = . enable_dnsserver = True ip_webserver = 127.0.0.1 prevent_atv_update = True enable_plexconnect_autodetect = True port_pms = 32400 port_webserver = 9999 ip_plexconnect = 0.0.0.0 ip_dnsmaster = 10.0.1.1 loglevel = Normal ip_pms = 10.0.1.4 enable_plexgdm = True
server {
listen 80;
listen [::]:80;
server_name trailers.apple.com atv.plexconnect;
location / {
proxy_pass http://127.0.0.1:9999;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
}
Baa, This is not just a Synology issue; it is also affecting my standard Mac setup with both PMS and PlexConnect running on the Mac (log files above). It started as soon as I started using the Master release and it is fixed as soon as i go back to the release before Master. This was not a git pull but a full Master.zip download.
I know that it is not depending on Synology... but those installations usually "do something different". Like having an own DNSServer, running an own WebServer with port forwarding and stuff.
Do you use just the stock setup? Any changes to settings.cfg?
>>19:34:36 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.0.15
DNSServer is catching the new host "atv.plexconnect". It might be a bad naming, maybe plexconnect.local would have been better. But I guess we will stick to it :-)
>>19:35:30 DNSServer: Domain: trailers.apple.com
Thanks Baa for the suggestions. Restarted everything (Mac, Apple TV2, hubs and router) and now it seems to be working again.
@Henri
Why not add o e simple line to the existing trailers vhost?
ServerAlias atv.plexconnect
Keeps the setup simpler…
@rippiedoos
Yeah you are right. Next is much easier and better maintainable (in example below I have webserver port on 4500):
SSLEngine off
ServerName trailers.apple.com
ServerAlias atv.plexconnect
ProxyPreserveHost On
ProxyPass / http://your.server.name.or.ip:4500/
ProxyPassReverse / http://your.server.name.or.ip:4500/
The other one (2 blocks) worked as well though -_- ...
I am experiencing the same issue.
I had PlexConnect working fine until I pulled the update today. Am I to understand this all centers around the need for new VirtualHost records for atv.plexconnect? I have set up OSX Server to serve up atv.plexconnect in the same fashion as trailers.apple.com but it's still not working.
For now I will just use the build from a few weeks back, as that seems to work just fine.
FYI: A full rundown of my setup and settings is detailed here: http://forums.plexapp.com/index.php/topic/71085-a-guide-to-how-i-got-plexconnect-running-on-os-x-server-107/?p=446045
Try changing the following in settings.cfg:
enable_plexgdm = False
ip_dnsmaster = change this to your ISP's DNS server (use google to find)
ip_pms = 192.168.0.3
If that does not work post another log please.
Settings.cfg -> not a PMS file, but from PlexConnect. Should be in that folder, too.
Hi. I'm having the same issue. I'm using PlexConnect for web and dns. Have tried the changes to Settings.cfg suggested here. Port 80 from a different computer gives
Error responseError code 403.
Message: Not Serving Client 10.0.1.9.
Error code explanation: 403 = Request forbidden – authorization will not help.
The Trailers app gives "Trailers is unavailable. Try again later." immediately. From log:
19:17:25 DNSServer: DNS request received!
19:17:25 DNSServer: Source: ('10.0.1.5', 65516)
19:17:25 DNSServer: Domain: trailers.apple.com
19:17:25 DNSServer: ***intercept request
19:17:25 DNSServer: -> DNS response: 10.0.1.103
All IP's are correct. PMS and PlexConnect.py is running on Ubuntu 13.04 (GNU/Linux 3.8.0-19-generic x86_64) server with bind9 uninstalled. It was working, but after a few reboots and playing around with some settings for the PMS and adding some channels manually and through PMS it stopped working. Any Ideas?
EDIT: I have 3 PMS on my network - this worked fine before. I have tried removing the two I changed some stuff on, but with no success.
