loomio-deploy updated

after a docker-compose restart:

docker-compose restart
Restarting loomiodeploy_letsencrypt_1 ... done
Restarting loomiodeploy_nginx_1 ...
Restarting loomiodeploy_mailin_1 ... done
Restarting loomiodeploy_loomio_1 ... done
Restarting loomiodeploy_worker_1 ... done
Restarting loomiodeploy_faye_1 ... done
Restarting loomiodeploy_db_1 ... done

ERROR: for loomiodeploy_nginx_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

try docker-compose down then docker-compose up -d

docker-compose down
Stopping loomiodeploy_letsencrypt_1 ... done
Stopping loomiodeploy_nginx_1 ...
Stopping loomiodeploy_mailin_1 ... done
Stopping loomiodeploy_loomio_1 ... done
Stopping loomiodeploy_worker_1 ... done
Stopping loomiodeploy_faye_1 ... done
Stopping loomiodeploy_db_1 ... done

ERROR: for loomiodeploy_nginx_1 UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=70)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

so can't stop loomiodeploy_nginx_1

docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f48a2113cb1b jwilder/nginx-proxy "/app/docker-entrypoi" 10 days ago Up 50 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp loomiodeploy_nginx_1

so i restarted the server

just after restart i have:

docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

and i do: docker-compose up -d

after this i have

docker-compose up -d
Starting loomiodeploy_faye_1
Starting loomiodeploy_db_1
Starting loomiodeploy_worker_1
Starting loomiodeploy_loomio_1
Starting loomiodeploy_mailin_1
Starting loomiodeploy_nginx_1
Starting loomiodeploy_letsencrypt_1

everything seems to be ok

and the log are on the file joined

it's not works

You need a successful docker-compose down to remove the containers. Looks like you're restarting existing containers rather than creating new ones.

Are you sure that port 80 is mapped correctly? Looks like the same problem as before.

Don't know why but today "docker-compose down" works and all containers are stopped and removed even nginx.

"docker-compose up -d" ok

You're right i have a problem with the mapping of port 80 and 443 cause i try to redirect theses ports through a VPN.

I correct the problem and inform you

Hi
I'm also getting errors with https and http access.
I just created an issue on loomio-deploy's GitHub project (https://github.com/loomio/loomio-deploy/issues/3).
It could be discussed in this thread or on the issue, as you want.
rgds,
Louis

Hi you need an internet connection for Lets encrypt to work properly in creating the certs.
(This is due to the cross signing needing to be done online from your end to their intermediary, this also applies to other cert authorities.)

In order to at least temporarily resolve the issue, you need to be online, have the domain on that machine and register that domain as part of the Lets encrypt process (which as I recall uses nginx.) You should then be able at least to import the key pair into your server and get loomio working.

Hi Andrew. Thank you for your reply.
It would not be so easy to make our server accessible from internet.
Would it be possible to use http only?

Although you only need to be online while you obtain certificates, it may be possible if you have it configured to only use http to have it entirely offline.
I am looking to install an instance of loomio on an obsolete laptop shortly, however that would be online basically all the time.
(problems with half-wit chorus nz fibre installers in the neighbourhood should not occur again.)