API tools faq
paste
Advertisement
Guest User

Untitled

a guest
May 22nd, 2019
177
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 24.22 KB | None | 0 0
raw download clone embed print report
  1. root@musicstash-loomio:~/loomio-deploy# docker-compose logs
  2. Attaching to loomio-letsencrypt, loomio-nginx, loomio-mailin, loomio-app, loomio-worker, loomio-redis, loomio-db
  3. loomio-nginx | WARNING: /etc/nginx/dhparam/dhparam.pem was not found. A pre-generated dhparam.pem will be used fo
  4. r now while a new one
  5. loomio-nginx | is being generated in the background. Once the new dhparam.pem is in place, nginx will be reloade
  6. d.
  7. loomio-nginx | forego | starting dockergen.1 on port 5000
  8. loomio-nginx | forego | starting nginx.1 on port 5100
  9. loomio-nginx | dockergen.1 | 2019/05/22 20:26:56 Generated '/etc/nginx/conf.d/default.conf' from 7 containers
  10. loomio-nginx | dockergen.1 | 2019/05/22 20:26:57 Running 'nginx -s reload'
  11. loomio-nginx | dockergen.1 | 2019/05/22 20:27:07 Watching docker events
  12. loomio-nginx | dockergen.1 | 2019/05/22 20:29:09 Contents of /etc/nginx/conf.d/default.conf did not change. Skipp
  13. ing notification 'nginx -s reload'
  14. loomio-nginx | dockergen.1 | 2019/05/22 20:29:17 Contents of /etc/nginx/conf.d/default.conf did not change. Skipp
  15. ing notification 'nginx -s reload'
  16. loomio-app | Warning: method `update` already defined
  17. loomio-app | Building clientside assets...
  18. loomio-app |
  19. loomio-app | -> rm -rf public/client/*
  20. loomio-app |
  21. loomio-app | -> cd vue && npm i && npm run build && cd ..
  22. loomio-app | npm WARN prosemirror-utils@0.8.2 requires a peer of prosemirror-tables@^0.7.9 but none is installe
  23. d. You must install peer dependencies yourself.
  24. loomio-app | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules/chokidar/node_modules
  25. /fsevents):
  26. loomio-app | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os
  27. ":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
  28. loomio-app | npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.8 (node_modules/fsevents):
  29. loomio-app | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.8: wanted {"os
  30. ":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
  31. loomio-app |
  32. loomio-app | audited 30344 packages in 133.965s
  33. loomio-app | found 8 vulnerabilities (1 low, 6 high, 1 critical)
  34. loomio-app | run `npm audit fix` to fix them, or `npm audit` for details
  35. loomio-app |
  36. loomio-app | > vue@0.1.0 build /loomio/vue
  37. loomio-app | > vue-cli-service build
  38. loomio-app |
  39. loomio-app |
  40. loomio-app | - Building for production...
  41. loomio-worker | Warning: method `update` already defined
  42. loomio-worker | [Worker(host:832c29f44923 pid:7)] Starting job worker
  43. loomio-worker | 2019-05-22T20:36:57+0000: [Worker(host:832c29f44923 pid:7)] Starting job worker
  44. loomio-db | The files belonging to this database system will be owned by user "postgres".
  45. loomio-db | This user must also own the server process.
  46. loomio-db |
  47. loomio-db | The database cluster will be initialized with locale "en_US.utf8".
  48. loomio-db | The default database encoding has accordingly been set to "UTF8".
  49. loomio-db | The default text search configuration will be set to "english".
  50. loomio-db |
  51. loomio-db | Data page checksums are disabled.
  52. loomio-db |
  53. loomio-db | fixing permissions on existing directory /pgdata ... ok
  54. loomio-db | creating subdirectories ... ok
  55. loomio-db | selecting default max_connections ... 100
  56. loomio-db | selecting default shared_buffers ... 128MB
  57. loomio-db | selecting dynamic shared memory implementation ... posix
  58. loomio-db | creating configuration files ... ok
  59. loomio-db | running bootstrap script ... ok
  60. loomio-db | performing post-bootstrap initialization ... ok
  61. loomio-db | WARNING: enabling "trust" authentication for local connections
  62. loomio-db | You can change this by editing pg_hba.conf or using the option -A, or
  63. loomio-db | --auth-local and --auth-host, the next time you run initdb.
  64. loomio-db |
  65. loomio-db | Success. You can now start the database server using:
  66. loomio-db |
  67. loomio-db | pg_ctl -D /pgdata -l logfile start
  68. loomio-db |
  69. loomio-db | waiting for server to start....LOG: database system was shut down at 2019-05-22 20:08:35 UTC
  70. loomio-db | LOG: MultiXact member wraparound protections are now enabled
  71. loomio-db | LOG: database system is ready to accept connections
  72. loomio-db | LOG: autovacuum launcher started
  73. loomio-db | done
  74. loomio-db | server started
  75. loomio-db |
  76. loomio-db | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
  77. loomio-db |
  78. loomio-db | LOG: received fast shutdown request
  79. loomio-db | LOG: aborting any active transactions
  80. loomio-db | LOG: autovacuum launcher shutting down
  81. loomio-db | LOG: shutting down
  82. loomio-db | waiting for server to shut down....LOG: database system is shut down
  83. loomio-db | done
  84. loomio-db | server stopped
  85. loomio-db |
  86. loomio-db | PostgreSQL init process complete; ready for start up.
  87. loomio-db |
  88. loomio-db | LOG: database system was shut down at 2019-05-22 20:08:37 UTC
  89. loomio-db | LOG: MultiXact member wraparound protections are now enabled
  90. loomio-db | LOG: database system is ready to accept connections
  91. loomio-db | LOG: autovacuum launcher started
  92. loomio-redis | 1:C 22 May 2019 20:10:46.262 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
  93. loomio-redis | 1:C 22 May 2019 20:10:46.263 # Redis version=5.0.5, bits=64, commit=00000000, modified=0, pid=1, j
  94. ust started
  95. loomio-redis | 1:C 22 May 2019 20:10:46.263 # Warning: no config file specified, using the default config. In ord
  96. er to specify a config file use redis-server /path/to/redis.conf
  97. loomio-redis | 1:M 22 May 2019 20:10:46.264 # You requested maxclients of 10000 requiring at least 10032 max file
  98. descriptors.
  99. loomio-redis | 1:M 22 May 2019 20:10:46.264 # Server can't set maximum open files to 10032 because of OS error: O
  100. peration not permitted.
  101. loomio-redis | 1:M 22 May 2019 20:10:46.264 # Current maximum open files is 4096. maxclients has been reduced to
  102. 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
  103. loomio-redis | 1:M 22 May 2019 20:10:46.265 * Running mode=standalone, port=6379.
  104. loomio-redis | 1:M 22 May 2019 20:10:46.265 # WARNING: The TCP backlog setting of 511 cannot be enforced because
  105. /proc/sys/net/core/somaxconn is set to the lower value of 128.
  106. loomio-redis | 1:M 22 May 2019 20:10:46.265 # Server initialized
  107. loomio-redis | 1:M 22 May 2019 20:10:46.265 # WARNING overcommit_memory is set to 0! Background save may fail und
  108. er low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or ru
  109. n the command 'sysctl vm.overcommit_memory=1' for this to take effect.
  110. loomio-redis | 1:M 22 May 2019 20:10:46.266 # WARNING you have Transparent Huge Pages (THP) support enabled in yo
  111. ur kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo nev
  112. er > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the
  113. setting after a reboot. Redis must be restarted after THP is disabled.
  114. loomio-redis | 1:M 22 May 2019 20:10:46.266 * Ready to accept connections
  115. loomio-letsencrypt | Generating a RSA private key
  116. loomio-letsencrypt | ..............................................................................................
  117. ...................................................................................................................
  118. ...................................................................................................................
  119. ...................................................................................................................
  120. ...................................................................................................++++
  121. loomio-letsencrypt | writing new private key to '/etc/nginx/certs/default.key.new'
  122. loomio-letsencrypt | -----
  123. loomio-letsencrypt | Info: a default key and certificate have been created at /etc/nginx/certs/default.key and /etc
  124. /nginx/certs/default.crt.
  125. loomio-letsencrypt | Info: Creating Diffie-Hellman group in the background.
  126. loomio-letsencrypt | A pre-generated Diffie-Hellman group will be used for now while the new one
  127. loomio-letsencrypt | is being created.
  128. loomio-letsencrypt | Generating DH parameters, 2048 bit long safe prime, generator 2
  129. loomio-letsencrypt | Reloading nginx proxy (a8965a152e689b53901263747ca812639a8916378525c737d1537aebceac79b2)...
  130. loomio-letsencrypt | 2019/05/22 20:31:39 Generated '/etc/nginx/conf.d/default.conf' from 8 containers
  131. loomio-letsencrypt | This is going to take a long time
  132. loomio-letsencrypt | Info: Diffie-Hellman group creation complete, reloading nginx.
  133. loomio-letsencrypt | Reloading nginx proxy (a8965a152e689b53901263747ca812639a8916378525c737d1537aebceac79b2)...
  134. loomio-db | ERROR: database "loomio_production" already exists
  135. loomio-db | STATEMENT: CREATE DATABASE "loomio_production" ENCODING = 'utf8'
  136. loomio-db | WARNING: hash indexes are not WAL-logged and their use is discouraged
  137. loomio-db | ERROR: database "loomio_production" already exists
  138. loomio-db | STATEMENT: CREATE DATABASE "loomio_production" ENCODING = 'utf8'
  139. loomio-db | ERROR: database "loomio_production" already exists
  140. loomio-db | STATEMENT: CREATE DATABASE "loomio_production" ENCODING = 'utf8'
  141. loomio-db | ERROR: database "loomio_production" already exists
  142. loomio-db | STATEMENT: CREATE DATABASE "loomio_production" ENCODING = 'utf8'
  143. loomio-mailin | info: Mailin v3.0.4
  144. loomio-mailin | info: Webhook url: http://app:3000/email_processor/
  145. loomio-mailin | info: Log file: /var/log/mailin.log
  146. loomio-mailin | info: Mailin Smtp server listening on port 25
  147. loomio-mailin | warn: Webhook http://app:3000/email_processor/ seems invalid or down. You may want to double check
  148. the webhook url.
  149. loomio-nginx | nginx.1 | test.godhub.xyz 199.119.233.175 - - [22/May/2019:20:30:54 +0000] "GET / HTTP/1.1" 502
  150. 575 "-" "Mozilla/5.0 (Linux; Android 7.0; SM-N920W8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 M
  151. obile Safari/537.36"
  152. loomio-nginx | nginx.1 | 2019/05/22 20:30:54 [error] 38#38: *2 connect() failed (111: Connection refused) whil
  153. e connecting to upstream, client: 199.119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "h
  154. ttp://172.17.0.6:3000/", host: "test.godhub.xyz"
  155. loomio-nginx | nginx.1 | 2019/05/22 20:30:54 [error] 38#38: *2 connect() failed (111: Connection refused) whil
  156. e connecting to upstream, client: 199.119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "h
  157. ttp://172.17.0.5:3000/", host: "test.godhub.xyz"
  158. loomio-nginx | nginx.1 | test.godhub.xyz 66.133.109.36 - - [22/May/2019:20:35:55 +0000] "GET /.well-known/acme
  159. -challenge/zlE0j-fF83LZUyOLPElY706uOONzkysiN2hNE4FgVHo HTTP/1.1" 502 173 "-" "Mozilla/5.0 (compatible; Let's Encryp
  160. t validation server; +https://www.letsencrypt.org)"
  161. loomio-nginx | nginx.1 | 2019/05/22 20:35:55 [error] 38#38: *6 connect() failed (111: Connection refused) whil
  162. e connecting to upstream, client: 66.133.109.36, server: test.godhub.xyz, request: "GET /.well-known/acme-challenge
  163. /zlE0j-fF83LZUyOLPElY706uOONzkysiN2hNE4FgVHo HTTP/1.1", upstream: "http://172.17.0.4:3000/.well-known/acme-challeng
  164. e/zlE0j-fF83LZUyOLPElY706uOONzkysiN2hNE4FgVHo", host: "test.godhub.xyz"
  165. loomio-nginx | nginx.1 | pstream: "http://172.17.0.5:3000/.well-known/acme-challenge/zlE0j-fF83LZUyOLPElY706uO
  166. ONzkysiN2hNE4FgVHo", host: "test.godhub.xyz"
  167. loomio-nginx | nginx.1 | server: test.godhub.xyz, request: "GET /.well-known/acme-challenge/zlE0j-fF83LZUyOLPE
  168. lY706uOONzkysiN2hNE4FgVHo HTTP/1.1", upstream: "http://172.17.0.6:3000/.well-known/acme-challenge/zlE0j-fF83LZUyOLP
  169. ElY706uOONzkysiN2hNE4FgVHo", host: "test.godhub.xyz"
  170. loomio-nginx | nginx.1 | test.godhub.xyz 66.133.109.36 - - [22/May/2019:20:37:07 +0000] "GET /.well-known/acme
  171. -challenge/uIwp-zchQWd1xNMq7i6CN1eYQj24zLd5kE6Z4v5uPBM HTTP/1.1" 502 173 "-" "Mozilla/5.0 (compatible; Let's Encryp
  172. t validation server; +https://www.letsencrypt.org)"
  173. loomio-nginx | nginx.1 | 2019/05/22 20:37:07 [error] 38#38: *10 connect() failed (111: Connection refused) whi
  174. le connecting to upstream, client: 66.133.109.36, server: test.godhub.xyz, request: "GET /.well-known/acme-challeng
  175. e/uIwp-zchQWd1xNMq7i6CN1eYQj24zLd5kE6Z4v5uPBM HTTP/1.1", upstream: "http://172.17.0.4:3000/.well-known/acme-challen
  176. ge/uIwp-zchQWd1xNMq7i6CN1eYQj24zLd5kE6Z4v5uPBM", host: "test.godhub.xyz"
  177. loomio-nginx | nginx.1 | , upstream: "http://172.17.0.6:3000/.well-known/acme-challenge/uIwp-zchQWd1xNMq7i6CN1
  178. eYQj24zLd5kE6Z4v5uPBM", host: "test.godhub.xyz"
  179. loomio-nginx | nginx.1 | 9.36, server: test.godhub.xyz, request: "GET /.well-known/acme-challenge/uIwp-zchQWd1
  180. xNMq7i6CN1eYQj24zLd5kE6Z4v5uPBM HTTP/1.1", upstream: "http://172.17.0.5:3000/.well-known/acme-challenge/uIwp-zchQWd
  181. 1xNMq7i6CN1eYQj24zLd5kE6Z4v5uPBM", host: "test.godhub.xyz"
  182. loomio-nginx | nginx.1 | 2019/05/22 20:37:37 [error] 38#38: *15 connect() failed (111: Connection refused) whi
  183.  
  184. le connecting to upstream, client: 199.119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "
  185. http://172.17.0.4:3000/", host: "test.godhub.xyz"
  186. loomio-letsencrypt | 2019/05/22 20:31:46 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notifi
  187. cation ''
  188. loomio-letsencrypt | 2019/05/22 20:31:47 [emerg] 81#81: PEM_read_bio_DHparams("/etc/nginx/dhparam/dhparam.pem") fai
  189. led (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: DH PARAMETERS)
  190. loomio-letsencrypt | Sleep for 3600s
  191. loomio-letsencrypt | 2019/05/22 20:32:46 Generated '/app/letsencrypt_service_data' from 8 containers
  192. loomio-letsencrypt | 2019/05/22 20:32:47 Running '/app/signal_le_service'
  193. loomio-letsencrypt | 2019/05/22 20:32:49 Watching docker events
  194. loomio-letsencrypt | /etc/nginx/certs/test.godhub.xyz /app
  195. loomio-letsencrypt | 2019/05/22 20:33:23 Contents of /app/letsencrypt_service_data did not change. Skipping notific
  196. ation '/app/signal_le_service'
  197. loomio-letsencrypt | Reloading nginx proxy (a8965a152e689b53901263747ca812639a8916378525c737d1537aebceac79b2)...
  198. loomio-letsencrypt | 2019/05/22 20:34:25 Generated '/etc/nginx/conf.d/default.conf' from 8 containers
  199. loomio-letsencrypt | Creating/renewal test.godhub.xyz certificates... (test.godhub.xyz)
  200. loomio-letsencrypt | 2019-05-22 20:35:24,592:INFO:simp_le:1382: Generating new account key
  201. loomio-letsencrypt | 2019-05-22 20:35:49,342:INFO:simp_le:1407: By using simp_le, you implicitly agree to the CA's
  202. terms of service: https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf
  203. loomio-letsencrypt | 2019-05-22 20:35:50,594:INFO:simp_le:1479: Generating new certificate private key
  204. loomio-letsencrypt | 2019-05-22 20:36:07,342:ERROR:simp_le:1446: CA marked some of the authorizations as invalid, w
  205. hich likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in
  206. -d example.com:path or --default_root? Are all your domains accessible from the internet? Please check your domains
  207. ' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and
  208. AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If your DNS pr
  209. ovider does not answer correctly to CAA records request, Let's Encrypt won't issue a certificate for your domain (s
  210. ee https://letsencrypt.org/docs/caa/). Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/sVQQ
  211. zd46-02DYCSppn26s0Zh7VuwxFWtaG6FaU3jpx4
  212. loomio-letsencrypt | 2019-05-22 20:36:07,364:INFO:simp_le:360: Saving account_key.json
  213. loomio-letsencrypt | Challenge validation has failed, see error log.
  214. loomio-letsencrypt |
  215. loomio-letsencrypt | Debugging tips: -v improves output verbosity. Help is available under --help.
  216. loomio-letsencrypt | /app
  217. loomio-letsencrypt | /etc/nginx/certs/test.godhub.xyz /app
  218. loomio-letsencrypt | Creating/renewal test.godhub.xyz certificates... (test.godhub.xyz)
  219. loomio-letsencrypt | 2019-05-22 20:37:05,592:INFO:simp_le:1479: Generating new certificate private key
  220. loomio-letsencrypt | 2019-05-22 20:37:15,594:ERROR:simp_le:1446: CA marked some of the authorizations as invalid, w
  221. hich likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in
  222. -d example.com:path or --default_root? Are all your domains accessible from the internet? Please check your domains
  223. ' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and
  224. AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If your DNS pr
  225. ovider does not answer correctly to CAA records request, Let's Encrypt won't issue a certificate for your domain (s
  226. ee https://letsencrypt.org/docs/caa/). Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/wlb3
  227. 7FoGWb-MVOTt3zkMuDogqYr7hVcNAdbkf6hMCBk
  228. loomio-letsencrypt | Challenge validation has failed, see error log.
  229. loomio-letsencrypt |
  230. loomio-letsencrypt | Debugging tips: -v improves output verbosity. Help is available under --help.
  231. loomio-letsencrypt | /app
  232. loomio-letsencrypt | /etc/nginx/certs/test.godhub.xyz /app
  233. loomio-nginx | nginx.1 | test.godhub.xyz 199.119.233.175 - - [22/May/2019:20:37:37 +0000] "GET / HTTP/1.1" 502
  234. 575 "-" "Mozilla/5.0 (Linux; Android 7.0; SM-N920W8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 M
  235. obile Safari/537.36"
  236. loomio-nginx | nginx.1 | connect() failed (111: Connection refused) while connecting to upstream, client: 199
  237. .119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "http://172.17.0.6:3000/", host: "test.
  238. godhub.xyz"
  239. loomio-nginx | nginx.1 | test.godhub.xyz 66.133.109.36 - - [22/May/2019:20:38:02 +0000] "GET /.well-known/acme
  240. -challenge/fAb6VBERv_j9WrNKt_9rBiwY1WdQTWRRY8AhZNGq0q4 HTTP/1.1" 502 173 "-" "Mozilla/5.0 (compatible; Let's Encryp
  241. t validation server; +https://www.letsencrypt.org)"
  242. loomio-nginx | nginx.1 | , upstream: "http://172.17.0.6:3000/.well-known/acme-challenge/fAb6VBERv_j9WrNKt_9rBi
  243. wY1WdQTWRRY8AhZNGq0q4", host: "test.godhub.xyz"
  244. loomio-nginx | nginx.1 | 9.36, server: test.godhub.xyz, request: "GET /.well-known/acme-challenge/fAb6VBERv_j9
  245. WrNKt_9rBiwY1WdQTWRRY8AhZNGq0q4 HTTP/1.1", upstream: "http://172.17.0.5:3000/.well-known/acme-challenge/fAb6VBERv_j
  246. 9WrNKt_9rBiwY1WdQTWRRY8AhZNGq0q4", host: "test.godhub.xyz"
  247. loomio-nginx | nginx.1 | 2019/05/22 20:38:41 [error] 38#38: *15 connect() failed (111: Connection refused) whi
  248. le connecting to upstream, client: 199.119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "
  249. http://172.17.0.4:3000/", host: "test.godhub.xyz"
  250. loomio-nginx | nginx.1 | connect() failed (111: Connection refused) while connecting to upstream, client: 199
  251. .119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "http://172.17.0.6:3000/", host: "test.
  252. godhub.xyz"
  253. loomio-nginx | nginx.1 | test.godhub.xyz 199.119.233.175 - - [22/May/2019:20:38:41 +0000] "GET / HTTP/1.1" 502
  254. 575 "-" "Mozilla/5.0 (Linux; Android 7.0; SM-N920W8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 M
  255. obile Safari/537.36"
  256. loomio-nginx | nginx.1 | 2019/05/22 20:39:07 [error] 38#38: *15 connect() failed (111: Connection refused) whi
  257. le connecting to upstream, client: 199.119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "
  258. http://172.17.0.4:3000/", host: "test.godhub.xyz"
  259. loomio-nginx | nginx.1 | connect() failed (111: Connection refused) while connecting to upstream, client: 199
  260. .119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "http://172.17.0.5:3000/", host: "test.
  261. godhub.xyz"
  262. loomio-nginx | nginx.1 | test.godhub.xyz 199.119.233.175 - - [22/May/2019:20:39:07 +0000] "GET / HTTP/1.1" 502
  263. 575 "-" "Mozilla/5.0 (Linux; Android 7.0; SM-N920W8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 M
  264. obile Safari/537.36"
  265. loomio-nginx | nginx.1 | 2019/05/22 20:41:22 [error] 38#38: *29 connect() failed (111: Connection refused) whi
  266. le connecting to upstream, client: 72.137.176.178, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "h
  267. ttp://172.17.0.4:3000/", host: "test.godhub.xyz"
  268. loomio-nginx | nginx.1 | 2019/05/22 20:41:22 [warn] 38#38: *29 upstream server temporarily disabled while conn
  269. ecting to upstream, client: 72.137.176.178, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "http://1
  270. 72.17.0.4:3000/", host: "test.godhub.xyz"
  271. loomio-nginx | nginx.1 | ream server temporarily disabled while connecting to upstream, client: 72.137.176.178
  272. , server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "http://172.17.0.6:3000/", host: "test.godhub.xyz"
  273. loomio-nginx | nginx.1 | test.godhub.xyz 72.137.176.178 - - [22/May/2019:20:41:22 +0000] "GET / HTTP/1.1" 502
  274. 575 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 Safa
  275. ri/537.36"
  276. loomio-nginx | 2019/05/22 20:41:24 [notice] 103#103: signal process started
  277. loomio-nginx | Generating DH parameters, 2048 bit long safe prime, generator 2
  278. loomio-nginx | This is going to take a long time
  279. loomio-nginx | dhparam generation complete, reloading nginx
  280. loomio-nginx | nginx.1 | test.godhub.xyz 72.137.176.178 - - [22/May/2019:20:49:05 +0000] "GET / HTTP/1.1" 502
  281. 575 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 Safa
  282. ri/537.36"
  283. loomio-nginx | nginx.1 | 2019/05/22 20:49:04 [error] 105#105: *34 connect() failed (111: Connection refused) w
  284. hile connecting to upstream, client: 72.137.176.178, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream:
  285. "http://172.17.0.6:3000/", host: "test.godhub.xyz"
  286. loomio-nginx | nginx.1 | 2019/05/22 20:49:04 [warn] 105#105: *34 upstream server temporarily disabled while co
  287. nnecting to upstream, client: 72.137.176.178, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "http:/
  288. /172.17.0.6:3000/", host: "test.godhub.xyz"
  289. loomio-nginx | nginx.1 | : *34 upstream server temporarily disabled while connecting to upstream, client: 72.1
  290. 37.176.178, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "http://172.17.0.4:3000/", host: "test.go
  291. dhub.xyz"
  292. loomio-nginx | nginx.1 | test.godhub.xyz 199.119.233.175 - - [22/May/2019:20:49:11 +0000] "GET / HTTP/1.1" 502
  293. 575 "-" "Mozilla/5.0 (Linux; Android 7.0; SM-N920W8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 M
  294. obile Safari/537.36"
  295. loomio-nginx | nginx.1 | 2019/05/22 20:49:11 [error] 105#105: *39 no live upstreams while connecting to upstre
  296. am, client: 199.119.233.175, server: test.godhub.xyz, request: "GET / HTTP/1.1", upstream: "http://test.godhub.xyz/
  297. ", host: "test.godhub.xyz"
  298. loomio-letsencrypt | Creating/renewal test.godhub.xyz certificates... (test.godhub.xyz)
  299. loomio-letsencrypt | 2019-05-22 20:38:00,343:INFO:simp_le:1479: Generating new certificate private key
  300. loomio-letsencrypt | 2019-05-22 20:38:05,842:ERROR:simp_le:1446: CA marked some of the authorizations as invalid, w
  301. hich likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in
  302. -d example.com:path or --default_root? Are all your domains accessible from the internet? Please check your domains
  303. ' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and
  304. AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If your DNS pr
  305. ovider does not answer correctly to CAA records request, Let's Encrypt won't issue a certificate for your domain (s
  306. ee https://letsencrypt.org/docs/caa/). Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/Vf9w
  307. uGo-VjDBl0QwOcVLi4YYEJE_3yJiR9aX1HoASoQ
  308. loomio-letsencrypt | Challenge validation has failed, see error log.
  309. loomio-letsencrypt |
  310. loomio-letsencrypt | Debugging tips: -v improves output verbosity. Help is available under --help.
  311. loomio-letsencrypt | /app
  312. loomio-letsencrypt | Sleep for 3600s
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!