API tools faq
paste
Advertisement
tmoflash

LetsEncrypt

tmoflash
Jan 24th, 2019
229
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.40 KB | None | 0 0
raw download clone embed print report
  1. root@WEBSERVER ~ # sudo service apache2 stop
  2. root@WEBSERVER ~ # sudo service nginx stop
  3. root@WEBSERVER ~ # letsencrypt renew
  4. Saving debug log to /var/log/letsencrypt/letsencrypt.log
  5.  
  6. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  7. Processing /etc/letsencrypt/renewal/corinthentertainment.com.conf
  8. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  9. Cert is due for renewal, auto-renewing...
  10. Plugins selected: Authenticator standalone, Installer apache
  11. Running pre-hook command: systemctl stop apache2
  12. Renewing an existing certificate
  13. Performing the following challenges:
  14. tls-sni-01 challenge for corinthentertainment.com
  15. Cleaning up challenges
  16. Attempting to renew cert (corinthentertainment.com) from /etc/letsencrypt/renewal/corinthentertainment.com.conf produced an unexpected error: Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.
  17.  
  18. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  19. Processing /etc/letsencrypt/renewal/plan.corinthmc.com.conf
  20. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  21. Cert not yet due for renewal
  22.  
  23. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  24. Processing /etc/letsencrypt/renewal/21divine.com.conf
  25. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  26. Cert not yet due for renewal
  27.  
  28. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  29. Processing /etc/letsencrypt/renewal/dev.panel.corinthmc.com.conf
  30. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  31. Cert is due for renewal, auto-renewing...
  32. Plugins selected: Authenticator standalone, Installer None
  33. Renewing an existing certificate
  34. Performing the following challenges:
  35. tls-sni-01 challenge for dev.panel.corinthmc.com
  36. Cleaning up challenges
  37. Attempting to renew cert (dev.panel.corinthmc.com) from /etc/letsencrypt/renewal/dev.panel.corinthmc.com.conf produced an unexpected error: Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.
  38.  
  39. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  40. Processing /etc/letsencrypt/renewal/liveyippy.com.conf
  41. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  42. Cert not yet due for renewal
  43.  
  44. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  45. Processing /etc/letsencrypt/renewal/wiki.corinthmc.com.conf
  46. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  47. Cert is due for renewal, auto-renewing...
  48. Plugins selected: Authenticator apache, Installer apache
  49. Renewing an existing certificate
  50. Performing the following challenges:
  51. tls-sni-01 challenge for wiki.corinthmc.com
  52. Waiting for verification...
  53. Cleaning up challenges
  54. Attempting to renew cert (wiki.corinthmc.com) from /etc/letsencrypt/renewal/wiki.corinthmc.com.conf produced an unexpected error: Failed authorization procedure. wiki.corinthmc.com (tls-sni-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Timeout during connect (likely firewall problem). Skipping.
  55.  
  56. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  57. Processing /etc/letsencrypt/renewal/corinthdesigns.com.conf
  58. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  59. Cert not yet due for renewal
  60.  
  61. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  62. Processing /etc/letsencrypt/renewal/mail.corinthmc.com.conf
  63. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  64. Cert not yet due for renewal
  65.  
  66. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  67. Processing /etc/letsencrypt/renewal/git.corinthmc.com.conf
  68. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  69. Cert not yet due for renewal
  70.  
  71. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  72. Processing /etc/letsencrypt/renewal/panel.ftbcorinth.com.conf
  73. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  74. Cert is due for renewal, auto-renewing...
  75. Plugins selected: Authenticator apache, Installer apache
  76. Renewing an existing certificate
  77. Performing the following challenges:
  78. tls-sni-01 challenge for panel.ftbcorinth.com
  79. Waiting for verification...
  80. Cleaning up challenges
  81. Attempting to renew cert (panel.ftbcorinth.com) from /etc/letsencrypt/renewal/panel.ftbcorinth.com.conf produced an unexpected error: Failed authorization procedure. panel.ftbcorinth.com (tls-sni-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Timeout during connect (likely firewall problem). Skipping.
  82.  
  83. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  84. Processing /etc/letsencrypt/renewal/corinthmc.com.conf
  85. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  86. Cert is due for renewal, auto-renewing...
  87. Plugins selected: Authenticator standalone, Installer apache
  88. Pre-hook command already run, skipping: systemctl stop apache2
  89. Renewing an existing certificate
  90. Performing the following challenges:
  91. http-01 challenge for corinthmc.com
  92. Cleaning up challenges
  93. Attempting to renew cert (corinthmc.com) from /etc/letsencrypt/renewal/corinthmc.com.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping.
  94.  
  95. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  96. Processing /etc/letsencrypt/renewal/forum.corinthmc.com.conf
  97. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  98. Cert is due for renewal, auto-renewing...
  99. Plugins selected: Authenticator standalone, Installer apache
  100. Pre-hook command already run, skipping: systemctl stop apache2
  101. Renewing an existing certificate
  102. Performing the following challenges:
  103. http-01 challenge for forum.corinthmc.com
  104. Cleaning up challenges
  105. Attempting to renew cert (forum.corinthmc.com) from /etc/letsencrypt/renewal/forum.corinthmc.com.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping.
  106.  
  107. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  108. Processing /etc/letsencrypt/renewal/beardedrazorback.com.conf
  109. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  110. Cert not yet due for renewal
  111.  
  112. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  113. Processing /etc/letsencrypt/renewal/mh.1.digitalhazards.net.conf
  114. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  115.  
  116. Traceback (most recent call last):
  117. File "/usr/lib/python3/dist-packages/certbot/renewal.py", line 64, in _reconstitute
  118. renewal_candidate = storage.RenewableCert(full_path, config)
  119. File "/usr/lib/python3/dist-packages/certbot/storage.py", line 439, in __init__
  120. self._check_symlinks()
  121. File "/usr/lib/python3/dist-packages/certbot/storage.py", line 498, in _check_symlinks
  122. "expected {0} to be a symlink".format(link))
  123. certbot.errors.CertStorageError: expected /etc/letsencrypt/live/mh.1.digitalhazards.net/cert.pem to be a symlink
  124. Renewal configuration file /etc/letsencrypt/renewal/mh.1.digitalhazards.net.conf is broken. Skipping.
  125.  
  126. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  127. Processing /etc/letsencrypt/renewal/blog.corinthmc.com.conf
  128. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  129. Cert is due for renewal, auto-renewing...
  130. Plugins selected: Authenticator standalone, Installer apache
  131. Pre-hook command already run, skipping: systemctl stop apache2
  132. Renewing an existing certificate
  133. Performing the following challenges:
  134. tls-sni-01 challenge for blog.corinthmc.com
  135. Cleaning up challenges
  136. Attempting to renew cert (blog.corinthmc.com) from /etc/letsencrypt/renewal/blog.corinthmc.com.conf produced an unexpected error: Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.
  137.  
  138. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  139. Processing /etc/letsencrypt/renewal/theord.com.conf
  140. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  141. Cert not yet due for renewal
  142.  
  143. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  144. Processing /etc/letsencrypt/renewal/panel.corinthmc.com.conf
  145. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  146. Cert not yet due for renewal
  147.  
  148. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  149. Processing /etc/letsencrypt/renewal/nicandjake.com.conf
  150. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  151. Cert not yet due for renewal
  152.  
  153. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  154. Processing /etc/letsencrypt/renewal/beingsofstrange.com.conf
  155. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  156. Cert not yet due for renewal
  157.  
  158. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  159. Processing /etc/letsencrypt/renewal/jacobkern.com.conf
  160. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  161. Cert not yet due for renewal
  162. All renewal attempts failed. The following certs could not be renewed:
  163. /etc/letsencrypt/live/corinthentertainment.com/fullchain.pem (failure)
  164. /etc/letsencrypt/live/dev.panel.corinthmc.com/fullchain.pem (failure)
  165. /etc/letsencrypt/live/wiki.corinthmc.com/fullchain.pem (failure)
  166. /etc/letsencrypt/live/panel.ftbcorinth.com/fullchain.pem (failure)
  167. /etc/letsencrypt/live/corinthmc.com/fullchain.pem (failure)
  168. /etc/letsencrypt/live/forum.corinthmc.com/fullchain.pem (failure)
  169. /etc/letsencrypt/live/blog.corinthmc.com/fullchain.pem (failure)
  170.  
  171. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  172.  
  173. The following certs are not due for renewal yet:
  174. /etc/letsencrypt/live/plan.corinthmc.com/fullchain.pem expires on 2019-03-09 (skipped)
  175. /etc/letsencrypt/live/21divine.com/fullchain.pem expires on 2019-04-16 (skipped)
  176. /etc/letsencrypt/live/liveyippy.com/fullchain.pem expires on 2019-04-19 (skipped)
  177. /etc/letsencrypt/live/corinthdesigns.com/fullchain.pem expires on 2019-04-07 (skipped)
  178. /etc/letsencrypt/live/mail.corinthmc.com/fullchain.pem expires on 2019-03-12 (skipped)
  179. /etc/letsencrypt/live/git.corinthmc.com/fullchain.pem expires on 2019-04-02 (skipped)
  180. /etc/letsencrypt/live/beardedrazorback.com/fullchain.pem expires on 2019-03-10 (skipped)
  181. /etc/letsencrypt/live/theord.com/fullchain.pem expires on 2019-03-10 (skipped)
  182. /etc/letsencrypt/live/panel.corinthmc.com/fullchain.pem expires on 2019-04-18 (skipped)
  183. /etc/letsencrypt/live/nicandjake.com/fullchain.pem expires on 2019-03-11 (skipped)
  184. /etc/letsencrypt/live/beingsofstrange.com/fullchain.pem expires on 2019-03-29 (skipped)
  185. /etc/letsencrypt/live/jacobkern.com/fullchain.pem expires on 2019-04-06 (skipped)
  186. All renewal attempts failed. The following certs could not be renewed:
  187. /etc/letsencrypt/live/corinthentertainment.com/fullchain.pem (failure)
  188. /etc/letsencrypt/live/dev.panel.corinthmc.com/fullchain.pem (failure)
  189. /etc/letsencrypt/live/wiki.corinthmc.com/fullchain.pem (failure)
  190. /etc/letsencrypt/live/panel.ftbcorinth.com/fullchain.pem (failure)
  191. /etc/letsencrypt/live/corinthmc.com/fullchain.pem (failure)
  192. /etc/letsencrypt/live/forum.corinthmc.com/fullchain.pem (failure)
  193. /etc/letsencrypt/live/blog.corinthmc.com/fullchain.pem (failure)
  194.  
  195. Additionally, the following renewal configuration files were invalid:
  196. /etc/letsencrypt/renewal/mh.1.digitalhazards.net.conf (parsefail)
  197. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  198. Running post-hook command: systemctl start apache2
  199. Running post-hook command: systemctl restart apache2
  200. 7 renew failure(s), 1 parse failure(s)
  201.  
  202. IMPORTANT NOTES:
  203. - The following errors were reported by the server:
  204.  
  205. Domain: panel.ftbcorinth.com
  206. Type: connection
  207. Detail: Timeout during connect (likely firewall problem)
  208.  
  209. To fix these errors, please make sure that your domain name was
  210. entered correctly and the DNS A/AAAA record(s) for that domain
  211. contain(s) the right IP address. Additionally, please check that
  212. your computer has a publicly routable IP address and that no
  213. firewalls are preventing the server from communicating with the
  214. client. If you're using the webroot plugin, you should also verify
  215. that you are serving files from the webroot path you provided.
  216. - The following errors were reported by the server:
  217.  
  218. Domain: wiki.corinthmc.com
  219. Type: connection
  220. Detail: Timeout during connect (likely firewall problem)
  221.  
  222. To fix these errors, please make sure that your domain name was
  223. entered correctly and the DNS A/AAAA record(s) for that domain
  224. contain(s) the right IP address. Additionally, please check that
  225. your computer has a publicly routable IP address and that no
  226. firewalls are preventing the server from communicating with the
  227. client. If you're using the webroot plugin, you should also verify
  228. that you are serving files from the webroot path you provided.
  229. root@WEBSERVER ~ # sudo service apache2 start
  230. root@WEBSERVER ~ # sudo service nginx start
  231. Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.
  232. root@WEBSERVER ~ #
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!