Install

Since it doesn't seem like your operating system has a packaged version of Certbot, you should use our certbot-auto script to get a copy:

wget https://dl.eff.org/certbot-auto
chmod a+x certbot-auto

certbot-auto accepts the same flags as certbot; it
installs all of its own
dependencies and updates the client code automatically.

Installing DNS plugins

Certbot's DNS plugins are not available for your OS yet. These
plugins can be used to automate obtaining a wildcard certificate from Let's
Encrypt's ACMEv2 server. This should change soon but if you don't want to wait,
you can use these plugins now by
running Certbot in Docker
instead of using the instructions on this page.

Get Started

Certbot supports a number of different “plugins” that can be used to obtain and/or install certificates.

Since your server architecture doesn't yet support automatic
installation you'll have to use the certonly command to obtain your
certificate.

$ sudo /path/to/certbot-auto certonly

This will allow you interactively select the plugin and options used to obtain
your certificate. If you already have a webserver running, we recommend
choosing the "webroot" plugin.

Alternatively, you can specify more information on the command line.

To obtain a cert using the "webroot" plugin,
which can work with the webroot directory of any webserver software:

This command will obtain a single cert for example.com,
www.example.com, thing.is, and m.thing.is; it will
place files below /var/www/example to prove control of the first two
domains, and under /var/www/thing for the second pair.

Note:

To use the webroot plugin, your server must be configured to serve files from hidden directories. If /.well-known is treated specially by your webserver configuration, you might need to modify the configuration to ensure that files inside /.well-known/acme-challenge are served by the webserver.

To obtain a cert using a built-in “standalone” webserver (you may need to
temporarily stop your existing webserver, if any) for example.com and
www.example.com:

Automating renewal

Certbot can be configured to
renew your certificates automatically before they expire. Since Let's Encrypt
certificates last for 90 days, it's highly advisable to take advantage of this
feature. You can test automatic renewal for your certificates by running this
command:

$ sudo /path/to/certbot-auto renew --dry-run

If that appears to be working correctly, you can arrange for automatic renewal
by adding a cron job or systemd timer which runs the
following:

/path/to/certbot-auto renew

Note:

if you're setting up a cron or systemd job, we
recommend running it twice per day (it won't do anything until your
certificates are due for renewal or revoked, but running it regularly would
give your site a chance of staying online in case a Let's Encrypt-initiated
revocation happened for some reason). Please select a random minute within the
hour for your renewal tasks.

An example cron job might look like this, which will run at noon and midnight every day:

Install

Since it doesn't seem like your operating system has a packaged version of Certbot, you should use our certbot-auto script to get a copy:

wget https://dl.eff.org/certbot-auto
chmod a+x certbot-auto

certbot-auto accepts the same flags as certbot; it
is a wrapper that installs all of its own
dependencies and updates the client code automatically.

Note:

certbot-auto will always try to fetch the newest version of
itself from its most recent release. If you want it to be locked to a
specific version and not receive automatic updates, run it with the
--no-self-upgrade flag. Also, if you're nervous about downloading and
running scripts from the network, some extra verification
steps are available.

Installing DNS plugins

Certbot's DNS plugins are not available for your OS yet. These
plugins can be used to automate obtaining a wildcard certificate from Let's
Encrypt's ACMEv2 server. This should change soon but if you don't want to wait,
you can use these plugins now by
running Certbot in Docker
instead of using the instructions on this page.

Get Started

Certbot supports a number of different “plugins” that can be used to obtain and/or install certificates.

Since your server architecture doesn't yet support automatic
installation you'll have to use the certonly command to obtain your
certificate.

$ sudo /path/to/certbot-auto certonly

This will allow you interactively select the plugin and options used to obtain
your certificate. If you already have a webserver running, we recommend
choosing the "webroot" plugin.

Alternatively, you can specify more information on the command line.

To obtain a cert using the "webroot" plugin,
which can work with the webroot directory of any webserver software:

This command will obtain a single cert for example.com,
www.example.com, thing.is, and m.thing.is; it will
place files below /var/www/example to prove control of the first two
domains, and under /var/www/thing for the second pair.

Note:

To use the webroot plugin, your server must be configured to serve files from hidden directories. If /.well-known is treated specially by your webserver configuration, you might need to modify the configuration to ensure that files inside /.well-known/acme-challenge are served by the webserver.

To obtain a cert using a built-in “standalone” webserver (you may need to
temporarily stop your existing webserver, if any) for example.com and
www.example.com:

Automating renewal

Certbot can be configured to
renew your certificates automatically before they expire. Since Let's Encrypt
certificates last for 90 days, it's highly advisable to take advantage of this
feature. You can test automatic renewal for your certificates by running this
command:

$ sudo /path/to/certbot-auto renew --dry-run

If that appears to be working correctly, you can arrange for automatic renewal
by adding a cron job or systemd timer which runs the
following:

/path/to/certbot-auto renew

Note:

if you're setting up a cron or systemd job, we
recommend running it twice per day (it won't do anything until your
certificates are due for renewal or revoked, but running it regularly would
give your site a chance of staying online in case a Let's Encrypt-initiated
revocation happened for some reason). Please select a random minute within the
hour for your renewal tasks.

An example cron job might look like this, which will run at noon and midnight every day: