Certbot - Revision history

Timon: typo

2023-01-29T15:06:48Z

typo

← Older revision		Revision as of 15:06, 29 January 2023
Line 3:		Line 3:
	== Install ==		== Install ==

	=== Snap-Store ===		=== Snap Store ===
	This is the install method advised by LetsEncrypt.		This is the install method advised by LetsEncrypt.

Timon: Add Apt & Apk install and also fix spelling

2023-01-29T15:06:25Z

Add Apt & Apk install and also fix spelling

← Older revision		Revision as of 15:06, 29 January 2023
Line 1:		Line 1:
	The Certbot is used the issue LetsEncrypt SSL-Certificates		The Certbot is used the issue LetsEncrypt SSL-Certificates.

	== Install ==		== Install ==
	~~Certbot '''must''' installed using the Snap-Store.~~

	~~Make sure~~ the ~~certbot is not installed using Apt:~~		=== Snap-Store ===
			This is the install method advised by LetsEncrypt.

	<code>sudo apt remove certbot</code>		Make sure the certbot is not installed using Apt: <code>sudo apt remove certbot</code>.

	Ensure the latest Snap version is installed:		Ensure the latest Snap version is installed: <code>sudo snap install core; sudo snap refresh core</code>.

	<code>sudo snap install ~~core; sudo snap refresh core~~</code>		Install the Certbot, make sure to use the <code>--classic</code> flag: <code>sudo snap install --classic certbot</code>.

	~~Install~~ the ~~Certbot, make sure~~ to ~~use~~ the <code>-~~-classic~~</code> ~~flag~~		Link the certbot binary to a path thats in the $PATH variabel: <code>sudo ln -s /snap/bin/certbot /usr/bin/certbot</code>. Depending on your environment this might not be necessary.

	~~<code>sudo snap install --classic~~ certbot~~</code>~~		=== Apt & Apk ===
			The certbot is also available in the officiall Debian, Ubuntu & Alpine repositories, but the version might be outdated.

	~~Link the~~ certbot ~~binary to a path thats in the $PATH variabel~~		* Ubuntu & Debian: <code>apt install certbot</code>
			* Alpine: <code>apk install certbot</code>
	<code>~~sudo ln -s /snap/bin/certbot /usr/bin/~~certbot</code>

	== Retrieving a Certificate ==		== Retrieving a Certificate ==
Line 40:		Line 40:
	<code>sudo certbot renew --nginx --agree-tos -n</code>		<code>sudo certbot renew --nginx --agree-tos -n</code>

	* <code>--nginx</code>: Use ~~Local~~ installed nginx for the ~~Authentication-Challange, see Challanges~~ for other ways to authenticate		* <code>--nginx</code>: Use a locally installed nginx for the authentication challange. See [[Certbot#Challenges\|Challenges]] for other ways to authenticate
	* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option		* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option
	* <code>-n</code>: Non-Interactive, do not prompt for anything		* <code>-n</code>: Non-Interactive, do not prompt for anything
Line 47:		Line 47:
	Certificates will be updated if there expire in less than 30 days		Certificates will be updated if there expire in less than 30 days

	== ~~Challanges~~ ==		== Challenges ==
	To validate that you own a Domain you must complete a ~~Challange~~ using one of the following method		To validate that you own a Domain you must complete a challange using one of the following method:

	=== Nginx ===		=== Nginx ===

Timon: /* Retriving a Certificate */

2021-12-06T20:53:18Z

Retriving a Certificate

← Older revision		Revision as of 20:53, 6 December 2021
Line 20:		Line 20:
	<code>sudo ln -s /snap/bin/certbot /usr/bin/certbot</code>		<code>sudo ln -s /snap/bin/certbot /usr/bin/certbot</code>

	== ~~Retriving~~ a Certificate ==		== Retrieving a Certificate ==
	To create an Certificate for <code>example.com</code>		To create an Certificate for <code>example.com</code>

Timon: Created page with "The Certbot is used the issue LetsEncrypt SSL-Certificates == Install == Certbot '''must''' installed using the Snap-Store. Make sure the certbot is not installed using Apt: `sudo apt remove certbot` Ensure the latest Snap version is installed: `sudo snap install core; sudo snap refresh core` Install the Certbot, make sure to use the `--classic` flag `sudo snap install --classic certbot` Link the certbot binary to a pat..."

2021-12-06T20:52:58Z

Created page with "The Certbot is used the issue LetsEncrypt SSL-Certificates == Install == Certbot '''must''' installed using the Snap-Store. Make sure the certbot is not installed using Apt: <code>sudo apt remove certbot</code> Ensure the latest Snap version is installed: <code>sudo snap install core; sudo snap refresh core</code> Install the Certbot, make sure to use the <code>--classic</code> flag <code>sudo snap install --classic certbot</code> Link the certbot binary to a pat..."

New page

The Certbot is used the issue LetsEncrypt SSL-Certificates

== Install ==
Certbot '''must''' installed using the Snap-Store.

Make sure the certbot is not installed using Apt:

<code>sudo apt remove certbot</code>

Ensure the latest Snap version is installed:

<code>sudo snap install core; sudo snap refresh core</code>

Install the Certbot, make sure to use the <code>--classic</code> flag

<code>sudo snap install --classic certbot</code>

Link the certbot binary to a path thats in the $PATH variabel

<code>sudo ln -s /snap/bin/certbot /usr/bin/certbot</code>

== Retriving a Certificate ==
To create an Certificate for <code>example.com</code>

<code>sudo certbot certonly --nginx --agree-tos -n -d example.com</code>

* <code>--nginx</code>: Use Local installed nginx for the Authentication-Challange, see Challanges for other ways to authenticate
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option
* <code>-n</code>: Non-Interactive, do not prompt for anything
* <code>-d <DOMAIN></code>: Domain to create the Certificate for

The Certificate will be saved under:

* <code>/etc/letsencrypt/live/<DOMAIN>/fullchain.pem</code>: Certificate
* <code>/etc/letsencrypt/live/<DOMAIN>/privkey.pem</code>: Private key

== Renewing Certificates ==
To renew all Certificates use:

<code>sudo certbot renew --nginx --agree-tos -n</code>

* <code>--nginx</code>: Use Local installed nginx for the Authentication-Challange, see Challanges for other ways to authenticate
* <code>--agree-tos</code>: Agree to the Terms of Service, the Command will not work without this option
* <code>-n</code>: Non-Interactive, do not prompt for anything
* <code>-d <DOMAIN></code>: Optional, Domain to renew the Certificate for

Certificates will be updated if there expire in less than 30 days

== Challanges ==
To validate that you own a Domain you must complete a Challange using one of the following method

=== Nginx ===
If a Nginx is running localy and serving for your domain you can simply use the <code>--nginx</code> option and certbot will use Nginx for the Challange and should complete it without stopping the Nginx.

=== Apache ===
If a Apache is running localy and serving for your domain you can simply use the <code>--apache</code> option and certbot will use Apache for the Challange and should complete it without stopping the Apache server.

=== Standalone ===
Certbot will start a Webserver on Port 80 and will try to serve a file containg a verification code. If the Certbot can find that file, the challange will be completed.

=== Webroot ===
Using the <code>--webroot <Path></code> the Certbot will put files under the given directory und the given directory and try to access them.