Advertisement
truetype

Untitled

Jan 28th, 2019
81
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.07 KB | None | 0 0
  1. cronjob running on Sun Jan 20 02:08:00 CET 2019
  2. Running certbot renew
  3. Saving debug log to /var/log/letsencrypt/letsencrypt.log
  4.  
  5. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  6. Processing /etc/letsencrypt/renewal/Redacteddomain.com.conf
  7. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  8. Cert is due for renewal, auto-renewing...
  9. Non-interactive renewal: random delay of 295 seconds
  10. Plugins selected: Authenticator standalone, Installer None
  11. Running pre-hook command: if ps aux | grep [n]ginx: > /dev/null; then s6-svc -d /var/run/s6/services/nginx; fi
  12. Renewing an existing certificate
  13. Performing the following challenges:
  14. http-01 challenge for couchpotato.Redacteddomain.com
  15. http-01 challenge for home.Redacteddomain.com
  16. http-01 challenge for muxi.Redacteddomain.com
  17. http-01 challenge for nextcloud.Redacteddomain.com
  18. http-01 challenge for ombi.Redacteddomain.com
  19. http-01 challenge for plex.Redacteddomain.com
  20. http-01 challenge for plexw.Redacteddomain.com
  21. http-01 challenge for tautulli.Redacteddomain.com
  22. http-01 challenge for Redacteddomain.com
  23. http-01 challenge for www.Redacteddomain.com
  24. Waiting for verification...
  25. Cleaning up challenges
  26. Attempting to renew cert (Redacteddomain.com) from /etc/letsencrypt/renewal/Redacteddomain.com.conf produced an unexpected error: Failed authorization procedure. home.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://home.Redacteddomain.com/.well-known/acme-challenge/XPVls6N-Q1Vt7OWoNOZrMhjjnb4PxwCmN2s-HQ: Timeout during connect (likely firewall problem), ombi.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://ombi.Redacteddomain.com/.well-known/acme-challenge/TNkuXtrDE_oF6GulDlxxql_SHlLbwpq_-a44: Timeout during connect (likely firewall problem), couchpotato.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://couchpotato.Redacteddomain.com/.well-known/acme-challenge/Szy5YNNxnyxIUnT4_AqAvadTSLE0Y-d_dGwcc: Timeout during connect (likely firewall problem), www.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.Redacteddomain.com/.well-known/acme-challenge/q8rIaUI4SEFgsox87_hnB0zurInNw0OnvhERNLcU: Timeout during connect (likely firewall problem), plexw.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://plexw.Redacteddomain.com/.well-known/acme-challenge/fTkC6EZA68evWI6oNB2h3y2mQxPX9iOW9rYTwfE: Timeout during connect (likely firewall problem), nextcloud.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://nextcloud.Redacteddomain.com/.well-known/acme-challenge/4v_zXFY1lpkW0v97vA2WdWksVxQk6cRzLbsJsNKM: Timeout during connect (likely firewall problem), tautulli.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://tautulli.Redacteddomain.com/.well-known/acme-challenge/-G7RnWnAYPc6BBLLPNKrkPdIoxQg9SouUsTzh0ks: Timeout during connect (likely firewall problem), plex.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://plex.Redacteddomain.com/.well-known/acme-challenge/0pgozxJ4W3rRtk7qUDP7yTm9hjfTRbdyWvfDPE7k: Timeout during connect (likely firewall problem), Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://Redacteddomain.com/.well-known/acme-challenge/xb_BCbxdwx8Rcpq8cpQBScjBzv_E_Oc1BPCbTC4: Timeout during connect (likely firewall problem), muxi.Redacteddomain.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://muxi.Redacteddomain.com/.well-known/acme-challenge/vBXxMV8zPWupxaxngDbgqZs5SSlBgvQIjVdGeQw: Timeout during connect (likely firewall problem). Skipping.
  27. All renewal attempts failed. The following certs could not be renewed:
  28. /etc/letsencrypt/live/Redacteddomain.com/fullchain.pem (failure)
  29.  
  30. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  31.  
  32. All renewal attempts failed. The following certs could not be renewed:
  33. /etc/letsencrypt/live/Redacteddomain.com/fullchain.pem (failure)
  34. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  35. Running post-hook command: if ps aux | grep 's6-supervise nginx' | grep -v grep > /dev/null; then s6-svc -u /var/run/s6/services/nginx; fi; cd /config/keys/letsencrypt && openssl pkcs12 -export -out privkey.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem -passout pass: && sleep 1 && cat privkey.pem fullchain.pem > priv-fullchain-bundle.pem
  36. 1 renew failure(s), 0 parse failure(s)
  37. IMPORTANT NOTES:
  38. - The following errors were reported by the server:
  39.  
  40. Domain: home.Redacteddomain.com
  41. Type: connection
  42. Detail: Fetching
  43. http://home.Redacteddomain.com/.well-known/acme-challenge/XPVls6N-Q1Vt7OWoxhjjnb4PVBP0iJwCmN2s-HQ:
  44. Timeout during connect (likely firewall problem)
  45.  
  46. Domain: ombi.Redacteddomain.com
  47. Type: connection
  48. Detail: Fetching
  49. http://ombi.Redacteddomain.com/.well-known/acme-challenge/TNkuXtrDE_oF6GulDlO3g9xHlLbwpq_-a44:
  50. Timeout during connect (likely firewall problem)
  51.  
  52. Domain: couchpotato.Redacteddomain.com
  53. Type: connection
  54. Detail: Fetching
  55. http://couchpotato.Redacteddomain.com/.well-known/acme-challenge/Szy5YNNx0YxUnT4_AqAvadTSLE0Y-d_dGwcc:
  56. Timeout during connect (likely firewall problem)
  57.  
  58. Domain: www.Redacteddomain.com
  59. Type: connection
  60. Detail: Fetching
  61. http://www.Redacteddomain.com/.well-known/acme-challenge/q8rIaUI4SEFgsoTmOBxurInNw0OnvhERNLcU:
  62. Timeout during connect (likely firewall problem)
  63.  
  64. Domain: plexw.Redacteddomain.com
  65. Type: connection
  66. Detail: Fetching
  67. http://plexw.Redacteddomain.com/.well-known/acme-challenge/fTkC6EZA68x2h3y2mQMVesxPX9iOW9rYTwfE:
  68. Timeout during connect (likely firewall problem)
  69.  
  70. Domain: nextcloud.Redacteddomain.com
  71. Type: connection
  72. Detail: Fetching
  73. http://nextcloud.Redacteddomain.com/.well-known/acme-challenge/4v_zXFY1lpkWx2WdWksVHw7BQk6cRzLbsJsNKM:
  74. Timeout during connect (likely firewall problem)
  75.  
  76. Domain: tautulli.Redacteddomain.com
  77. Type: connection
  78. Detail: Fetching
  79. http://tautulli.Redacteddomain.com/.well-known/acme-challenge/-G7RnWnAxLLPNKrkPdIoKf2MQg9SouUsTzh0ks:
  80. Timeout during connect (likely firewall problem)
  81.  
  82. Domain: plex.Redacteddomain.com
  83. Type: connection
  84. Detail: Fetching
  85. http://plex.Redacteddomain.com/.well-known/acme-challenge/0pgozuOkMJ4xtkxP7yTm9hjfTRbdyWvfDPE7k:
  86. Timeout during connect (likely firewall problem)
  87.  
  88. Domain: Redacteddomain.com
  89. Type: connection
  90. Detail: Fetching
  91. http://Redacteddomain.com/.well-known/acme-challenge/xb_BCbxdwFKZxBScjBzv_E_Oc1BPCbTC4:
  92. Timeout during connect (likely firewall problem)
  93.  
  94. Domain: muxi.Redacteddomain.com
  95. Type: connection
  96. Detail: Fetching
  97. http://muxi.Redacteddomain.com/.well-known/acme-challenge/vBXxMVxxx4ngDbgqZs5SSlBgvQIjVdGeQw:
  98. Timeout during connect (likely firewall problem)
  99.  
  100. To fix these errors, please make sure that your domain name was
  101. entered correctly and the DNS A/AAAA record(s) for that domain
  102. contain(s) the right IP address. Additionally, please check that
  103. your computer has a publicly routable IP address and that no
  104. firewalls are preventing the server from communicating with the
  105. client. If you're using the webroot plugin, you should also verify
  106. that you are serving files from the webroot path you provided.
  107. <------------------------------------------------->
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement