plexconnect -getting it to work with nginx?

jmterry · 26. März 2015

I have tried to follow a previous user here to get plexconnect to work so that I can use my appleTV v3 to view plex but I am confused. I basically modified the listed code with my ip(s) and paths in attempt, but I believe I got myself lost. Can someone tell me how to query via CLI what programs are running? I followed the post all the way to attempting to get plexconnect to start up as a daemon. All of the supported plugins work I just cannot get this little app that allows ATV viewing to work.

I changed the web interface for OMV to be viewed at port :8085 so that (as I understand it) the ATV can connect to the PMS on port 80 because this can't be changed short of creating an ip table in omv's firewall or perhaps a trigger set up in my router? I understand the basics but I think I am getting wrapped up in the details.

I went ahead and tried to change the dns server and certificate in the ATV, but ATV cannot find my cert. I changed the path in the settings.cnfg to point to where I have the cert, but I think I am missing something that allows the ATV to connect. When I try to use: "service plexconnect start" as ultimately the code for the created daemon should let me do, I do not receive any echoed response. I cannot remember the command that allows one to see all the running processes, so I am really not certain I have PlexConnect running. Will someone please post that command? And or help me figure out where I have gone wrong?

~jt~

jmterry · 26. März 2015

Here is the code I have in my init.d file for plexconnect

Bash

#!/bin/bash
### BEGIN INIT INFO
# Provides:          plexconnect
# Required-Start:    plexmediaserver networking
# Required-Stop:     plexmediaserver networking
# Default-Start:     3 4 5
# Default-Stop:      0 1 6
# Short-Description: This is the Plex Connect daemon
# Description:       This script starts the Plex Connect
#                    Python scripts in a detached screen.
### END INIT INFO
# Using the lsb functions to perform the operations.
. /lib/lsb/init-functions
# Process name ( For display )
NAME=PlexConnect
# Daemon name, where is the actual executable
DAEMON="/usr/bin/screen"
DAEMON_OPTS="-S PlexConnect -d -m /home/PlexConnect/PlexConnect.py"
DAEMON_USER="root"
# pid file for the daemon
PIDFILE=/var/run/PlexConnect.pid
# If the daemon is not there, then exit.
test -x "$DAEMON" || exit 5
case $1 in
 start)
  # Checked the PID file exists and check the actual status of process
  if [ -e $PIDFILE ]; then
   status_of_proc -p $PIDFILE "$DAEMON $DAEMON_OPTS" "$NAME process" && status="0" || status="$?"
   # If the status is SUCCESS then don't need to start again.
   if [ $? = "0" ]; then
    log_success_msg "Starting the process $NAME"
    exit # Exit
   fi
  fi
  # Start the daemon.
  # Start the daemon with the help of start-stop-daemon
  # Log the message appropriately
  if start-stop-daemon --start --quiet --oknodo --pidfile $PIDFILE --startas $DAEMON -p $PIDFILE -- ${DAEMON_OPTS}; then
   while read line ; do [[ $line =~ ([0-9]*).PlexConnect ]] && echo ${BASH_REMATCH[1]} ; done < <(screen -ls) > $PIDFILE
   log_success_msg "Starting the process $NAME"
  else
   log_failure_msg "Starting the process $NAME"
  fi
  ;;
 stop)
  # Stop the daemon.
  if [ -e $PIDFILE ]; then
   status_of_proc -p $PIDFILE "$DAEMON DAEMON_OPTS" "Stoppping the $NAME process" && status="0" || status="$?"
   if [ "$?" = 0 ]; then
    start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE
    /bin/rm -rf $PIDFILE
    log_success_msg ""Stopping the $NAME process""
   fi
  else
   log_failure_msg "$NAME process is not running"
  fi
  ;;
 restart)
  # Restart the daemon.
  $0 stop && sleep 2 && $0 start
  ;;
 status)
  # Check the status of the process.
  if [ -e $PIDFILE ]; then
   status_of_proc -p $PIDFILE "$DAEMON $DAEMON_OPTS" "$NAME process" && exit 0 || exit $?
   log_success_msg "$NAME process is running"
  else
   log_failure_msg "$NAME process is not running"
  fi
  ;;
 reload)

Alles anzeigen

subzero79 · 26. März 2015

In the diagnostics section you can check system information for running process. I was in that thread for nginx (which i found to be totatly unnecessary).

You don't need to change port 80 in the webUI. You can set a specific iptables rule to redirect incomming traffic from atv3 ip to omv ports 80 and 443 to other ports (the ones in plexconnect settings). The rule is published in the forum, just use google not the forum engine.

For installing the certificate (can't remember the exact procedure) but it was just to start a simple web server in the folder were you have the certificates and with atv interface point to that address to install them.

python -m SimpleHTTPServer

subzero79 · 26. März 2015

PlexConnect port conflict

Just firing this rules in terminal make the port redirection work, but they are not reboot persistant. As a fast solution you can put them at /etc/rc.local file before the exit line to make them reboot persistant.

jmterry · 26. März 2015

I found the rule here -thanks subzero... I will try this. I may need to move the certs or generate new ones but this is good. Even if I need to reapply the rule after reboot. I'll just leave myself a note as I do run 24/7.

subzero79 · 26. März 2015

Also put order in your router so your wireless or wired devices have always the same ip address. DHCP reservation not static ips

If the atv changes it's ip the rule wont do any effect for plexconnect to work

jmterry · 26. März 2015

thanks. I have done this for omv box and my often used MacBook Pro, but not yet for this new ATV. I'll do that next.

plexconnect -getting it to work with nginx?

Jetzt mitmachen!

Tags