Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to install following instructions #9

Closed
dalareo opened this issue Feb 16, 2017 · 2 comments
Closed

Not able to install following instructions #9

dalareo opened this issue Feb 16, 2017 · 2 comments

Comments

@dalareo
Copy link

dalareo commented Feb 16, 2017

I get:

Attaching to loomiodeploy_letsencrypt_1, loomiodeploy_nginx_1, loomiodeploy_mailin_1, loomiodeploy_loomio_1, loomiodeploy_worker_1, loomiodeploy_faye_1, loomiodeploy_db_1
mailin_1       | info: Mailin v3.0.3
nginx_1        | forego     | starting dockergen.1 on port 5000
mailin_1       | info: Webhook url: http://loomio:3000/email_processor/
letsencrypt_1  | Sleep for 3600s
nginx_1        | forego     | starting nginx.1 on port 5100
mailin_1       | info: Log file: /var/log/mailin.log
letsencrypt_1  | 2017/02/16 18:32:49 Generated '/app/letsencrypt_service_data' from 6 containers
nginx_1        | dockergen.1 | 2017/02/16 18:32:48 Generated '/etc/nginx/conf.d/default.conf' from 6 containers
mailin_1       | info: Mailin Smtp server listening on port 25
letsencrypt_1  | 2017/02/16 18:32:49 Running '/app/update_certs'
nginx_1        | dockergen.1 | 2017/02/16 18:32:48 Running 'nginx -s reload'
mailin_1       | warn: Webhook http://loomio:3000/email_processor/ seems invalid or down. You may want to double check the webhook url.
letsencrypt_1  | 2017/02/16 18:32:49 Watching docker events
nginx_1        | dockergen.1 | 2017/02/16 18:32:48 Watching docker events
nginx_1        | dockergen.1 | 2017/02/16 18:32:48 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
letsencrypt_1  | Reloading nginx proxy...
nginx_1        | dockergen.1 | 2017/02/16 18:32:49 Received event start for container 0177ff90294f
loomio_1       | [7] Puma starting in cluster mode...
letsencrypt_1  | 2017/02/16 18:32:49 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/update_certs'
worker_1       | [Worker(host:7c167e70de75 pid:1)] Starting job worker
nginx_1        | dockergen.1 | 2017/02/16 18:32:49 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'
loomio_1       | [7] * Version 2.15.3 (ruby 2.3.0-p0), codename: Autumn Arbor Airbrush
letsencrypt_1  | �h2017/02/16 18:32:49 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification ''
worker_1       | 2017-02-16T18:32:58+0000: [Worker(host:7c167e70de75 pid:1)] Starting job worker
nginx_1        | nginx.1    | 0.0.0.0 172.17.0.1 - - [16/Feb/2017:18:33:35 +0000] "GET / HTTP/1.1" 503 213 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0"
loomio_1       | [7] * Min threads: 4, max threads: 4
letsencrypt_1  | �;2017/02/16 18:32:49 [notice] 45#45: signal process started
nginx_1        | nginx.1    | 0.0.0.0 172.17.0.1 - - [16/Feb/2017:18:33:41 +0000] "GET / HTTP/1.1" 503 213 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0"
db_1           | LOG:  database system was shut down at 2017-02-16 18:31:17 UTC
letsencrypt_1  | Creating/renewal faye.loomio.example.local certificates... (faye.loomio.example.local)
loomio_1       | [7] * Environment: production
db_1           | LOG:  MultiXact member wraparound protections are now enabled
loomio_1       | [7] * Process workers: 1
db_1           | LOG:  database system is ready to accept connections
letsencrypt_1  | 2017-02-16 18:32:49,922:INFO:simp_le:1211: Generating new account key
db_1           | LOG:  autovacuum launcher started
loomio_1       | [7] * Preloading application
letsencrypt_1  | 2017-02-16 18:32:50,375:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
loomio_1       | [7] * Listening on tcp://0.0.0.0:3000
letsencrypt_1  | 2017-02-16 18:32:51,750:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): letsencrypt.org
loomio_1       | [7] Use Ctrl-C to stop
letsencrypt_1  | ACME server returned an error: urn:acme:error:malformed :: The request message was malformed :: Name does not end in a public suffix
loomio_1       | [7] - Worker 0 (pid: 10) booted, phase: 0
letsencrypt_1  | 
letsencrypt_1  | 
letsencrypt_1  | Debugging tips: -v improves output verbosity. Help is available under --help.
letsencrypt_1  | Creating/renewal loomio.example.local certificates... (loomio.example.local)
letsencrypt_1  | 2017-02-16 18:32:53,596:INFO:simp_le:1211: Generating new account key
letsencrypt_1  | 2017-02-16 18:32:53,924:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
letsencrypt_1  | 2017-02-16 18:32:55,368:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): letsencrypt.org
letsencrypt_1  | ACME server returned an error: urn:acme:error:malformed :: The request message was malformed :: Name does not end in a public suffix
letsencrypt_1  | 
letsencrypt_1  | 
letsencrypt_1  | Debugging tips: -v improves output verbosity. Help is available under --help.
letsencrypt_1  | Creating/renewal loomio.example.local certificates... (loomio.example.local)
letsencrypt_1  | 2017-02-16 18:32:57,183:INFO:simp_le:1211: Generating new account key
letsencrypt_1  | 2017-02-16 18:32:58,368:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
letsencrypt_1  | 2017-02-16 18:32:59,615:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): letsencrypt.org
letsencrypt_1  | ACME server returned an error: urn:acme:error:malformed :: The request message was malformed :: Name does not end in a public suffix
letsencrypt_1  | 
letsencrypt_1  | 
letsencrypt_1  | Debugging tips: -v improves output verbosity. Help is available under --help.
letsencrypt_1  | Sleep for 3600s

But get error "Secure connection failed" when accessing: https://loomio.example.local/

@modulistic
Copy link
Contributor

Hey, I'm a bit late, but you need a public DNS name for this to work. A private one will not do for the way loomio_deploy deals with letsencrypt. Plus the .local has its own gazillion issues to consider (see mDNS)

@juliencarnot
Copy link
Contributor

If you do not have a public DNS name, you might be more interested in the dev install instructions

I added a PR to indicate this in the readme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants