Login Issues: After asking Email and Name, app just hangs...
I was sure to save the email and password presented at the end of installation. But when I type that email address in, and then my name at the next prompt, the app just hangs and goes nowhere: doesn't log me in, doesn't shut me out.
I had no issues during installation.
I'm running Loomio on OSX.
Thanks for your help :slight_smile:
Simon DittlmannSun 25 Nov 2018 11:39AM
Hi everyone, hi @alexcoopalim , I issue the exact same errors. Have you been lucky to get it working after all? May you be so kind and share your solution if existing? Thank you in advance!
Simon DittlmannMon 26 Nov 2018 9:52AM
I got it working for my case. At mine it was a proxy removing all cookies on the transit to loomio server.
Tyler SchlichenmeyerThu 10 Jan 2019 11:51AM
So, I'm gathering from the OP that i must have missed a default email i am supposed to use for my local instance (i cant move past the initial authentication). Anywhere to recover said email, or is the process different at this point?
Robert GuthrieFri 11 Jan 2019 4:50AM
Just create a new account the way any new user would. There is no default email/user account. You can then rails c into the server and User.find_by(email: "your@email.com").update(is_admin: 1) to get admin privileges.
Hope that helps.
Tyler SchlichenmeyerFri 11 Jan 2019 5:28AM
Hi Robert, thanks for the tip. Tried this, got a successful update, but trying to log in again I am still stuck on this screen:
Obviously, I am not receiving an email, and I don't see any other routes of logging in.
Tyler SchlichenmeyerFri 11 Jan 2019 5:57AM
PS my apologies if the solution to this is a simple workaround in rails, I am still learning the framework but am trying to get a baseline sandbox to start out with!
Robert GuthrieFri 11 Jan 2019 6:48AM
Oh no!
Have you configured your SMTP settings in your env file?
You should see errors in your logs. (run docker-compose logs to see)
Tyler SchlichenmeyerFri 11 Jan 2019 7:06AM
Sorry, I should have clarified: I followed the local dev setup instructions (not the docker deploy) which did not contain any references about spinning up through docker or about SMTP. I guess i should look into setting up an SMTP in a local install? Or is there a container i can use locally? Or other workaround?
Robert GuthrieFri 11 Jan 2019 8:32AM
Oh, brilliant!
On localhost you can access dev urls like:
http://localhost:3000/dev/setup_group
whichv creates a testing group and logs you in.
There is a complete list of development routes here:
http://localhost:3000/dev/
Warning: It's a new person trap to forget the trailing slash when entering these urls, if you do this, you'll find that the links just 404.
Tyler SchlichenmeyerFri 11 Jan 2019 9:04AM
Thanks SO much!!! Question: Is this common RoR/web dev practice, or is it in the documentation somewhere I'm missing?? Might be a good idea to include on the setup page! Let me know if i should set up a PR on the documentation :)
Robert GuthrieFri 11 Jan 2019 9:18AM
Please do make a PR on the docs. That would be great.

alex coopalim ·Fri 15 Jun 2018 11:27AM
Hi, I think we have the same issue here. Trying to follow the (quite simple) instructions from https://github.com/loomio/loomio-deploy/ (feeling silly ... :| ).
We have no error server side except the following which appears regulary :
loomio_1 | Started GET "/cable" for XXX at 2018-06-15 11:11:02 +0000
loomio_1 | Started GET "/cable/" [WebSocket] for XXX at 2018-06-15 11:11:02 +0000
loomio_1 | Successfully upgraded to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: upgrade, HTTP_UPGRADE: websocket)
loomio_1 | An unauthorized connection attempt was rejected
loomio_1 | Failed to upgrade to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: upgrade, HTTP_UPGRADE: websocket)
loomio_1 | Finished "/cable/" [WebSocket] for XXX at 2018-06-15 11:11:02 +0000
loomio_1 | Finished "/cable/" [WebSocket] for XXX at 2018-06-15 11:11:02 +0000
Clicking the "create account" button triggers a POST to /ahoy/events wich responds '{}' and nothing else appears anywhere, server side or client side.
N.B. : at the first time we visit the website, we have an error (Cf. attached file) but I think this could normal as we have no account for now.
Thank you.