Certbot - Revision history

Scott at 16:22, 7 January 2021

2021-01-07T16:22:18Z

← Older revision		Revision as of 16:22, 7 January 2021
Line 37:		Line 37:
	* Now run a command like this:		* Now run a command like this:
	<pre>		<pre>
	certbot certonly --webroot --webroot-path=/var/www/html \		certbot certonly --webroot --webroot-path=/var/www/html -d domain1.example.com
	~~-d example.com \~~
	-d domain1~~.example.com \~~
	~~-d domain2~~.example.com
	</pre>		</pre>
	You should get some output about where the ssl cert and key are located.		You should get some output about where the ssl cert and key are located.

2020-03-09T18:52:15Z

Troubleshooting

← Older revision		Revision as of 18:52, 9 March 2020
Line 68:		Line 68:

	== Troubleshooting ==		== Troubleshooting ==
	If things get messed up, delete the offending certificate with the <code>certbot delete</code> command and ~~then~~ start over. '''DO NOT''' attempt to fix things manually. You'll just end up with a bigger mess.		If things get messed up, delete the offending certificate with the <code>certbot delete</code> command and choose the offending URL from the list. Then start over. '''DO NOT''' attempt to fix things manually. You'll just end up with a bigger mess.

2019-03-20T18:00:44Z

← Older revision		Revision as of 18:00, 20 March 2019
Line 26:		Line 26:
	</pre>		</pre>

	* Include the following line in the ~~ssl~~ config for each domain:		* Include the following line in the config for each domain:
	<pre>		<pre>
	include snippets/ssl-certbot.conf;		include snippets/ssl-certbot.conf;
Line 63:		Line 63:
	sudo certbot renew --dry-run		sudo certbot renew --dry-run
	</pre>		</pre>

			== Wisdom ==
			* If the site is currently working with <code>http</code>, just add the certbot snippet to the '''existing''' config and run the certbot command to create the SSL cert/chain first. THEN redo the entire config as SSL.

	== Troubleshooting ==		== Troubleshooting ==
	If things get messed up, delete the offending certificate with the <code>certbot delete</code> command and then start over. '''DO NOT''' attempt to fix things manually. You'll just end up with a bigger mess.		If things get messed up, delete the offending certificate with the <code>certbot delete</code> command and then start over. '''DO NOT''' attempt to fix things manually. You'll just end up with a bigger mess.

2019-02-13T23:10:22Z

← Older revision		Revision as of 23:10, 13 February 2019
Line 63:		Line 63:
	sudo certbot renew --dry-run		sudo certbot renew --dry-run
	</pre>		</pre>

			== Troubleshooting ==
			If things get messed up, delete the offending certificate with the <code>certbot delete</code> command and then start over. '''DO NOT''' attempt to fix things manually. You'll just end up with a bigger mess.

2018-11-29T20:01:25Z

← Older revision		Revision as of 20:01, 29 November 2018
Line 59:		Line 59:
	* More SSL config advice here: https://mozilla.github.io/server-side-tls/ssl-config-generator/		* More SSL config advice here: https://mozilla.github.io/server-side-tls/ssl-config-generator/

	* Test with this:		* Test automated certificate renewal with this:
	<pre>		<pre>
	sudo certbot renew --dry-run		sudo certbot renew --dry-run
	</pre>		</pre>

2018-11-29T19:59:45Z

2018-11-29T19:59:12Z

@@ Line 40: / Line 40: @@
 -d domain2.example.com
 </pre>
 * Test with this:

2018-11-29T19:31:19Z

← Older revision		Revision as of 19:31, 29 November 2018
Line 12:		Line 12:
	</pre>		</pre>

	* Create the file <code>/etc/nginx/snippets/ssl-certbot~~-renewal~~.conf</code>:		* Create the file <code>/etc/nginx/snippets/ssl-certbot.conf</code>:
	<pre>		<pre>
	# support for certbot ssl auto-renewal		# support for certbot ssl auto-renewal
Line 28:		Line 28:
	* Include the following line in the ssl config for each domain:		* Include the following line in the ssl config for each domain:
	<pre>		<pre>
	include snippets/ssl-certbot~~-renewal~~.conf;		include snippets/ssl-certbot.conf;
	</pre>		</pre>

2018-11-29T19:28:13Z

← Older revision		Revision as of 19:28, 29 November 2018
Line 19:		Line 19:
	root /var/www/html/;		root /var/www/html/;
	}		}
			</pre>

			* Create the well-known directory for verification:
			<pre>
			mkdir -p /var/www/html/.well-known
	</pre>		</pre>

2018-04-19T18:30:10Z

← Older revision		Revision as of 18:30, 19 April 2018
Line 3:		Line 3:
	https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04		https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04

	~~The~~ <code>certbot</code> connects to Let's Encrypt to obtain an SSL certificate for your server.		<code>certbot</code> connects to Let's Encrypt to obtain an SSL certificate for your server.

	* Install packages		* Install packages