Comment 1 for bug 1820381

Hi, Edwin.

This sounds more like a question than a bug, so I have a couple of questions for you:

1. Did you install either websocketd or apache2-websocket and it it running as required?
2. Is there a firewall preventing you from communicating with port 7632 which is the standard port that our instructions give for setting up the websocket listener?
3. If you followed the proxy instructions have you triple checked that the proxy is configured correctly?

One of the classic causes for login failures such as you describe is a failure to communicate with the websocket listener.

It would be helpful if you can open the developer tools in your browser, switch to the console, and paste the contents of any error messages that appear when you attempt to login.

Jason