isp-almo.almo.gq Open in urlscan Pro
2606:4700:3035::6815:5677  Public Scan

Form analysis
1 forms found in the DOM

GET /instructions

<form action="/instructions" accept-charset="UTF-8" data-remote="true" method="get">
  <span>My HTTP website is running</span>
  <select name="ws" id="ws">
    <option value="">Software</option>
    <option value="apache">Apache</option>
    <option value="nginx">Nginx</option>
    <option value="haproxy">HAProxy</option>
    <option value="plesk">Plesk</option>
    <option value="other">Other</option>
    <option value="webproduct">Web Hosting Product</option>
  </select>
  <span>on</span>
  <select name="os" id="os">
    <option value="">System</option>
    <option value="bitnami">Bitnami</option>
    <option value="pip">Pip</option>
    <option value="gentoo">Gentoo</option>
    <option value="fedora">Fedora</option>
    <option value="freebsd">FreeBSD</option>
    <option value="windows">Windows</option>
    <option value="snap">Snapd</option>
    <option value="debianstretch">Debian 9</option>
    <option value="debianbuster">Debian 10</option>
    <option value="debiantesting">Debian Testing</option>
    <option value="ubuntufocal">Ubuntu 20</option>
    <option value="ubuntuother">Ubuntu 19</option>
    <option value="ubuntubionic">Ubuntu 18</option>
    <option value="ubuntuxenial">Ubuntu 16</option>
    <option value="arch">Arch Linux</option>
    <option value="centosrhel8">CentOS 8</option>
    <option value="centosrhel7">CentOS 7</option>
    <option value="opbsd6">OpenBSD</option>
    <option value="osx">macOS</option>
    <option value="devuanascii">Devuan 2.0</option>
    <option value="devuanbeowulf">Devuan 3.0</option>
    <option value="devuanother">Devuan Testing</option>
    <option value="tumbleweed">openSUSE tumbleweed</option>
    <option value="leap">openSUSE 15</option>
    <option value="sharedhost">Web Hosting Service</option>
  </select>
</form>

Text Content

Skip to main content
a project of the Electronic Frontier Foundation
 * EN
 * فارسی

 * certbot instructions
 * about certbot
 * contribute to certbot
 * hosting providers with HTTPS
 * get help
 * donate
 * donate to EFF
 * ≡

 * home
 * certbot instructions
 * about certbot
 * contribute to certbot
 * hosting providers with HTTPS
 * get help
 * donate
 * ×


GET YOUR SITE ON HTTPS://


FIND OUT IF YOUR HOSTING PROVIDER HAS HTTPS BUILT IN — NO CERTBOT NEEDED.

See the list of providers


SEE IF YOUR HOSTING PROVIDER OFFERS HTTPS.


OR, RUN CERTBOT ONCE TO AUTOMATICALLY GET FREE HTTPS CERTIFICATES FOREVER.

Get Certbot instructions


OR, GET INSTRUCTIONS FOR CERTBOT.


WHAT'S YOUR HTTP WEBSITE RUNNING ON?

My HTTP website is running SoftwareApache Nginx HAProxy Plesk Other Web Hosting
Product on SystemBitnami Pip Gentoo Fedora FreeBSD Windows Snapd Debian 9 Debian
10 Debian Testing Ubuntu 20 Ubuntu 19 Ubuntu 18 Ubuntu 16 Arch Linux CentOS 8
CentOS 7 OpenBSD macOS Devuan 2.0 Devuan 3.0 Devuan Testing openSUSE tumbleweed
openSUSE 15 Web Hosting Service
Help, I'm not sure!

Use our instruction generator to find custom commands to get Certbot on your
server's environment. Pick your server's software and system above.


TO USE CERTBOT, YOU'LL NEED...

comfort with the
command line
Command Line

A command line is a way of interacting with a computer by typing text-based
commands to it and receiving text-based replies. Certbot is run from a
command-line interface, usually on a Unix-like server. In order to use Certbot
for most purposes, you’ll need to be able to install and run it on the command
line of your web server, which is usually accessed over SSH.

A command line is a way of interacting with a computer by typing text-based
commands to it and recei...

From our Certbot Glossary
...and an
HTTP website
HTTP

HTTP (Hypertext Transfer Protocol) is the traditional, but insecure, method for
web browsers to request the content of web pages and other online resources from
web servers. It is an Internet standard and normally used with TCP port 80.
Almost all websites in the world support HTTP, but websites that have been
configured with Certbot or some other method of setting up HTTPS may
automatically redirect users from the HTTP version of the site to the HTTPS
version.

HTTP (Hypertext Transfer Protocol) is the traditional, but insecure, method for
web browsers to requ...

From our Certbot Glossary

that is
already online
Website That’s Already Online

Certbot is usually meant to be used to switch an existing HTTP site to work in
HTTPS (and, afterward, to continue renewing the site’s HTTPS certificates
whenever necessary). Some Certbot documentation assumes or recommends that you
have a working web site that can already be accessed using HTTP on port 80. That
means, for example, that if you use a web browser to go to your domain using
http://, your web server answers and some kind of content comes up (even if it’s
just a default welcome page rather than the final version of your site). Some
methods of using Certbot have this as a prerequisite, so you’ll have a smoother
experience if you already have a site set up with HTTP. (If your site can’t be
accessed this way as a matter of policy, you’ll probably need to use DNS
validation in order to get a certificate with Certbot.)

