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 馃檪
Thank you James :) Here is the screenshot of my console errors. I couldn't find the "api/v1/sessions" response.
I'm getting the same issue. In my docker logs, I'm seeing this:
nginx_1 | nginx.1 | dsa-la-lsc.org 173.244.48.9 - - [10/Jun/2018:15:12:44 +0000] "GET /cable HTTP/1.1" 101 4 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0"
nginx_1 | nginx.1 | dsa-la-lsc.org 173.244.48.9 - - [10/Jun/2018:15:12:45 +0000] "POST /ahoy/events HTTP/2.0" 200 28 "https://dsa-la-lsc.org/dashboard" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0"
nginx_1 | nginx.1 | 2018/06/10 15:12:46 [error] 47#47: *334 connect() failed (111: Connection refused) while connecting to upstream, client: 173.244.48.9, server: dsa-la-lsc.org, request: "GET /service-worker.js?1.8.564 HTTP/2.0", upstream: "http://172.17.0.5:3000/service-worker.js?1.8.564", host: "dsa-la-lsc.org"
nginx_1 | nginx.1 | 2018/06/10 15:12:46 [warn] 47#47: *334 upstream server temporarily disabled while connecting to upstream, client: 173.244.48.9, server: dsa-la-lsc.org, request: "GET /service-worker.js?1.8.564 HTTP/2.0", upstream: "http://172.17.0.5:3000/service-worker.js?1.8.564", host: "dsa-la-lsc.org"
nginx_1 | nginx.1 | dsa-la-lsc.org 173.244.48.9 - - [10/Jun/2018:15:12:46 +0000] "GET /service-worker.js?1.8.564 HTTP/2.0" 304 0 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0"
No errors in the console or any 400/500 statuses on the network tab.
Usually this is because the rails server can't send emails, but I can't see that error in your logs. Is that all the revevant logs? Maybe post the full thing via a text attachment or pastebin like service?
Can you check the configuration of your SMTP settings?
Hey Robert, thanks for the tips. I've been playing aroun for a couple hours now with no luck. Here are my raw logs (with one attempt at creating an account at the end) https://pastebin.com/usqqm1ba
And here is my env file with all the important stuff removed https://pastebin.com/ejSqFFcS
Hope this leads to a solution, I'm super excited to get loomio up and running!
Hrrm. I don't see any information about critical failures in those logs. I would have expected the loomio_1 container to have a connection refused error.
please try:
docker-compose run loomio rails c
to start a rails console
then run
u = User.create(email: "enteryouremail@here.com")
UserMailer.login(user: u, token: u.login_tokens.create).deliver
and paste the result in here.
Here's the output: https://pastebin.com/wRGFmb7i
Didn't receive an email, so I imagine something's wrong with my smtp settings, but I don't know what
It does seem like it's a problem with your SMTP settings. Can you view logs on that service?
Yes I can, and there are a lot of juicy errors in there. https://pastebin.com/K6RCKKr4
They all seem to do with spamd?
I think that's the wrong pastebin link
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.
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!
I got it working for my case. At mine it was a proxy removing all cookies on the transit to loomio server.
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?
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.
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.
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!
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)
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?
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.
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 :)
Please do make a PR on the docs. That would be great.

There should be an error in your javascript console (available by selecting 'Console' from the dev tools in the browser); could you screenshot that here? It may also be useful to know what the response of the
/api/v1/sessionscall was in the 'Network' tab.