Comment 4 for bug 1820381

Ok. You should have skipped the --with-websockets-port option if you're not using a proxy. I'd try running configure again without that option, doing make, make install, and the chown steps of the instructions. Then restarting OpenSRF services, apache2, and websockets. (This part of the README may not be very clear. Others have had similar issues.)

Also, I think part of the problem is pointing the browser at "private.localhost." You should try "localhost" instead, and even better, you should try with a browser on a machine other than the one that is running Evergreen.

Even though websocketd listens on all addresses by default, it may not know about private.localhost nor public.localhost. These addresses are special and meant to be used only by the private and public OpenSRF routers respectively. They're not meant to be visible to the world.

Finally, Python isn't going to work with OpenSRF/Evergreen on Ubuntu Xenial. This isn't documented and we may or may not have a bug about it, but Evergreen's Python is broken on Ubuntu Xenial and Debian Jessie(?) because of an apparent bug in a Python XMPP module. There may also not be a bug for that module, either. As far as I know, I'm the only one to encounter it. There has been some chatter about it in IRC or on the development mailing list. One way to test if Python is going to work or not is to start srfsh.py. It should error out on Ubuntu Xenial.