Certbot is usually meant to be used to switch an existing HTTP site to work in
HTTPS (and, afterward...

From our Certbot Glossary

with an open
port 80
Port 80

Different Internet services are distinguished by using different TCP port
numbers. Unencrypted HTTP normally uses TCP port 80, while encrypted HTTPS
normally uses TCP port 443. To use certbot --webroot, certbot --apache, or
certbot --nginx, you should have an existing HTTP website that’s already online
hosted on the server where you’re going to use Certbot. This site should be
available to the rest of the Internet on port 80. To use certbot --standalone,
you don’t need an existing site, but you have to make sure connections to port
80 on your server are not blocked by a firewall, including a firewall that may
be run by your Internet service provider or web hosting provider. Please check
with your ISP or hosting provider if you’re not sure. (Using DNS validation does
not require Let’s Encrypt to make any inbound connection to your server, so with
this method in particular it’s not necessary to have an existing HTTP website or
the ability to receive connections on port 80.)

Different Internet services are distinguished by using different TCP port
numbers. Unencrypted HTTP ...

From our Certbot Glossary
...which is hosted on a
server
Server

A server is a computer on the Internet that provides a service, like a web site
or an email service. Most web site owners pay a hosting provider for the use of
a server located in a data center and administered over the Internet. This might
be a physical dedicated server, a virtual private server (VPS), or a shared
server. Other servers provide other parts of the Internet infrastructure, such
as DNS servers.

A server is a computer on the Internet that provides a service, like a web site
or an email service....

From our Certbot Glossary

which you can access via
ssh
SSH

SSH (which stands for “secure shell”) is a technology for connecting to a remote
server and accessing a command line on that server, often in order to administer
it. The administrator of a server can grant SSH access to others, and can also
use SSH access directly in order to administer the server remotely. SSH is
usually used to access servers running Unix-like operating systems, but your own
computer doesn’t have to be running Unix in order to use SSH. You normally use
SSH from your computer’s command line in a terminal by typing a command such as
ssh username@example.com, especially if your own computer runs Linux or macOS.
After logging in, you’ll have access to the server’s command line. If you use
Windows on your computer, you might also use a dedicated SSH application such as
PuTTY. Most Certbot users run Certbot from a command prompt on a remote server
over SSH.

SSH (which stands for “secure shell”) is a technology for connecting to a remote
server and accessin...

From our Certbot Glossary

with the ability to
sudo
sudo

Sudo is the most common command on Unix-like operating systems to run a specific
command as root (the system administrator). If you’re logged in to your server
as a user other than root, you’ll likely need to put sudo before your Certbot
commands so that they run as root (for example, sudo certbot instead of just
certbot), especially if you’re using Certbot’s integration with a web server
like Apache or Nginx. (The certbot-auto script automatically runs sudo if it’s
necessary and you didn’t specify it.)

Sudo is the most common command on Unix-like operating systems to run a specific
command as root (th...

From our Certbot Glossary

optional if you want a
wildcard cert
Wildcard Certificate

A wildcard certificate is a certificate that includes one or more names starting
with *.. Browsers will accept any label in place of the asterisk (*). For
example, a certificate for *.example.com will be valid for www.example.com,
mail.example.com, hello.example.com, and goodbye.example.com.

However, a wildcard certificate including only the name *.example.com will not
be valid for example.com: the substituted label can not be empty. If you want
the certificate to be valid for example.com, you also need to include
example.com (i.e. without the *. part) on the certificate.

Additionally, the asterisk can only be substituted by a single label and not by
multiple labels. For example, the name hello.goodbye.example.com will not be
covered by a certificate including only the name *.example.com. It will be
covered however, by *.goodbye.example.com. Note that a wildcard name can not
contain multiple asterisks. For example, *.*.example.com is not valid.

A wildcard certificate is a certificate that includes one or more names starting
with *.. Browsers w...

From our Certbot Glossary
:
DNS credentials
DNS Credentials

DNS credentials are a password or other kind of secret (such as an API key) that
your DNS provider lets you use to change the contents of your DNS records. They
are usually issued by your domain registrar (or by another DNS provider, if your
DNS provider isn’t the same as your registrar). DNS credentials are a sensitive
kind of secret because they can be used to take over your site completely. You
should never share these credentials publicly or with an unauthorized person. It
can be OK to provide a copy of them to Certbot to let it perform DNS validation
automatically, since it runs locally on your machine.

DNS credentials are a password or other kind of secret (such as an API key) that
your DNS provider l...

From our Certbot Glossary


DON'T HAVE THESE REQUIREMENTS?

Not to worry! Some hosting providers automate the HTTPS process. See the full
list of hosting providers , or find out more about how to set up your system.

Want to learn more? See our explainers
Want to contribute to Certbot? See opportunites to help
 * 
 * 
 * 

certbot
 * home
 * about certbot
 * certbot instructions
 * hosting providers with HTTPS

 * get help
 * frequently asked questions
 * certbot glossary
 * certbot documentation
 * community forum

 * contact us
 * contribute to certbot

 * donate to EFF

 * privacy
 *