This was perfect. I was thinking about writing a how to on the FreeNas forums for installing plexconnect. Would you guys mind if I used some sections of your posts (with referencing of course)?
Yeah you can. I was about to write one myself.
This was perfect. I was thinking about writing a how to on the FreeNas forums for installing plexconnect. Would you guys mind if I used some sections of your posts (with referencing of course)?
Even better if you write one that I can put on the wiki and you can link to on the FreeNAS forum (that way we can try and keep the link always up to date).
Even better if you write one that I can put on the wiki and you can link to on the FreeNAS forum (that way we can try and keep the link always up to date).
I posted the Guide here
http://forums.freenas.org/threads/how-to-install-plexconnect-for-atv.18315/
I posted the Guide here
http://forums.freenas.org/threads/how-to-install-plexconnect-for-atv.18315/
That's perfect but the one thing I would change (and the reason why I was going to write it) was to change pkg_add to pkg install. Pkg_add is not recommended to use as per FreeNAS documentation.
Thanks for posting it!
Hey guys!
I'm running FreeNAS-9.1.1-RELEASE-x64 (a752d35). Installed PMS in jailid Plex_2.
I got everything running flawlessly until I rebooted my server today.
I ran Jexec Plex_2 csh.
cd PlexConnect/
Hey guys!
I'm running FreeNAS-9.1.1-RELEASE-x64 (a752d35). Installed PMS in jailid Plex_2.
I got everything running flawlessly until I rebooted my server today.
I ran Jexec Plex_2 csh.
cd PlexConnect/
bash /PlexConnect/PlexConnect_daemon.bash startThen I get the following error:Shared object "libintl.so.9" not found, required by "bash"I've tried the following for the bash shell:Make DeinstallMake Install CleanBut I still get the "Shared object "libintl.so.9" not found, required by "bash"" error...Can someone please help?
Made a factory reset and now everything is working great!
Thanks to the guide by Ole Norway I got PlexConnect installed on my freeness 9.2.1. Unfortunately something with the PMS ip does not work properly. My freenas is running with the ip address 192.168.178.2 and PlexConnect runs with this ip address as well. I changed the Settings.cfg according to the guide:
enable_plexgdm = False ip_pms = 192.168.178.3
But the plexconnect dns server delivers 192.168.178.2 instead of the ip_pms set in the Settings.cfg file? How can this be the case? Any ideas?
[PlexConnect] enable_plexgdm = False ip_pms = 192.168.178.3 port_pms = 32400 enable_dnsserver = True port_dnsserver = 53 ip_dnsmaster = 8.8.8.8 prevent_atv_update = True enable_plexconnect_autodetect = True ip_plexconnect = 192.168.178.5 hosttointercept = trailers.apple.com port_webserver = 8080 enable_webserver_ssl = True port_ssl = 443 certfile = ./assets/certificates/trailers.pem loglevel = Normal logpath = .
This is my whole config file.
EDIT: I tried to run plexconnect in a separate jail, after installing it in the jail of the pas everything works fine!
Removed - Wrong spot to post
Issues setting up PlexConnect on FreeNAS after pulling code via git
root@plexconnect_1:/ # pkg update
root@plexconnect_1:/ # pkg upgrade
root@plexconnect_1:/mnt/PlexConnect # git pull
You will have to change the paths of the shebang in PlexConnect.py by:
- Determine where python is locatedwhereis python
python: /usr/local/bin/python
vi PlexConnect.py
change the path in the first line to the output of whereis, or
change it to: #!/usr/bin/env pythonescape-key :wq! (to save)
./PlexConnect.py
Should work now
Issues setting up PlexConnect on FreeNAS after pulling code via git
root@plexconnect_1:/ # pkg update
root@plexconnect_1:/ # pkg upgrade
root@plexconnect_1:/ # cd mnt/root@plexconnect_1:/mnt # git clone https://github.com/iBaa/PlexConnect.gitroot@plexconnect_1:/mnt/PlexConnect # git pull
root@plexconnect_1:/mnt/PlexConnect # ./PlexConnect.pyenv: python: No such file or directoryAny suggestions?
Have you installed Python27 as it says in the guide?
pkg_add -v -r python27
pkg_add -v -r bash
pkg_add -v -r nano
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.