Loomio
Mon 30 Oct 2017 4:07PM

Installation issue - blank page - nginx upstream error

DU Jose Simoes Public Seen by 467

Hi!
I've installed the latest version of loomio-deploy on a fresh Digital Ocean Ubuntu 17.04 x64 droplet, following all steps in the guide.

The installation completes, but I can't access the page. Firefox renders a blank page, with no content, and chrome gives me an http "421 824245dfe7f9 You talk too soon" message only.

My log for a single request:

loomio_1 | Started GET "/" for x.x.x.x at 2017-10-30 16:01:22 +0000
loomio_1 | Processing by RootController#index as HTML
loomio_1 | Redirected to https://loomio.appning.org/dashboard
loomio_1 | Completed 302 Found in 293ms (ActiveRecord: 0.0ms)
nginx_1 | nginx.1 | loomio.appning.org x.x.x.x - - [30/Oct/2017:16:01:23 +0000] "GET / HTTP/2.0" 302 112 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0"
nginx_1 | nginx.1 | 2017/10/30 16:01:23 [error] 52#52: *23 connect() failed (111: Connection refused) while connecting to upstream, client: x.x.x.x, server: loomio.appning.org, request: "GET /dashboard HTTP/2.0", upstream: "http://172.17.0.5:3000/dashboard", host: "loomio.appning.org"
nginx_1 | nginx.1 | 2017/10/30 16:01:23 [warn] 52#52: *23 upstream server temporarily disabled while connecting to upstream, client: x.x.x.x, server: loomio.appning.org, request: "GET /dashboard HTTP/2.0", upstream: "http://172.17.0.5:3000/dashboard", host: "loomio.appning.org"
nginx_1 | nginx.1 | 2017/10/30 16:01:23 [error] 52#52: *23 upstream sent no valid HTTP/1.0 header while reading response header from upstream, client: x.x.x.x, server: loomio.appning.org, request: "GET /dashboard HTTP/2.0", upstream: "http://172.17.0.6:25/dashboard", host: "loomio.appning.org"
nginx_1 | nginx.1 | loomio.appning.org x.x.x.x - - [30/Oct/2017:16:01:23 +0000] "GET /dashboard HTTP/2.0" 009 36 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0"

This is the second time i deploy loomio on this instance - the first time I thought I had screwed up, so I rebuilt the droplet and started again.

Any help? I have some urgency in solving this issue and no ideas on what to do. Thanks!

DU

Jose Simoes Mon 30 Oct 2017 4:09PM

A previous request rendered the following (different) output - note the upstream error:

loomio_1 | Started GET "/" for x.x.x.x at 2017-10-30 16:00:47 +0000
loomio_1 | Processing by RootController#index as HTML
loomio_1 | Redirected to https://loomio.appning.org/dashboard
loomio_1 | Completed 302 Found in 56ms (ActiveRecord: 0.0ms)
nginx_1 | nginx.1 | loomio.appning.org x.x.x.x - - [30/Oct/2017:16:00:47 +0000] "GET / HTTP/2.0" 302 112 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0"
nginx_1 | nginx.1 | 2017/10/30 16:00:47 [error] 52#52: *21 upstream sent no valid HTTP/1.0 header while reading response header from upstream, client: x.x.x.x, server: loomio.appning.org, request: "GET /dashboard HTTP/2.0", upstream: "http://172.17.0.6:25/dashboard", host: "loomio.appning.org"
nginx_1 | nginx.1 | loomio.appning.org x.x.x.x - - [30/Oct/2017:16:00:47 +0000] "GET /dashboard HTTP/2.0" 009 36 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0"

DU

Jose Simoes Fri 3 Nov 2017 8:56PM

Bump!

RG

Robert Guthrie Sat 4 Nov 2017 7:55AM

I setup an install the other day and it worked well. I don't see what the problem could be.

but this seems wrong:
http://172.17.0.6:25/dashboard

why is it referencing port 25? it should be loomio:3000

RG

Robert Guthrie Sat 4 Nov 2017 7:56AM

it seems like you've edited your docker-compose.yml a bit heavily. can you share that?

WH

William Harader Tue 7 Nov 2017 4:15PM

I get the exact same error on a fresh install of Ubuntu 14.04. I followed the instructions for loomio-deploy exactly, except for setting up SMTP, which I assume shouldn't be an issue. I watched the resource usage, and it's thrashing the server, so I believe the issue is caused by a timeout somewhere.

Think a server upgrade would fix things?

RG

Robert Guthrie Tue 7 Nov 2017 7:08PM

Can you share your env and docker-compose files please @williamharader and @josesimoes?

DU

Jose Simoes Tue 7 Nov 2017 8:42PM

Sorry for the latency. Sure, here they are:

docker-compose.yml: https://pastebin.com/gahneye8

env: https://pastebin.com/18S5j6Cx

I've switched sensitive data with XXX. Also, I've only edited env, not docker-compose.

Thank you for helping!

RG

Robert Guthrie Tue 7 Nov 2017 10:58PM

just to check: Have you run

docker-compose down; docker-compose pull; docker-compose up -d

to ensure you're running latest images?

DU

Jose Simoes Tue 7 Nov 2017 11:02PM

The whole problem started when I updated Loomio. From there, I've cleaned all docker images and containers and re-installed (again). Same problem. Then I re-built the droplet, and re-installed Loomio. No good. So the problem is very probably in my env file, but... Where?

RG

Robert Guthrie Tue 7 Nov 2017 11:16PM

do you have javascript console errors?

Load More