Improved Fallback for the no-service case

We will want better support if the machine doesn't have the localproxy service installed. As of now, if there is no localproxy service installed, we can't start the app (or perhaps it just silently fails? not sure). Can we detect if the localproxy service is not installed and instead spin up our own port 80 server in nodeland and do some forwarding?