wahlman, I did just that but it's still not working. Here's what I did.
installed the latest plexconnect onto my macbook pro using the git method, created the required certificates and copied those into the assets/certificates folder. Then I ran plexconnect throgh terminal.app. I then started up my ATV and went into the DNS settings and changed it to point at my plexconnect which is running on my macbook pro. Upon Launching the trailers app, it constantly spins and leaves me with a final message saying trailers unavailable.
The ATV3 was already working with PlexConnect (in the Synology) ? If yes, it's easier to copy the trailers files (key / pem / cer) from the Syno to the Mac. This way the ATV3 will work in your friend's house (pointing to the Syno) or at your new house (with DNS parametrized to point to your Mac).
I have no experience of using MyPlex to access remote PMS based in Syno boxes. I think that this may imply that the Syno will have to transcode, and in this case you will run into another set of problems. My advise is to first complete the PlexConnect installation in the Mac using the certs from the Syno (instead of creating new ones), see if everything works (in local), meaning by this that PlexConnect in the Mac has to find PMS in the local LAN, and then try using MyPlex (instead of local libraries) to see if it goes well. If not, probably you will have to setup a VPN between your Mac and the Syno (not very difficult, you may use OpenVPN on both sides, in the Syno you have a the VPN package that can generate the Openvpn files and certs) so that PMS "thinks" that PlexConnect is local (instead of remote).
In summary:
- One PMS running in the Syno
- One PlexConnect running in the same Syno
- One ATV3 whose DNS is pointing to #2 above, using the certs loaded in the Syno
- One PlexConnect running in the Mac, whose Settings.cfg file indicated the IP address of the Syno, with GDM disabled, and the certs copied from the Syno
- A 2nd ATV3 whose DNS is pointing to #4 above, using the certs loaded in the Syno
- VPN package installed in the Syno (with OpenVPN enabled) -> in your friend's house you will have to assign (in the router) UDP port 1194 pointing to the Syno
- "OpenVPN client" installed in your Mac (using the OpenVPN certs generated by the Syno) + a valid userid/password in the Syno
Steps #6 and #7 are only necessary if you run into "transcoding problems" with MyPlex.
You can setup a VPN and go thru all that it you wish. In the end you still will need a 1 VPN host and client which would be more difficult to setup then just using myplex and require more bandwidth on both ends. You can use the same cert only if you are running a VPN, opening ports (unsafe), or if you use a new plexconnect host at the new site with the old cert. If it was me I would just sign up for a additional user at the site listed below to reduce bandwidth and setup time, install a new plexconnect host on the Mac, use the same or create new certs on the host/atv, but it’s your time and do as you wish. Your cannot connect to your other plexconnect host over the internet without using a VPN or opening ports which would more then likely require a new plexconnect host anyways. Myplex still is the most efficient to setup and requires the least amount if bandwidth and memory on both ends compared to a VPN since you can just sign into myplex on the atv assuming you setup myplex on pms at the old site properly.
Http://plex.tv
Myplex still is the most efficient to setup and requires the least amount if bandwidth and memory on both ends compared to a VPN since you can just sign into myplex on the atv assuming you setup myplex on pms at the old site properly.
I agree, but if it implies transcoding on the PMS side, the Syno may not be able to transcode at all, so the user will not see any content in the remote ATV. Creating a VPN will of course require higher bandwith, otherwise the ATV3 may suffer from lags. That's one important point to consider.
Regarding security, creating a VPN between the Mac (where "PlexConnect remote" is running) and the Syno (where "PMS local" is running) does not seems a significant security risk to me. Syno makes available to their users a number of "blocking techniques" that prevent most attacks, such as permanently disabling IP's that fail the same userid/pw combination twice during a 10 hour period, or allowing just a tiny range of IP's to access the VPN.
MyPlex requires that port 32400 is open to the world... In the end I don't know what's more insecure, if opening port 32400 or port 1194...
@moody_blue, the synology NAS transcode just fine. I am using the 1512+ and it works well with when I am accessing my media remotely on my Mac, iPad or iPhone. No Problems there. Okay what I did was took back my ATV3 back to my friends house, hooked it up, launched the trailers app and went into the Plexconnect settings tab and logged into myplex (this wasn't filled out previously). So now I'm gonna disconnect the ATV3 now and take it back to my house and hook it up again to see if it will finally work.
Okay I ssh'd into the NAS and there are nothing in the assets/certificates folder. Only 1 file called certificates.txt. Do I need to copy the 2 files (.cer and .pem) from my macbook pro to this folder? I never had certificates in this folder and everything has always worked fine. And why do I need 2 ATV? I only have 1.
You only need 1 'apple tv 3'. You need your old certs in the certificates folder. Once in place restart or stop/start plexconnect.
@ Moody_blue I think a VPN would offer decent security. I was talking about opening wan ports such as 53, 80, 443 which would be very bad security wise.
Okay I ssh'd into the NAS and there are nothing in the assets/certificates folder.
The certificates are in /usr/local/plexconnect/etc/certificates/. You need to copy them to your Mac, and then restart PlexConnect in the Mac. As there is no ATV in your friend's house you can also stop PlexConnect in the Syno.
If you used bwynants's certificates (instead of creating your own ones in the Syno), you can unzip the Synology installer (using WINRAR, TAR or equivalent), where you will find another tar file, inside which there is an "etc/certificates" folder with the certs.
