diff --git a/.github/workflows/assigned.yaml b/.github/workflows/assigned.yaml
new file mode 100644
index 000000000..f365067ce
--- /dev/null
+++ b/.github/workflows/assigned.yaml
@@ -0,0 +1,14 @@
+name: Issue Assigned
+
+on:
+ issues:
+ types: [assigned]
+jobs:
+ send-mattermost-message:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: mattermost/action-mattermost-notify@master
+ with:
+ MATTERMOST_WEBHOOK_URL: ${{ secrets.MATTERMOST_ASSIGN_WEBHOOK }}
+ TEXT: >
+ ${{ github.event.assignee.login }} assigned to "${{ github.event.issue.title }}": ${{ github.event.issue.html_url }}
diff --git a/.github/workflows/review_requested.yaml b/.github/workflows/review_requested.yaml
new file mode 100644
index 000000000..1d71acba7
--- /dev/null
+++ b/.github/workflows/review_requested.yaml
@@ -0,0 +1,16 @@
+name: Review Requested
+
+on:
+ pull_request_target:
+ types: [review_requested]
+jobs:
+ send-mattermost-message:
+ # Don't notify for the interim step of certbot/eff-devs being assigned
+ if: ${{ github.event.requested_reviewer.login != ''}}
+ runs-on: ubuntu-latest
+ steps:
+ - uses: mattermost/action-mattermost-notify@master
+ with:
+ MATTERMOST_WEBHOOK_URL: ${{ secrets.MATTERMOST_ASSIGN_WEBHOOK }}
+ TEXT: >
+ Review requested from ${{ github.event.requested_reviewer.login }} for "${{ github.event.pull_request.title }}": ${{ github.event.pull_request.html_url }}
diff --git a/.gitignore b/.gitignore
index 3d31a6c3d..88a8f4eed 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,5 +1,8 @@
_site
.jekyll-metadata
+.jekyll-cache
.sass-cache
node_modules
_instructions/
+build
+watch
diff --git a/.gitmodules b/.gitmodules
deleted file mode 100644
index 18bee710f..000000000
--- a/.gitmodules
+++ /dev/null
@@ -1,4 +0,0 @@
-[submodule "_docs"]
- path = _docs
- url = https://github.com/certbot/certbot.git
- branch = master
diff --git a/.travis.yml b/.travis.yml
deleted file mode 100644
index e9f8bc50a..000000000
--- a/.travis.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-language: node_js
-dist: focal
-node_js:
- - 8.12.0
-
-addons:
- apt:
- packages:
- - gsfonts
- - imagemagick
- - latexmk
- - texlive
- - texlive-latex-extra
-
-before_install:
- - rvm install 2.6.3
-
-install:
- - npm install gulp
- - npm install
- - gem install jekyll
- - gem install html-proofer
- - ./_docs.sh depend
-
-script:
- - gulp build
- - npm test
-
-after_success:
- - 'if [[ $TRAVIS_PULL_REQUEST == "false" && $TRAVIS_REPO_SLUG == "certbot/website" ]]; then bash ./push-build.sh; fi'
-
-env:
- global:
- # speeds up installation of html-proofer
- - NOKOGIRI_USE_SYSTEM_LIBRARIES=true
- - NODE_ENV=production
-
-sudo: required
-
-notifications:
- email: false
- irc:
- if: branch = master
- channels:
- # This is set to a secure variable to prevent forks from sending
- # notifications. This value was created by installing
- # https://github.com/travis-ci/travis.rb and running
- # `travis encrypt "chat.freenode.net#certbot-devel"`.
- - secure: "m8jEd5hCZxGRK1xUnU7JIx8o/I/gZPlHNpFPZh9fJlHDe4yWnatLR9xqkpf3qerTXD1pSl0om4M+BYfOZCJVxUeb5PH1qyW6a3RyMi+siuUwJv6PbvveNmuDGD8gMCARzyuhB0jZx5QvDpTDaSiY5BDfr9nI5JcZJwq4ecSVoSUleGJK5Dx0ngmp5ERSXpZhBGJpVqz0VZ32j/dNGQdZlTlAJM18i6lQiYUK4lZTkwQ5YcBjSjWrZEfTCyGja7YH1tz5b6XyPONB2u4iqYEs9N+jKVZwX8kg5yLCxEt2C7phJwDufiLtLly3en6iVt1IB25AfIdiLIJWSj0LFCwRT/f96/z9ayzeBWtTK/Q1guKaYHzNodjzWxhLMESyg5BQ+LZQm0pWqRIyrV+UFvdbv6UnbGckfPw4MLfIf4+GUuTa3CxL9vuzQQw/8euZcWDCxw6f8bZpHyMRhiBCh64CI1D1CKoHX5/jTbQ5hnxjmr5vijOtZMJZNPuLjK0BdDoJUPE9JH0ngJ7hIHanaxbRYs4XzXUSY0ZipynW5M+XkfpJqbB1i29+96s6pThXDS09FHy5pwHqkGlNJs2YdBGWm3h1CSHa+tUUy5WtO9tns6HDGgGthAKcs5YA62kwGzNYldpt4c3JyLbUQ31ct04tJZ/H6/k5VUeUr82OYfRSumE="
- on_success: never
diff --git a/Dockerfile b/Dockerfile
deleted file mode 100644
index a2334f040..000000000
--- a/Dockerfile
+++ /dev/null
@@ -1,71 +0,0 @@
-FROM node:8
-
-RUN mkdir /opt/certbot
-WORKDIR /opt/certbot
-
-ENV NODE_ENV production
-ENV RUBY_VERSION 2.6.3
-ENV NOKOGIRI_USE_SYSTEM_LIBRARIES true
-
-# Set UTF-8 character encoding
-RUN apt-get update && apt-get install locales -y
-RUN echo dpkg-reconfigure -f noninteractive tzdata && \
- sed -i -e 's/# en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /etc/locale.gen && \
- echo 'LANG="en_US.UTF-8"'>/etc/default/locale && \
- dpkg-reconfigure --frontend=noninteractive locales && \
- update-locale LANG=en_US.UTF-8
-ENV LANG en_US.UTF-8
-ENV LANGUAGE en_US:en
-ENV LC_ALL C.UTF-8
-
-# need rsync for deploy script and texlive for building docs
-RUN apt-get install -y --no-install-recommends \
- imagemagick \
- gsfonts \
- latexmk \
- rsync \
- sudo \
- texlive \
- texlive-latex-extra
-
-# Install ruby and dependencies
-RUN echo 'gem: --no-document' >> /usr/local/etc/gemrc &&\
- mkdir /src && cd /src && git clone https://github.com/sstephenson/ruby-build.git &&\
- cd /src/ruby-build && ./install.sh &&\
- cd / && rm -rf /src/ruby-build && ruby-build $RUBY_VERSION /usr/local
-RUN gem install jekyll html-proofer
-
-# Install docs dependencies
-COPY _docs/ ./_docs
-COPY _docs.sh ./
-RUN ./_docs.sh depend
-
-# Install js dependencies
-COPY package.json ./
-RUN npm install gulp-cli -g
-RUN npm install
-
-COPY _data ./_data
-COPY _faq_entries ./_faq_entries
-COPY _gulp ./_gulp
-COPY _includes ./_includes
-COPY _layouts ./_layouts
-COPY _sass ./_sass
-COPY _scripts ./_scripts
-COPY about ./about
-COPY faq ./faq
-COPY fonts ./fonts
-COPY images ./images
-COPY privacy ./privacy
-COPY support ./support
-COPY _config.yml ./_config.yml
-COPY favicon.ico ./favicon.ico
-COPY gulpfile.js ./gulpfile.js
-COPY index.html ./index.html
-COPY certbot-deploy ./certbot-deploy
-COPY .git ./.git
-COPY .gitmodules ./.gitmodules
-
-RUN gulp build
-
-CMD ["gulp", "jekyll:watch"]
diff --git a/EDITING.md b/EDITING.md
deleted file mode 100644
index fc5f0ccd6..000000000
--- a/EDITING.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Editing the Certbot instructions
-Certbot instructions are available for editing as part of the https://github.com/certbot/website repository - if you've found an error or generally think that you can improve them we welcome your support!
-## Source Files
-The files for the instruction generator are in https://github.com/certbot/website/tree/master/_scripts/instruction-widget
-
-They're mostly determined by the template files in the [templates directory](https://github.com/certbot/website/tree/master/_scripts/instruction-widget/templates) which are made up of HTML and [mustache.js template](https://mustache.github.io/) commands.
-
-Some of the text is set through javascript which can be found [here](https://github.com/certbot/website/blob/master/_scripts/instruction-widget/install.js)
-
-## Editing
-Most text is determined by by the HTML in the template files. To edit them you'll need a basic understanding of HTML.
-
-Anything inside of `{{ example_text }}` is a mustache.js template - which documentation can be read about [here](https://mustache.github.io/mustache.5.html).
-
-Certain variables, such as the specific command to invoke certbot, are determined in `install.js` and `getting-started.js` and are set as context elements to go along with the ones determined by the drop down options (defined [here](https://github.com/certbot/website/blob/master/_scripts/instruction-widget/data/inputs.json)).
-
-These allow you to change certain text selectively based on the specific webserver or OS that the user has specified. This means that if there is an error for your specific webserver or OS instructions you should check both the corresponding js file and template for the source of that error.
-
-For example if the [Gentoo install instructions](https://certbot.eff.org/#gentoo-apache) have the wrong commands you'll want to look at the [Gentoo template file](https://github.com/certbot/website/blob/master/_scripts/instruction-widget/templates/install/gentoo.html) as well as the [Gentoo section of install.js](https://github.com/certbot/website/blob/master/_scripts/instruction-widget/install.js#L122)
-
-Altrenately if the Getting Started instructions for Apache on Gentoo are wrong - you may want to add a variable to the [get-started.js](https://github.com/certbot/website/blob/master/_scripts/instruction-widget/get-started.js) or add a specific check to the appropriate template file (found [here](https://github.com/certbot/website/tree/master/_scripts/instruction-widget/templates/getting-started))
diff --git a/LICENSE.txt b/LICENSE.txt
deleted file mode 100644
index dba13ed2d..000000000
--- a/LICENSE.txt
+++ /dev/null
@@ -1,661 +0,0 @@
- GNU AFFERO GENERAL PUBLIC LICENSE
- Version 3, 19 November 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc.
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
- The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works. By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
- Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
- A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate. Many developers of free software are heartened and
-encouraged by the resulting cooperation. However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
- The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community. It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server. Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
- An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals. This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- TERMS AND CONDITIONS
-
- 0. Definitions.
-
- "This License" refers to version 3 of the GNU Affero General Public License.
-
- "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
- "The Program" refers to any copyrightable work licensed under this
-License. Each licensee is addressed as "you". "Licensees" and
-"recipients" may be individuals or organizations.
-
- To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy. The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
- A "covered work" means either the unmodified Program or a work based
-on the Program.
-
- To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy. Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
- To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
- An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License. If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
- 1. Source Code.
-
- The "source code" for a work means the preferred form of the work
-for making modifications to it. "Object code" means any non-source
-form of a work.
-
- A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
- The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form. A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
- The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities. However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
- The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
- The Corresponding Source for a work in source code form is that
-same work.
-
- 2. Basic Permissions.
-
- All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met. This License explicitly affirms your unlimited
-permission to run the unmodified Program. The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
- You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force. You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright. Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
- Conveying under any other circumstances is permitted solely under
-the conditions stated below. Sublicensing is not allowed; section 10
-makes it unnecessary.
-
- 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
- No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
- When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
- 4. Conveying Verbatim Copies.
-
- You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
- You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
- 5. Conveying Modified Source Versions.
-
- You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
- a) The work must carry prominent notices stating that you modified
- it, and giving a relevant date.
-
- b) The work must carry prominent notices stating that it is
- released under this License and any conditions added under section
- 7. This requirement modifies the requirement in section 4 to
- "keep intact all notices".
-
- c) You must license the entire work, as a whole, under this
- License to anyone who comes into possession of a copy. This
- License will therefore apply, along with any applicable section 7
- additional terms, to the whole of the work, and all its parts,
- regardless of how they are packaged. This License gives no
- permission to license the work in any other way, but it does not
- invalidate such permission if you have separately received it.
-
- d) If the work has interactive user interfaces, each must display
- Appropriate Legal Notices; however, if the Program has interactive
- interfaces that do not display Appropriate Legal Notices, your
- work need not make them do so.
-
- A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
- 6. Conveying Non-Source Forms.
-
- You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
- a) Convey the object code in, or embodied in, a physical product
- (including a physical distribution medium), accompanied by the
- Corresponding Source fixed on a durable physical medium
- customarily used for software interchange.
-
- b) Convey the object code in, or embodied in, a physical product
- (including a physical distribution medium), accompanied by a
- written offer, valid for at least three years and valid for as
- long as you offer spare parts or customer support for that product
- model, to give anyone who possesses the object code either (1) a
- copy of the Corresponding Source for all the software in the
- product that is covered by this License, on a durable physical
- medium customarily used for software interchange, for a price no
- more than your reasonable cost of physically performing this
- conveying of source, or (2) access to copy the
- Corresponding Source from a network server at no charge.
-
- c) Convey individual copies of the object code with a copy of the
- written offer to provide the Corresponding Source. This
- alternative is allowed only occasionally and noncommercially, and
- only if you received the object code with such an offer, in accord
- with subsection 6b.
-
- d) Convey the object code by offering access from a designated
- place (gratis or for a charge), and offer equivalent access to the
- Corresponding Source in the same way through the same place at no
- further charge. You need not require recipients to copy the
- Corresponding Source along with the object code. If the place to
- copy the object code is a network server, the Corresponding Source
- may be on a different server (operated by you or a third party)
- that supports equivalent copying facilities, provided you maintain
- clear directions next to the object code saying where to find the
- Corresponding Source. Regardless of what server hosts the
- Corresponding Source, you remain obligated to ensure that it is
- available for as long as needed to satisfy these requirements.
-
- e) Convey the object code using peer-to-peer transmission, provided
- you inform other peers where the object code and Corresponding
- Source of the work are being offered to the general public at no
- charge under subsection 6d.
-
- A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
- A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling. In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage. For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product. A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
- "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source. The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
- If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information. But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
- The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed. Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
- Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
- 7. Additional Terms.
-
- "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law. If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
- When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it. (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.) You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
- Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
- a) Disclaiming warranty or limiting liability differently from the
- terms of sections 15 and 16 of this License; or
-
- b) Requiring preservation of specified reasonable legal notices or
- author attributions in that material or in the Appropriate Legal
- Notices displayed by works containing it; or
-
- c) Prohibiting misrepresentation of the origin of that material, or
- requiring that modified versions of such material be marked in
- reasonable ways as different from the original version; or
-
- d) Limiting the use for publicity purposes of names of licensors or
- authors of the material; or
-
- e) Declining to grant rights under trademark law for use of some
- trade names, trademarks, or service marks; or
-
- f) Requiring indemnification of licensors and authors of that
- material by anyone who conveys the material (or modified versions of
- it) with contractual assumptions of liability to the recipient, for
- any liability that these contractual assumptions directly impose on
- those licensors and authors.
-
- All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10. If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term. If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
- If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
- Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
- 8. Termination.
-
- You may not propagate or modify a covered work except as expressly
-provided under this License. Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
- However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
- Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
- Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
- 9. Acceptance Not Required for Having Copies.
-
- You are not required to accept this License in order to receive or
-run a copy of the Program. Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance. However,
-nothing other than this License grants you permission to propagate or
-modify any covered work. These actions infringe copyright if you do
-not accept this License. Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
- 10. Automatic Licensing of Downstream Recipients.
-
- Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License. You are not responsible
-for enforcing compliance by third parties with this License.
-
- An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations. If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
- You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License. For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
- 11. Patents.
-
- A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The
-work thus licensed is called the contributor's "contributor version".
-
- A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version. For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
- Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
- In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement). To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
- If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients. "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
- If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
- A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License. You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
- Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
- 12. No Surrender of Others' Freedom.
-
- If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all. For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
- 13. Remote Network Interaction; Use with the GNU General Public License.
-
- Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software. This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
-
- Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
-combined work, and to convey the resulting work. The terms of this
-License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
-
- 14. Revised Versions of this License.
-
- The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time. Such new versions
-will be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
- Each version is given a distinguishing version number. If the
-Program specifies that a certain numbered version of the GNU Affero General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation. If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
- If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
- Later license versions may give you additional or different
-permissions. However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
- 15. Disclaimer of Warranty.
-
- THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
- 16. Limitation of Liability.
-
- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
- 17. Interpretation of Sections 15 and 16.
-
- If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
- END OF TERMS AND CONDITIONS
-
- How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-
- Copyright (C)
-
- This program is free software: you can redistribute it and/or modify
- it under the terms of the GNU Affero General Public License as published by
- the Free Software Foundation, either version 3 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU Affero General Public License for more details.
-
- You should have received a copy of the GNU Affero General Public License
- along with this program. If not, see .
-
-Also add information on how to contact you by electronic and paper mail.
-
- If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source. For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code. There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
- You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-.
diff --git a/README.md b/README.md
index 9421b448b..3c693f970 100644
--- a/README.md
+++ b/README.md
@@ -1,106 +1,23 @@
# Certbot Website
-Website for [EFF's Certbot](https://certbot.eff.org/) project. Uses Jekyll for static site generation.
-
-[](https://travis-ci.com/certbot/website)
-
-## Development
-
-### Building with Travis
-
-If you're developing directly on this repository rather than on a fork, it's probably easiest to let Travis build the site for you.
-
-All branches and pull requests and built and tested by Travis.
-
-For branches, the built assets are pushed to an analagous branch in [certbot/website-builds](https://github.com/certbot/website-builds). Built assets from PRs are not saved because Travis doesn't provide a mechanism to securely push to a Github repo after PRs across forks.
-
-To view the build of any branch, checkout that branch from certbot/website-builds and run nginx to serve the files using the nginx configuration file from this certbot/website repository.
-
-For example, commands to do this might looks like:
-```
-git clone https://github.com/certbot/website-builds.git
-cd website-builds
-git checkout
-CERTBOT_WEBSITE_PATH=/path/to/your/local/certbot/website/repo
-docker run -p 8000:4000 --rm -v "$CERTBOT_WEBSITE_PATH/nginx.conf:/etc/nginx/conf.d/default.conf:ro" -v $(pwd):/usr/share/nginx/html:ro -it nginx
-```
-After starting that command running, you can access the website in your browser at http://localhost:8000. To shut the server down, just hit ctrl+c in the terminal you ran the docker command.
-
-If you are on linux and your user is not a member of the docker group, you'll need to run the command with `sudo`.
-
-### Building locally
-
-#### Install
-1. Install `ruby 2.0+`, `node 8.0+`, and `npm 2.0+`.
-2. `gem install jekyll` (requires v3.0 or higher)
-3. `sudo npm install gulp-cli -g`
-4. `npm install`
-
-If you want to build a copy of the documentation for your local mirror of the
-Cerbot website, also do:
-
-5. `git submodule init`
-6. `git submodule update`
-7. `./_docs.sh depend`
-8. Install `pdflatex` e.g. via `sudo apt install texlive texlive-latex-extra`
-
-#### Run
-To *watch* for changes and reload assets as needed via BrowserSync:
-`gulp watch`
-
-To *build* the site once:
-`gulp build`
-
-To build for production (minified javascript, no source maps):
-`gulp build --env production`
-The environment can also be set in the NODE_ENV environment variable. See https://github.com/gunpowderlabs/gulp-environments.
+This website is now internally maintained.
## Editing content
-### Basic pages
-Most pages can be edited as markdown files.
+Please suggest content changes on [Mattermost](https://opensource.eff.org/signup_user_complete/?id=6iqur37ucfrctfswrs14iscobw) or via an issue in [Github](https://github.com/certbot/website/issues/new/choose).
-Use `/index.html` to edit the homepage.
-Use `/[RELATIVE_URL]/index.html` to edit internal pages.
+## Hosting providers list
-### Hosting providers list
+If you notice information that’s out of date or incorrect, [submit a pull request](https://github.com/certbot/website/blob/master/_data/hosting_providers.json) to our website’s Github repo. Make sure to check out tips for successfully editing the hosting providers list.
- Make sure to fill out the `name`, `link`, `category`, and `reviewed` fields.
- `reviewed` should be a date in format `2019.7.11`.
- `link` is usually a link to the provider's main page; it's where clicking on the name will go.
- for `category`, see descriptions [here](https://certbot.eff.org/hosting_providers/).
- for `full`/`partial` categories, one of the links provided should have evidence of being in that category.
- - only one of `tutorial`, `announcement`, `plan` will show up, in that order.
- - `partial` should have `tutorial`.
- - `full` providers shouldn't need a tutorial to turn on https. an exception might include instructions of what to do if something goes wrong and the automatic https doesn't work.
+ - only one of `tutorial`, `announcement`, `plan` will show up, in that order.
+ - `partial` should have `tutorial`.
+ - `full` providers shouldn't need a tutorial to turn on https. an exception might include instructions of what to do if something goes wrong and the automatic https doesn't work.
- if one provider offers multiple products, either split into two entries or note it in the `note` field.
-- the `note` field is good for things like noting which products have https, or that the site is available only in certain languages. it's not meant for advertising.
+- the `note` field is good for things like noting which products have https, or that the site is available only in certain languages. it's not meant to advertise the hosting provider's site/offerings.
- all unused fields should be `""`
-
-### Installation instructions
-
-Are generated by JavaScript with
-[Mustache](https://mustache.github.io/mustache.5.html), and can be edited in
-`_scripts/instruction-widget`.
-
-### FAQ
-FAQ entries are a Jekyll collection. Add FAQ entries (question and answer pairs) as markdown files to the `_faq_entries` directory.
-
-FAQ entries require two variables to be set in the [front matter](https://jekyllrb.com/docs/frontmatter/):
-
-* title: the "Question" the FAQ entry answers
-* weight: the position of this entry on the page - lighter FAQ entries will float to the top.
-
-## Testing
-Certbot/website uses [html-proofer](https://github.com/gjtorikian/html-proofer) to validate the html output of the build.
-
-To install:
-```
-gem install html-proofer
-```
-
-To run the tests:
-```
-npm test
-```
-(Files with known issues are ignored.)
diff --git a/_config.yml b/_config.yml
deleted file mode 100644
index 1dfeaffda..000000000
--- a/_config.yml
+++ /dev/null
@@ -1,49 +0,0 @@
-# Site settings
-title: Certbot
-email: certbot@eff.org
-description: > # this means to ignore newlines until "baseurl:"
- Automatically enable HTTPS on your website with EFF's Certbot, deploying Let's Encrypt certificates.
-baseurl: "" # the subpath of your site, e.g. /blog/
-url: "https://certbot.eff.org" # the base hostname & protocol for your site
-collections:
- faq_entries:
- output: false
- instructions:
- output: true
- permalink: "/lets-encrypt/:path"
- terms:
- output: false
-defaults:
-- scope:
- type: "instructions"
- values:
- layout: "instruction"
- js:
- - instructions
-exclude:
-- README.md
-- package.json
-- package-lock.json
-- node_modules
-- gulpfile.js
-- vendor
-- _docs
-- _gulp
-- build_key.enc
-- build_key
-- push-build.sh
-- Dockerfile
-- EDITING.md
-- certbot-deploy
-- LICENSE.txt
-- nginx.conf
-- docker-compose.yml
-include:
-- /node_modules/jquery/*
-keep_files:
-- css
-- js
-- docs
-
-# Build settings
-markdown: kramdown
diff --git a/_data/.keep b/_data/.keep
deleted file mode 100644
index e69de29bb..000000000
diff --git a/_data/cb-logo-border.png b/_data/cb-logo-border.png
new file mode 100644
index 000000000..b784bc4a7
Binary files /dev/null and b/_data/cb-logo-border.png differ
diff --git a/_data/hosting_providers.json b/_data/hosting_providers.json
index 91c580d0e..179a7e995 100644
--- a/_data/hosting_providers.json
+++ b/_data/hosting_providers.json
@@ -1,4 +1,124 @@
[
+{
+ "name": "Mayam.host",
+ "link": "https://mayam.host",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://mayam.host/hosting",
+ "plan": "",
+ "reviewed": "2026.01.09",
+ "note": "Free SSL for all webhosting plans"
+},
+{
+ "name": "Neubox",
+ "link": "https://www.neubox.com",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://neubox.com/hosting",
+ "plan": "",
+ "reviewed": "2025.08.13",
+ "note": "Website is in Spanish"
+ },
+ {
+ "name": "Theory7",
+ "link": "https://www.theory7.net",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://www.theory7.net/webhosting/",
+ "plan": "",
+ "reviewed": "2025.08.05",
+ "note": "Free & automated SSL for all webhosting and domains"
+ },
+ {
+ "name": "Olvy Cloud",
+ "link": "https://olvy.net",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://olvy.net/ssl-certificates/",
+ "plan": "",
+ "reviewed": "2025.01.31",
+ "note": "Free SSL certificate for all web hosting plans"
+ },
+ {
+ "name": "Namesilo",
+ "link": "https://www.namesilo.com",
+ "category": "partial",
+ "tutorial": "https://www.namesilo.com/",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2025.08.05",
+ "note": "See entry 'How can I activate my SSL'"
+ },
+ {
+ "name": "IABAI",
+ "link": "https://www.iab.ai",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2024.01.01",
+ "note": "Free SSL certificate for all web hosting plans"
+ },
+ {
+ "name": "Viridio.net",
+ "link": "https://viridio.net",
+ "category": "partial",
+ "tutorial": "https://viridio.net/ssl-certificates/",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2023.11.18",
+ "note": "Formerly AISO.net. Free Let's Encrypt SSL certificates, confusing interface."
+ },
+ {
+ "name": "Avantiv",
+ "link": "https://avantiv.com",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "https://avantiv.com/hospedagem-de-sites/",
+ "reviewed": "2023.06.10",
+ "note": "Free SSL certificate for all web hosting plans"
+ },
+ {
+ "name": "interhost.co.il",
+ "link": "https://www.interhost.co.il",
+ "category": "partial",
+ "tutorial": "https://interhost.co.il/ssl-installation/",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2022.12.07",
+ "note": "Tier 1 Hosting Services & Network Solutions"
+ },
+ {
+ "name": "Snel.com",
+ "link": "https://www.snel.com",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "https://www.snel.com/webhosting/",
+ "reviewed": "2022.11.17",
+ "note": "Free & automated SSL for all-in web hosting plans"
+ },
+ {
+ "name": "Site.nl",
+ "link": "https://site.nl/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "https://site.nl/ssl-certificaat",
+ "reviewed": "2022.8.17",
+ "note": "Free & automated SSL for both webhosting and website builder users"
+ },
+ {
+ "name": "WebOké",
+ "link": "https://www.weboke.nl/",
+ "category": "partial",
+ "tutorial": "https://www.weboke.nl/knowledgebase/80/Gratis-Lets-encrypt-certificaat-instellen.html",
+ "announcement": "https://weboke.nl/webhosting",
+ "plan": "",
+ "reviewed": "2021.6.22",
+ "note": "Website is in dutch"
+ },
{
"name": "Antagonist",
"link": "https://www.antagonist.nl/",
@@ -29,6 +149,16 @@
"reviewed": "2019.5.31",
"note": "This applies to paid plans only."
},
+ {
+ "name": "Cloud86",
+ "link": "https://cloud86.nl/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.9.27",
+ "note": "The website is in Dutch."
+ },
{
"name": "Domainnameshop",
"link": "https://www.domainnameshop.com/",
@@ -59,6 +189,16 @@
"reviewed": "2019.5.31",
"note": ""
},
+ {
+ "name": "Esmero",
+ "link": "https://www.esmero.nl/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://www.esmero.nl/webhosting",
+ "plan": "",
+ "reviewed": "2024.6.14",
+ "note": "The website is in Dutch."
+ },
{
"name": "EvergreenTech.io",
"link": "https://evergreentech.io/",
@@ -119,6 +259,16 @@
"reviewed": "2019.5.31",
"note": ""
},
+ {
+ "name": "NDCHost",
+ "link": "https://ndchost.com/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.1.25",
+ "note": "Free SSL included with all web hosting plans. Certbot supported on all Cloud and Metal server plans. Installation and configuration included free if needed."
+ },
{
"name": "Neocities",
"link": "https://neocities.org/",
@@ -129,6 +279,16 @@
"reviewed": "2019.5.31",
"note": ""
},
+ {
+ "name": "netclusive",
+ "link": "https://netclusive.de/",
+ "category": "full",
+ "tutorial": "https://www.netclusive.de/faq/content/36/430/de/kann-ich-meine-webseite-ssl-verschluesseln.html",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2020.10.01",
+ "note": "The website is in German."
+ },
{
"name": "Netlify",
"link": "https://www.netlify.com/",
@@ -159,16 +319,6 @@
"reviewed": "2020.02.03",
"note": "All production and development environments include Let's Encrypt certificates automatically."
},
- {
- "name": "Pride Tech Design",
- "link": "https://pridetechdesign.com/",
- "category": "full",
- "tutorial": "",
- "announcement": "",
- "plan": "",
- "reviewed": "2019.5.31",
- "note": ""
- },
{
"name": "Render",
"link": "https://render.com/",
@@ -249,6 +399,16 @@
"reviewed": "2020.02.13",
"note": "The website is in Hungarian."
},
+ {
+ "name": "NFOservers",
+ "link": "https://nfoservers.com",
+ "category": "partial",
+ "tutorial": "",
+ "announcement": "https://forums.nfoservers.com/viewtopic.php?f=6&t=14580",
+ "plan": "",
+ "reviewed": "2021.11.21",
+ "note": "Only available for your own domains, not available on free subdomains"
+ },
{
"name": "34SP.com",
"link": "",
@@ -481,12 +641,12 @@
},
{
"name": "Combell",
- "link": "",
- "category": "partial",
+ "link": "https://www.combell.com/",
+ "category": "full",
"tutorial": "",
- "announcement": "",
+ "announcement": "https://www.combell.com/en/blog/free-lets-encrypt-ssl-certificate-for-combell-clients/",
"plan": "",
- "reviewed": "",
+ "reviewed": "2020.12.17",
"note": ""
},
{
@@ -531,13 +691,13 @@
},
{
"name": "Do.de",
- "link": "",
- "category": "partial",
+ "link": "https://www.do.de",
+ "category": "full",
"tutorial": "",
- "announcement": "",
+ "announcement": "https://www.do.de/wiki/lets-encrypt-ssl-zertifikate",
"plan": "",
- "reviewed": "",
- "note": ""
+ "reviewed": "2022.6.2",
+ "note": "The website is in German."
},
{
"name": "Domain & Webspace Tremmel",
@@ -579,16 +739,6 @@
"reviewed": "",
"note": ""
},
- {
- "name": "DreamHost",
- "link": "",
- "category": "partial",
- "tutorial": "",
- "announcement": "",
- "plan": "",
- "reviewed": "",
- "note": ""
- },
{
"name": "Dwe Gruppe",
"link": "",
@@ -899,6 +1049,16 @@
"reviewed": "",
"note": ""
},
+ {
+ "name": "Hostomy",
+ "link": "https://hostomy.com",
+ "category": "partial",
+ "tutorial": "https://hostomy.com/blog/installing-ssl-in-hostomy-shared-hosting/",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2022.10.7",
+ "note": ""
+ },
{
"name": "HostM.com",
"link": "",
@@ -1252,22 +1412,22 @@
{
"name": "NearlyFreeSpeech.NET",
"link": "https://www.nearlyfreespeech.net/",
- "category": "partial",
- "tutorial": "https://members.nearlyfreespeech.net/faq?q=SSLCertificates#SSLCertificates",
- "announcement": "",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://faq.nearlyfreespeech.net/section/ourservice/sslcertificates#sslcertificates",
"plan": "",
- "reviewed": "2019.6.1",
- "note": "You need to log in to access the tutorial."
+ "reviewed": "2025.08.05",
+ "note": ""
},
{
"name": "Netsite",
- "link": "",
- "category": "partial",
- "tutorial": "",
+ "link": "https://www.netsite.dk/",
+ "category": "full",
+ "tutorial": "https://www.netsite.dk/support/hjemmeside/https/",
"announcement": "",
"plan": "",
- "reviewed": "",
- "note": ""
+ "reviewed": "2020.9.12",
+ "note": "All shared web hosting packages have SSL active + automated + https redirect"
},
{
"name": "Neify Hosting",
@@ -1459,6 +1619,16 @@
"reviewed": "2019.7.22",
"note": ""
},
+ {
+ "name": "Porkbun",
+ "link": "https://porkbun.com/products/web_hosting",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://porkbun.com/products/ssl",
+ "plan": "",
+ "reviewed": "2022.11.12",
+ "note": "Let's Encrypt available on all plans and services"
+ },
{
"name": "Professional Hosting",
"link": "",
@@ -1619,6 +1789,16 @@
"reviewed": "",
"note": ""
},
+ {
+ "name": "Seravo",
+ "link": "https://seravo.com",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://seravo.com/blog/https-is-not-optional/",
+ "plan": "",
+ "reviewed": "2020.11.11",
+ "note": ""
+ },
{
"name": "ServerPilot",
"link": "https://serverpilot.io/",
@@ -1669,6 +1849,16 @@
"reviewed": "",
"note": ""
},
+ {
+ "name": "SnapPages",
+ "link": "https://www.snappages.net/",
+ "category": "partial",
+ "tutorial": "http://help.snappages.site/en/articles/3508506-securing-your-site",
+ "announcement": "https://www.subsplash.com/websites",
+ "plan": "",
+ "reviewed": "2020.11.01",
+ "note": ""
+ },
{
"name": "snowflake Ops",
"link": "",
@@ -1749,6 +1939,16 @@
"reviewed": "",
"note": ""
},
+ {
+ "name": "Thecamels",
+ "link": "https://thecamels.org/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://thecamels.org/en/ssl-certificates/lets-encrypt/",
+ "plan": "",
+ "reviewed": "2020.1.30",
+ "note": "Let's Encrypt available on all hosting plans, VPS and metal servers. Active automatically. Certbot supported"
+ },
{
"name": "Thisistap",
"link": "",
@@ -1851,13 +2051,13 @@
},
{
"name": "VeeroTech",
- "link": "",
+ "link": "https://www.veerotech.net/",
"category": "partial",
"tutorial": "https://www.veerotech.net/kb/install-ssl-certificate-using-lets-encrypt-inside-cpanel/",
"announcement": "",
"plan": "",
"reviewed": "2019.6.6",
- "note": ""
+ "note": "All shared, reseller, semi dedicated and WordPress hosting plans feature Let's Encrypt manual and automatic options. Certificates can be automatically issued or manually issued and will renew automatically."
},
{
"name": "Vélhost",
@@ -1879,6 +2079,16 @@
"reviewed": "2019.6.6",
"note": ""
},
+ {
+ "name": "Vimexx",
+ "link": "https://www.vimexx.nl/",
+ "category": "partial",
+ "tutorial": "https://www.vimexx.nl/help/gratis-lets-encrypt-ssl-op-je-website-installeren",
+ "announcement": "https://www.vimexx.nl/news/gratis-wildcard-ssl-via-lets-encrypt",
+ "plan": "",
+ "reviewed": "2021.2.28",
+ "note": "The website is in Dutch."
+ },
{
"name": "VIPserv.org",
"link": "",
@@ -1981,12 +2191,12 @@
},
{
"name": "World4You Internet Services GmbH",
- "link": "",
+ "link": "https://www.world4you.com/en/",
"category": "partial",
"tutorial": "",
- "announcement": "",
+ "announcement": "https://www.world4you.com/en/domain/ssl-certificates",
"plan": "",
- "reviewed": "2019.6.6",
+ "reviewed": "2025.7.5",
"note": ""
},
{
@@ -2061,13 +2271,13 @@
},
{
"name": "KnownHost",
- "link": "",
- "category": "partial",
+ "link": "https://www.knownhost.com",
+ "category": "full",
"tutorial": "",
- "announcement": "",
- "plan": "",
- "reviewed": "",
- "note": "*Pending re-verification"
+ "announcement": "https://www.knownhost.com/kb/shared-reseller-hosting/#free_ssl",
+ "plan": "https://www.knownhost.com/web-hosting",
+ "reviewed": "2022.12.13",
+ "note": "Free & automated SSL for all-in web hosting plans"
},
{
"name": "PlotHost",
@@ -2317,7 +2527,7 @@
"announcement": "https://blog.alwaysdata.com/2016/11/28/https-native-support-for-lets-encrypt/",
"plan": "",
"reviewed": "2020.01.07",
- "note": "Available for all plans from free account to dedicated servers"
+ "note": ""
},
{
"name": "Wikstrom Telephone Company (Wiktel)",
@@ -2377,7 +2587,7 @@
"announcement": "https://www.canet.at/hosting-server/",
"plan": "",
"reviewed": "2020.03.26",
- "note": "All plans come with Let's Encrypt for Web and Mail"
+ "note": ""
},
{
"name": "Nuclear.Hosting",
@@ -2387,7 +2597,7 @@
"announcement": "",
"plan": "",
"reviewed": "2020.04.01",
- "note": "Available for all membership types, without any limitations."
+ "note": ""
},
{
"name": "HahuCloud",
@@ -2397,7 +2607,7 @@
"announcement": "",
"plan": "",
"reviewed": "2020.05.30",
- "note": "Available for all membership types, without any limitations."
+ "note": ""
},
{
"name": "Shellrent",
@@ -2418,5 +2628,245 @@
"plan": "",
"reviewed": "2020.07.15",
"note": "All webhosting plans include Let's Encrypt. The website is in Dutch."
+ },
+ {
+ "name": "Conetix",
+ "link": "https://conetix.com.au",
+ "category": "partial",
+ "tutorial": "https://conetix.com.au/support/plesk-obsidian-how-to-install-a-free-lets-encrypt-ssl/",
+ "announcement": "https://conetix.com.au/blog/lets-encrypt-free-certificates-on-all-conetix-host/",
+ "plan": "",
+ "reviewed": "2020.09.16",
+ "note": ""
+ },
+ {
+ "name": "Firebase Hosting",
+ "link": "https://firebase.google.com/",
+ "category": "full",
+ "tutorial": "https://firebase.google.com/docs/hosting/custom-domain#ssl-provisioning",
+ "announcement": "https://firebase.googleblog.com/2014/05/introducing-firebase-hosting.html",
+ "plan": "",
+ "reviewed": "2020.09.20",
+ "note": "All domains/sites automatically use Let's Encrypt. Multiple sites share a single certificate using the SAN field"
+ },
+ {
+ "name": "Rad Web Hosting",
+ "link": "https://radwebhosting.com",
+ "category": "partial",
+ "tutorial": "https://radwebhosting.com/client_area/knowledgebase/226/Enable-Lets-Encrypt-AutoSSL-Provider.html",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2020.09.28",
+ "note": "Let's Encrypt available on all hosting, VPS, and dedicated server plans."
+ },
+ {
+ "name": "Zoner Oy",
+ "link": "https://www.zoner.fi/",
+ "category": "partial",
+ "tutorial": "https://www.zoner.fi/tukiohjeet/lets-encrypt-sertifikaatin-kayttoonotto/",
+ "announcement": "https://www.zoner.fi/lets-encrypt-ilmainen-ssl-sertifikaatti/",
+ "plan": "",
+ "reviewed": "2021.02.12",
+ "note": "All webhosting plans include Let's Encrypt."
+ },
+ {
+ "name": "webkeeper.ch",
+ "link": "https://www.webkeeper.ch/",
+ "category": "partial",
+ "tutorial": "https://www.webkeeper.ch/de/support-kb/webhosting/installation-lets-encrypt-zertifikat",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.5.28",
+ "note": "Deutsch, English, Italiano / All webhosting plans include Let's Encrypt."
+ },
+ {
+ "name": "Clausweb",
+ "link": "https://www.clausweb.ro/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://www.clausweb.ro/blog/ce-este-un-certificat-ssl-si-la-ce-se-foloseste/",
+ "plan": "",
+ "reviewed": "2020.2.19",
+ "note": ""
+ },
+ {
+ "name": "UKFast",
+ "link": "https://ukfast.co.uk/",
+ "category": "no",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.10.09",
+ "note": ""
+ },
+ {
+ "name": "nazwa.pl",
+ "link": "https://nazwa.pl/",
+ "category": "no",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "Home.pl",
+ "link": "https://home.pl/",
+ "category": "no",
+ "tutorial": "https://pomoc.home.pl/baza-wiedzy/certyfikat-ssl-na-serwerze-w-home-pl-informacje-podstawowe",
+ "announcement": "",
+ "plan": "https://home.pl/ssl/#szczegoly",
+ "reviewed": "2022.03.02",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "az.pl",
+ "link": "https://az.pl/",
+ "category": "no",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "Small.pl",
+ "link": "https://www.small.pl/",
+ "category": "partial",
+ "tutorial": "https://pomoc.small.pl/SSL/#generowanie-darmowych-certyfikat%C3%B3w-lets-encrypt",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "ct8.pl",
+ "link": "https://www.ct8.pl/",
+ "category": "partial",
+ "tutorial": "https://wiki.mydevil.net/SSL#Generowanie_darmowych_certyfikat.C3.B3w_Let.27s_Encrypt",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "cyber_Folks",
+ "link": "https://cyberfolks.pl/",
+ "category": "partial",
+ "tutorial": "https://cyberfolks.pl/pomoc/jak-uruchomic-certyfikat-ssl-lets-encrypt/",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "SeoHost.pl",
+ "link": "https://seohost.pl/",
+ "category": "partial",
+ "tutorial": "https://seohost.pl/pomoc/jak-aktywowac-darmowy-certyfikat-ssl-lets-encrypt",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "Kei.pl",
+ "link": "https://www.kei.pl/",
+ "category": "partial",
+ "tutorial": "https://www.kei.pl/pomoc/certyfikat-lets-encrypt",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "zenbox.pl",
+ "link": "https://zenbox.pl/",
+ "category": "partial",
+ "tutorial": "https://pomoc.zenbox.pl/pl/kb/articles/jak-moge-wlaczyc-certyfikat-lets-encrypt-dla-mojej-domeny",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "dhosting.pl",
+ "link": "https://dhosting.pl/",
+ "category": "partial",
+ "tutorial": "https://dhosting.pl/pomoc/baza-wiedzy/lets-encrypt-i-sni/",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "Kylos",
+ "link": "https://www.kylos.pl/",
+ "category": "full",
+ "tutorial": "https://panel.kylos.pl/knowledgebase/246/Darmowe-certyfikaty-SSL-dla-stron-WWW-w-cPanel.html",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2021.12.18",
+ "note": "The website is in Polish."
+ },
+ {
+ "name": "MyHost (NZ)",
+ "link": "https://myhost.nz/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "",
+ "plan": "https://myhost.nz/hosting/web-hosting",
+ "reviewed": "2022.09.16",
+ "note": ""
+ },
+ {
+ "name": "SiteHost",
+ "link": "https://sitehost.nz/",
+ "category": "partial",
+ "tutorial": "",
+ "announcement": "https://sitehost.nz/blog/2017/ssl-what-you-need-to-know",
+ "plan": "",
+ "reviewed": "2022.09.16",
+ "note": ""
+ },
+ {
+ "name": "Koumbit",
+ "link": "https://koumbit.org/",
+ "category": "partial",
+ "tutorial": "https://www.koumbit.org/en/content/it-possible-have-secure-connection-site",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2022.10.17",
+ "note": ""
+ },
+ {
+ "name": "Hoasted",
+ "link": "https://www.hoasted.com/",
+ "category": "partial",
+ "tutorial": "https://support.hoasted.com/article/101-ssl-met-lets-encrypt-certificaat",
+ "announcement": "",
+ "plan": "",
+ "reviewed": "2024.8.16",
+ "note": "This website is in Dutch."
+ },
+ {
+ "name": "Framer",
+ "link": "https://www.framer.com/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://www.framer.com/help/articles/do-i-have-to-setup-ssl-when-adding-a-custom-domain-to-a-framer-project/",
+ "plan": "",
+ "reviewed": "2025.03.17",
+ "note": ""
+ },
+ {
+ "name": "Hosterfy",
+ "link": "https://www.hosterfy.com/",
+ "category": "full",
+ "tutorial": "",
+ "announcement": "https://www.hosterfy.com/fr/hebergement-web-illimite-cpanel",
+ "plan": "",
+ "reviewed": "2025.04.22",
+ "note": "Free & automated SSL for all web hosting plans"
}
]
diff --git a/_data/inputs.json b/_data/inputs.json
deleted file mode 100644
index 2dab2e23d..000000000
--- a/_data/inputs.json
+++ /dev/null
@@ -1,186 +0,0 @@
-{
- "webservers": [
- {
- "name": "Apache",
- "id": "apache"
- },
- {
- "name": "Nginx",
- "id": "nginx"
- },
- {
- "name": "Haproxy",
- "id": "haproxy"
- },
- {
- "name": "Plesk",
- "id": "plesk"
- },
- {
- "name": "Web Hosting Product",
- "id": "webproduct"
- },
- {
- "name": "None of the above",
- "id": "other"
- }
- ],
- "operating_systems": [
- {
- "name": "Web Hosting Service",
- "id": "sharedhost",
- "distro": "sharedhost",
- "version": "0"
- },
- {
- "name": "snapd",
- "id": "snap",
- "distro": "snap",
- "version": "0"
- },
- {
- "name": "Debian 9 (stretch)",
- "id": "debianstretch",
- "distro": "debian",
- "version": "9"
- },
- {
- "name": "Debian 10 (buster)",
- "id": "debianbuster",
- "distro": "debian",
- "version": "10"
- },
- {
- "name": "Debian testing/unstable",
- "id": "debiantesting",
- "distro": "debian",
- "version": "11"
- },
- {
- "name": "Ubuntu 20.04",
- "id": "ubuntufocal",
- "distro": "ubuntu",
- "version": "20.04"
- },
- {
- "name": "Ubuntu 19.10",
- "id": "ubuntuother",
- "distro": "ubuntu",
- "version": "19.10"
- },
- {
- "name": "Ubuntu 18.04 LTS (bionic)",
- "id": "ubuntubionic",
- "distro": "ubuntu",
- "version": "18.04"
- },
- {
- "name": "Ubuntu 16.04 (xenial)",
- "id": "ubuntuxenial",
- "distro": "ubuntu",
- "version": "16.04"
- },
- {
- "name": "Gentoo",
- "id": "gentoo",
- "distro": "gentoo",
- "version": "0"
- },
- {
- "name": "Arch Linux",
- "id": "arch",
- "distro": "arch",
- "version": "0"
- },
- {
- "name": "Fedora",
- "id": "fedora",
- "distro": "fedora",
- "version": "0"
- },
- {
- "name": "CentOS 6",
- "id": "centos6",
- "distro": "centos",
- "version": "6"
- },
- {
- "name": "RHEL 6",
- "id": "centosrhel6",
- "distro": "rhel",
- "version": "6"
- },
- {
- "name": "CentOS/RHEL 7",
- "id": "centosrhel7",
- "distro": "centos",
- "version": "7"
- },
- {
- "name": "CentOS/RHEL 8",
- "id": "centosrhel8",
- "distro": "centos",
- "version": "8"
- },
- {
- "name": "FreeBSD",
- "id": "freebsd",
- "distro": "freebsd",
- "version": "0"
- },
- {
- "name": "OpenBSD 6.0+",
- "id": "opbsd6",
- "distro": "opbsd",
- "version": "6"
- },
- {
- "name": "macOS",
- "id": "osx",
- "distro": "macos",
- "version": "10"
- },
- {
- "name": "Devuan ASCII 2.0",
- "id": "devuanascii",
- "distro": "devuan",
- "version": "2"
- },
- {
- "name": "Devuan Beowulf 3.0",
- "id": "devuanbeowulf",
- "distro": "devuan",
- "version": "3"
- },
- {
- "name": "Devuan testing/unstable",
- "id": "devuanother",
- "distro": "devuan",
- "version": "4"
- },
- {
- "name": "openSUSE Tumbleweed",
- "id": "tumbleweed",
- "distro": "opensuse",
- "version": "0"
- },
- {
- "name": "openSUSE Leap 15.0",
- "id": "leap",
- "distro": "opensuse",
- "version": "15.0"
- },
- {
- "name": "Other UNIX",
- "id": "pip",
- "distro": "python",
- "version": "0"
- },
- {
- "name": "Windows",
- "id": "windows",
- "distro": "windows",
- "version": "0"
- }
- ]
-}
diff --git a/_docs b/_docs
deleted file mode 160000
index b841f0f30..000000000
--- a/_docs
+++ /dev/null
@@ -1 +0,0 @@
-Subproject commit b841f0f307e3f7bda7122761e0efa1139a50c6c8
diff --git a/_docs.sh b/_docs.sh
deleted file mode 100755
index 3b5e0d10e..000000000
--- a/_docs.sh
+++ /dev/null
@@ -1,19 +0,0 @@
-#!/usr/bin/env bash
-
-case "$1" in
- "depend" )
- cd _docs
- export CERTBOT_WEBSITE='True'
- sudo apt-get update
- sudo apt-get install python3-dev python3-venv gcc libaugeas0 libssl-dev \
- libffi-dev ca-certificates openssl -y
- ./tools/venv3.py
- ;;
- "install" )
- cd _docs
- source ./venv3/bin/activate
- pip install --upgrade git+https://github.com/EFForg/sphinx_rtd_theme.git
- cd certbot
- make -C docs clean html epub latex latexpdf > /dev/null
- ;;
-esac
diff --git a/_faq_entries/0-are-certificates-trusted.md b/_faq_entries/0-are-certificates-trusted.md
deleted file mode 100644
index df12fd9bd..000000000
--- a/_faq_entries/0-are-certificates-trusted.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Are certificates from Let’s Encrypt trusted by my browser?"
-weight: 0
----
-
-For most browsers and operating systems, yes. See the [compatibility list](https://community.letsencrypt.org/t/trust-of-dst-root-ca-x3-and-isrg-root/4394) for more detail.
\ No newline at end of file
diff --git a/_faq_entries/10-root-privileges.md b/_faq_entries/10-root-privileges.md
deleted file mode 100644
index bc3740296..000000000
--- a/_faq_entries/10-root-privileges.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: "Does Certbot require root/administrator privileges?"
-weight: 10
----
-
-Whether root is required to run Certbot or not depends on how you intend to use it.
-
-If you're asking this question because you have a hosting provider that doesn't grant you root access, you'll need to ensure first of all that you have a way to install a certificate if you get one. If the answer is "no", ask your hosting provider to support Let's Encrypt (many already do). If the answer is "yes", or you're asking the question for security reasons, read on...
-
-The [webroot](/docs/using.html#webroot) and [manual](/docs/using.html#manual) plugins work well without root privileges. However, you need to provide writable paths for Certbot's working directories either by ensuring that `/etc/letsencrypt/`, `/var/log/letsencrypt/`, `/var/lib/letsencrypt/` are writable, or by picking different directories with the `--config-dir`, `--logs-dir`, and `--work-dir` flags.
-
-The [standalone](https://certbot.eff.org/docs/using.html#standalone) plugin requires root to bind port 80 or 443, although on Linux you could also grant [CAP_NET_BIND_SERVICE](http://superuser.com/a/892391) to the relevant user.
-
-Certbot's Apache and Nginx plugins normally require root both for making temporary and persistent changes to webserver configurations, and to perform graceful reload events for those servers.
-
-The `certbot-auto` script works on the assumption that root privileges will be used, both in order to install OS dependencies where required and because it needs to support all of the plugins mentioned above. The packaged versions of Certbot are more flexible, and some of the teams building these packages are working toward having Cerbot run with group rather than root privileges where possible.
diff --git a/_faq_entries/11-CSR.md b/_faq_entries/11-CSR.md
deleted file mode 100644
index 1884d26f2..000000000
--- a/_faq_entries/11-CSR.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Can I use an existing private key or Certificate Signing Request (CSR) with Certbot?"
-weight: 11
----
-
-Yes. You can obtain a certificate for an existing CSR, which means you may generate your own CSR using your own private key. However, Certbot will not accept a private key as input and generate a CSR for you.
diff --git a/_faq_entries/12-rate-limits.md b/_faq_entries/12-rate-limits.md
deleted file mode 100644
index bf5ff1243..000000000
--- a/_faq_entries/12-rate-limits.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "What are the current rate limits?"
-weight: 12
----
-
-[https://letsencrypt.org/docs/rate-limits/](https://letsencrypt.org/docs/rate-limits/)
diff --git a/_faq_entries/13-bringing-down-website.md b/_faq_entries/13-bringing-down-website.md
deleted file mode 100644
index 2be985cea..000000000
--- a/_faq_entries/13-bringing-down-website.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Can I issue a certificate without bringing down my web server?"
-weight: 13
----
-
-Yes, Certbot has different [plugins](https://certbot.eff.org/docs/using.html#getting-certificates-and-choosing-plugins) to perform domain validation and none of them require any downtime except for the "standalone" plugin.
diff --git a/_faq_entries/14-IP.md b/_faq_entries/14-IP.md
deleted file mode 100644
index 43810d4a7..000000000
--- a/_faq_entries/14-IP.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "What IP addresses will the Let's Encrypt servers use to validate my web server?"
-weight: 14
----
-
-The Let's Encrypt CA doesn't publish a list of IP addresses it uses to validate, because they may change at any time. In the future, it may validate from multiple IP addresses at once.
diff --git a/_faq_entries/15-port-80.md b/_faq_entries/15-port-80.md
deleted file mode 100644
index 456654b8c..000000000
--- a/_faq_entries/15-port-80.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Can I issue a certificate if my webserver doesn't listen on port 80?"
-weight: 15
----
-
-Yes, using the DNS-01 or TLS-ALPN-01 challenge. However, Certbot does not include support for TLS-ALPN-01 yet. If you're using any Certbot with any method other than DNS authentication, your web server must listen on port 80, or at least be capable of doing so temporarily during certificate validation.
-
-If you have an ISP or firewall that blocks port 80 and you can't get it unblocked, you'll need to use DNS authentication or a different Let's Encrypt client.
diff --git a/_faq_entries/16-privacy-policy.md b/_faq_entries/16-privacy-policy.md
deleted file mode 100644
index 7bb03248d..000000000
--- a/_faq_entries/16-privacy-policy.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "What's Certbot's privacy policy?"
-weight: 16
----
-
-The Certbot privacy policy can be found [here](/privacy).
diff --git a/_faq_entries/17-copyright-license.md b/_faq_entries/17-copyright-license.md
deleted file mode 100644
index 3a71b1aa5..000000000
--- a/_faq_entries/17-copyright-license.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "What are the licenses for Certbot and this website?"
-weight: 16
----
-
-The Certbot software and documentation are licensed under the Apache 2.0 license as described [here](https://raw.githubusercontent.com/certbot/certbot/master/LICENSE.txt). Otherwise, this website is generally licensed under EFF's [CC-BY](https://creativecommons.org/licenses/by-nc/2.0/) license, except this FAQ page, which is a derivative of the [Let’s Encrypt FAQ](https://community.letsencrypt.org/t/frequently-asked-questions-faq/26) (which was licensed under [Let’s Encrypt’s CC-BY-NC](https://community.letsencrypt.org/tos#3)).
diff --git a/_faq_entries/18-debugging-tools.md b/_faq_entries/18-debugging-tools.md
deleted file mode 100644
index e7fe2208a..000000000
--- a/_faq_entries/18-debugging-tools.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: "What tools can I use for debugging my site’s HTTPS configuration?"
-weight: 15
----
-
-There are four scanning tools that are commonly suggested on the Let’s Encrypt community forum:
- - [https://letsdebug.net/](https://letsdebug.net/) (by Alex Zorin)
- - [https://check-your-website.server-daten.de/](https://check-your-website.server-daten.de/) (by Jürgen Auer)
- - [https://whynopadlock.com/](https://whynopadlock.com/) (by LexiConn)
- - [https://www.ssllabs.com/ssltest/](https://www.ssllabs.com/ssltest/) (by Qualys)
-
-They all have their strengths. Let's Debug would be used only by people who don't have HTTPS working yet, while SSL Labs would be used only by people who (at least sort of) do.
-
-**Let’s Debug**: Let's Debug is most helpful if you have a failed challenge and want a straightforward explanation of why the challenge is failing.
-
-**Check-Your-Website**: Jürgen's scanner is most helpful if you have a confusing DNS or HTTP configuration error where some pages or some browsers work properly and others don't, or if your HTTP site works in a browser and yet you get failed challenges that you don't understand
-
-**Why No Padlock**: Why No Padlock is most helpful if you already have a certificate but all or some users don't see a valid HTTPS connection (and it gives very specific information about what's causing mixed content warnings)
-
-**SSL Labs**: SSL Labs is most helpful for cryptographic issues on an already set up HTTPS site, such as a case where some browsers work properly and others give a ciphersuite-related error, or if you want to convince nerds and/or regulatory bodies that you're following security best practices
diff --git a/_faq_entries/2-certs-other-than-ssl-tls.md b/_faq_entries/2-certs-other-than-ssl-tls.md
deleted file mode 100644
index f1c7a56e2..000000000
--- a/_faq_entries/2-certs-other-than-ssl-tls.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Will Certbot issue certificates for anything other than SSL/TLS for websites?"
-weight: 2
----
-
-Certbot will fetch Let’s Encrypt certificates that will be standard Domain Validation certificates, so you can use them for any server that uses a domain name, like web servers. You can also use these certificates for other TLS applications such as IMAPS.
diff --git a/_faq_entries/3-code-signing.md b/_faq_entries/3-code-signing.md
deleted file mode 100644
index b84c258c3..000000000
--- a/_faq_entries/3-code-signing.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Can I use certificates from Certbot for code signing or email encryption?"
-weight: 3
----
-
-No. Email encryption and code signing require a different type of certificate than the Let's Encrypt CA is issuing.
diff --git a/_faq_entries/4-store-private-keys.md b/_faq_entries/4-store-private-keys.md
deleted file mode 100644
index b89fd070b..000000000
--- a/_faq_entries/4-store-private-keys.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: "Will Certbot generate or store the private keys for my certificates on Let’s Encrypt’s servers?"
-weight: 4
----
-
-No. Never.
-
-The private key is always generated and managed on your own servers, not by the Let's Encrypt certificate authority.
diff --git a/_faq_entries/5-EV.md b/_faq_entries/5-EV.md
deleted file mode 100644
index 089eba63a..000000000
--- a/_faq_entries/5-EV.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Will Certbot issue Extended Validation (EV) certificates?"
-weight: 5
----
-
-Certbot and Let’s Encrypt have no plans to issue EV certificates at this time.
diff --git a/_faq_entries/6-SAN.md b/_faq_entries/6-SAN.md
deleted file mode 100644
index 08ba908e6..000000000
--- a/_faq_entries/6-SAN.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Can I get a certificate for multiple domain names (SAN certificates)?"
-weight: 6
----
-
-Yes, the same certificate can apply to several different names using the Subject Alternative Name (SAN) mechanism. Certbot automatically requests certificates for multiple names when requested to do so. The resulting certificates will be accepted by browsers for any of the domain names listed in them.
diff --git a/_faq_entries/7-wildcard.md b/_faq_entries/7-wildcard.md
deleted file mode 100644
index 066bc4cd8..000000000
--- a/_faq_entries/7-wildcard.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Does Let's Encrypt issue wildcard certificates?"
-weight: 7
----
-
-Yes! Let's Encrypt has [begun issuing](https://community.letsencrypt.org/t/acme-v2-and-wildcard-certificate-support-is-live/55579) wildcard certificates in March 2018. Certbot has added support for wildcard certificates as of version 0.22.0. Obtaining a wildcard certificate requires using the DNS authentication method, either via `--manual` or via a Certbot DNS plugin appropriate to your DNS provider.
-
-Note that [depending how you install Certbot](https://community.letsencrypt.org/t/getting-wildcard-certificates-with-certbot/56285), appropriate plugins to automate the process may not yet be available on your system. Information about the DNS plugins [is available in the Certbot documentation](https://certbot.eff.org/docs/using.html#dns-plugins).
-
-**Certificates obtained with `--manual` cannot be renewed automatically with `certbot renew`** (unless you've provided a custom authorization script). However, certificates obtained with a Certbot DNS plugin can be renewed automatically. In order to obtain wildcard certificates that can be renewed without human intervention, you'll need to use a Certbot DNS plugin that's compatible with an API supported by your DNS provider, or a script that can make appropriate DNS record changes upon demand. Even if your regular DNS provider doesn't support a compatible update mechanism, you can use a `CNAME` delegation for the `_acme-challenge` record in your DNS zone to a different provider that does. You can also point `_acme-challenge` to an [acme-dns](https://github.com/joohoi/acme-dns) instance.
-
-Note that [depending how you install Certbot](https://community.letsencrypt.org/t/getting-wildcard-certificates-with-certbot/56285), appropriate plugins to automate the process may not yet be available on your system.
-
-Please see Certbot documentation for more information about your situation.
diff --git a/_faq_entries/8-OS.md b/_faq_entries/8-OS.md
deleted file mode 100644
index d65745c6e..000000000
--- a/_faq_entries/8-OS.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: "Does Certbot support my operating system?"
-weight: 8
----
-
-We currently have Certbot support for major Linux and BSD variant operating systems. There are a large number of other [client implementations](https://letsencrypt.org/docs/client-options/) available too.
diff --git a/_faq_entries/9-automatic-configuration.md b/_faq_entries/9-automatic-configuration.md
deleted file mode 100644
index 6ed4ab0f7..000000000
--- a/_faq_entries/9-automatic-configuration.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Will Certbot support automated configuration of my web server?"
-weight: 9
----
-
-This website provides information about the level of support for various web servers and operating systems, which varies and is increasing over time. On supported systems, the automated configuration makes it fast and easy to obtain, install, and automatically renew certificates.
-
-If automated configuration is not supported for your web server, you can still get a certificate using Certbot and configure your server software manually. In this case, the certificate will not be renewed automatically.
-
-Note that automated configuration is not required. It can be disabled if you prefer to configure your server software yourself.
diff --git a/_gulp/config.js b/_gulp/config.js
deleted file mode 100644
index 5bf382d7a..000000000
--- a/_gulp/config.js
+++ /dev/null
@@ -1,14 +0,0 @@
-module.exports = {
- site_root: "_site",
- css: {
- src: "_sass/**/*.?(s)css",
- dest: "_site/css"
- },
- js: {
- src: "_scripts/**/*",
- dest: "_site/js"
- },
- instructions: {
- dest: "./_data/instructions.json"
- }
-}
\ No newline at end of file
diff --git a/_gulp/index.js b/_gulp/index.js
deleted file mode 100644
index c61e5ba22..000000000
--- a/_gulp/index.js
+++ /dev/null
@@ -1,16 +0,0 @@
-var gulp = require('gulp');
-var fs = require('fs');
-var tasks = fs.readdirSync('./_gulp/tasks/');
-
-tasks.forEach(function(task) {
- require('./tasks/' + task);
-});
-
-gulp.task('watch',
- gulp.parallel('instructions', 'css', 'js', 'jekyll:watch', 'serve'));
-
-gulp.task('build',
- gulp.series('instructions',
- gulp.parallel('css', 'js', 'docs:install', 'jekyll:build')
- )
-);
diff --git a/_gulp/tasks/css.js b/_gulp/tasks/css.js
deleted file mode 100644
index 71f4c5a03..000000000
--- a/_gulp/tasks/css.js
+++ /dev/null
@@ -1,41 +0,0 @@
-var gulp = require('gulp'),
- sass = require('gulp-sass'),
- sourcemaps = require('gulp-sourcemaps'),
- autoprefixer = require('gulp-autoprefixer'),
- globbing = require('gulp-css-globbing'),
- env = require('gulp-environments'),
- del = require('del'),
- gutil = require('gulp-util'),
- browserSync = require('browser-sync');
-
-var config = require('../config');
-
-gulp.task('css:clean', function(done) {
- return del([config.css.dest],
- done);
-});
-
-var css = function() {
- try {
- var server = browserSync.get('Server');
- } catch(err) {
- var server = null;
- }
-
- return gulp.src(config.css.src)
- .pipe(env.development(sourcemaps.init()))
- .pipe(globbing({
- extensions: ['.scss']
- }))
- .pipe(env.development(sass())
- .on('error', sass.logError))
- .pipe(env.production(sass()))
- .pipe(autoprefixer({
- browsers: ['last 2 version']
- }))
- .pipe(env.development(sourcemaps.write('.')))
- .pipe(gulp.dest(config.css.dest))
- .pipe(server ? server.stream({match: '**/*.css'}) : gutil.noop());
-}
-
-gulp.task('css', gulp.series('css:clean', css));
diff --git a/_gulp/tasks/docs.js b/_gulp/tasks/docs.js
deleted file mode 100644
index 31ff68c33..000000000
--- a/_gulp/tasks/docs.js
+++ /dev/null
@@ -1,45 +0,0 @@
-var gulp = require('gulp'),
- child = require('child_process'),
- git = require('gulp-git'),
- del = require('del'),
- zip = require('gulp-zip'),
- rename = require('gulp-rename');
-
-var docs_make = function(done) {
- return child.spawn('./_docs.sh', ['install'], {stdio: 'inherit', cwd: '.'})
- .on('close', done);
-}
-
-var docs_clean = function(done) {
- return del('./_site/docs', done);
-}
-
-var docs_html = function() {
- return gulp.src(['./_docs/certbot/docs/_build/html/**'],
- {base: './_docs/certbot/docs/_build/html/'})
- .pipe(gulp.dest('./_site/docs'));
-}
-
-var docs_zip = function() {
- return gulp.src('./_docs/certbot/docs/_build/html/**')
- .pipe(zip('certbot.zip'))
- .pipe(gulp.dest('./_site/docs'));
-}
-
-var docs_epub = function() {
- return gulp.src(['./_docs/certbot/docs/_build/epub/Certbot.epub'])
- .pipe(rename('certbot.epub'))
- .pipe(gulp.dest('./_site/docs'));
-}
-
-var docs_pdf = function() {
- return gulp.src(['./_docs/certbot/docs/_build/latex/Certbot.pdf'])
- .pipe(rename('certbot.pdf'))
- .pipe(gulp.dest('./_site/docs'));
-}
-
-gulp.task('docs:install',
- gulp.series(docs_clean, docs_make, docs_html, gulp.parallel(
- docs_zip, docs_epub, docs_pdf
- ))
-);
diff --git a/_gulp/tasks/instructions.js b/_gulp/tasks/instructions.js
deleted file mode 100644
index 549f35e89..000000000
--- a/_gulp/tasks/instructions.js
+++ /dev/null
@@ -1,44 +0,0 @@
-var gulp = require('gulp'),
- webpackRequire = require('webpack-require'),
- del = require('del'),
- fs = require('fs');
-
-var config = require('../config');
-
-gulp.task('instructions:clean', function(done) {
- return del([config.instructions.dest],
- done);
-});
-
-// Write all certbot install and get started instruction sets to
-// a single json file, to be consumed by Jekyll templates.
-gulp.task('instructions', gulp.series('instructions:clean', (done) => {
- // We need to run the instruction widget modules with webpack loaders
- // in order to properly require mustache templates.
- webpackRequire(
- {
- module: {
- loaders: [
- {test: /\.json$/, loader: 'json'},
- {test: /\.html$/, loader: 'mustache?noShortcut'}
- ]
- }
- },
- require.resolve('./../../_scripts/instruction-widget/build-all.js'),
- function(err, factory, stats, mock_fs) {
-
- var dir = './_instructions'
- if (!fs.existsSync(dir)){
- fs.mkdirSync(dir);
- }
-
- var instructions = factory().build()
- instructions.forEach(function(el) {
- var path = dir + '/' + el.os.id + '-' + el.server.id + '.md';
- var body = '---\n---\n' + el.instructions;
- fs.writeFile(path, body, function() {});
- });
- done();
- }
- );
-}));
diff --git a/_gulp/tasks/jekyll.js b/_gulp/tasks/jekyll.js
deleted file mode 100644
index 75386134a..000000000
--- a/_gulp/tasks/jekyll.js
+++ /dev/null
@@ -1,19 +0,0 @@
-var gulp = require('gulp'),
- child = require('child_process');
-
-var jekyll_watch = function(done) {
- return child.spawn('jekyll', ['build',
- '--watch',
- '--incremental'],
- {stdio: 'inherit'})
- .on('close', done);
-}
-
-var jekyll_build = function(done) {
- return child.spawn('jekyll', ['build'],
- {stdio: 'inherit'})
- .on('close', done);
-}
-
-gulp.task('jekyll:watch', jekyll_watch);
-gulp.task('jekyll:build', jekyll_build);
diff --git a/_gulp/tasks/js.js b/_gulp/tasks/js.js
deleted file mode 100644
index 6ab104d43..000000000
--- a/_gulp/tasks/js.js
+++ /dev/null
@@ -1,55 +0,0 @@
-var gulp = require('gulp'),
- env = require('gulp-environments'),
- del = require('del'),
- webpack = require('gulp-webpack');
-
-var config = require('../config');
-
-config.webpack = {
- entry: {
- main: './_scripts/main',
- instructions: './_scripts/instruction-widget/main',
- },
- output: {
- filename: '[name].js',
- },
- devtool: env.development() ? "source-map" : "",
- module: {
- loaders: [
- {test: /\.json$/, loader: 'json'},
- {test: /\.html$/, loader: 'mustache?noShortcut'}
- ],
- rules: [
- { test: require.resolve('jquery'), loader: 'expose-loader?$!expose-loader?jQuery' },
- ]
- },
- plugins: env.production() ? [
- new webpack.webpack.optimize.UglifyJsPlugin({
- compress: { warnings: false }
- }),
- new webpack.webpack.ProvidePlugin({
- '$': 'jquery',
- 'jQuery': 'jquery',
- 'window.jQuery': 'jquery'
- }),
- ] : [
- new webpack.webpack.ProvidePlugin({
- '$': 'jquery',
- 'jQuery': 'jquery',
- 'window.jQuery': 'jquery'
- }),
- ],
- bail: env.production()
-}
-
-var js_clean = function(done) {
- return del([config.js.dest], done);
-}
-
-var js = function() {
- return gulp.src(config.js.src)
- .pipe(webpack(config.webpack))
- .pipe(gulp.dest(config.js.dest));
-}
-
-gulp.task('js', gulp.series(js_clean, js));
diff --git a/_gulp/tasks/serve.js b/_gulp/tasks/serve.js
deleted file mode 100644
index 27fca2092..000000000
--- a/_gulp/tasks/serve.js
+++ /dev/null
@@ -1,37 +0,0 @@
-var gulp = require('gulp'),
- browserSync = require('browser-sync');
-
-var config = require('../config');
-var server = browserSync.create('Server');
-
-var reload = function(done) {
- server.reload();
- done();
-}
-
-gulp.task('serve', (done) => {
- server.init({
- port: 4000,
- server: {
- baseDir: config.site_root,
- serveStaticOptions: {
- extensions: ['html']
- }
- },
- middleware: function(req, res, next) {
- req.url = req.url.replace(/\?server=(.*)&os=(.*)/, "/$2-$1")
- return next();
- },
- ghostMode: false,
- notify: false,
- open: false
- });
-
- gulp.watch(config.css.src, gulp.series('css'));
- gulp.watch(config.js.src, gulp.series('js'));
- gulp.watch([config.site_root + '/**/*.html',
- config.site_root + '/**/*.js',
- '!' + config.site_root + '/docs/**/*'],
- reload);
- done();
-});
diff --git a/_includes/contrib/code_list.html b/_includes/contrib/code_list.html
deleted file mode 100644
index 2eac79d79..000000000
--- a/_includes/contrib/code_list.html
+++ /dev/null
@@ -1,15 +0,0 @@
-
- If you’re a software developer, come talk to us on Mattermost (see above). The team focuses on a few issues at a time, so it’s best to check in with us.
-
-
-
- Chat with us about an idea you’re excited to implement
-
- If you’re having trouble with your setup, check out the community forums. If you’re reasonably sure that you’ve found a bug in Certbot code, post an issue on our Github.
-
-
-
- <3 Donate!
-
- If you love this project, we’d appreciate the help. Certbot is a free and open source project from the Electronic Frontier Foundation.
-
-
- Looking for ways to configure Certbot? Read the Certbot documentation.
-
-
The Certbot developers and volunteers have contributed to this documentation on Read the Docs.
-
-
-
- Not sure how to set up your web server? Check out an external tutorial.
-
-
DigitalOcean has great guides for setting up a web server on a particular operating system, no matter your hosting provider. Try searching for your operating system along with “web server”, “nginx”, or “apache” on their tutorials page.
-
-
-
- Wondering what a particular term means? Check out our glossary.
-
-
We created a glossary of terms that are important to understanding the HTTPS ecosystem.
-
-
-
- Looking for a shared hosting provider that offers free HTTPS certificates without needing to install Certbot?
-
-
-
- your {% include tooltip.html term-name="domain-name" text="website domain" %} (http://example.com)
- might be purchased from a {% include tooltip.html term-name="domain-registrar" text="domain registrar" %} company
-
-
-
-
-
-
-
- a {% include tooltip.html term-name="server" text="server" %} hosts your website
-
-
-
-
-
-
-
- and this server might be provided by a {% include tooltip.html term-name="hosting-provider" text="hosting provider" %}
-
-
Good news! You have HTTPS, but you need to follow a tutorial to turn it on.
-
-
-
-
-
-
-
-
No HTTPS Support
-
HTTPS isn't included in the shared hosting packages of these providers
-
-
- Consider switching hosting providers or to a more manual hosting product like
- {% include tooltip.html term-name="virtual-private-server" text="VPS" %} or
- {% include tooltip.html term-name="dedicated-server" text="dedicated servers" %}
-
-
-
-
-
hosting provider
-
-
category
-
relevant link
-
last reviewed by us
-
note
-
-
-
- {% for host in site.data.hosting_providers %}
-
- comfort with the {% include tooltip.html term-name="command-line" text="command line" %}
-
-
-
-
-
-
- ...and an
- {% include tooltip.html term-name="http" text="HTTP website" %}
-
- that is {% include tooltip.html term-name="website-thats-already-online" text="already online" %}
-
- with an open {% include tooltip.html term-name="port-80" text="port 80" %}
-
-
-
-
-
-
-
- ...which is hosted on a {% include tooltip.html term-name="server" text="server" %}
-
- which you can access via {% include tooltip.html term-name="ssh" %}
-
- with the ability to {% include tooltip.html term-name="sudo" %}
-
-
-
- optional if you want a {% include tooltip.html term-name="wildcard-certificate" text="wildcard cert" %}:
- {% include tooltip.html term-name="dns-credentials" text="DNS credentials" %}
-
-
- {{#advanced}}
- Run one of the commands in the "Examples" section of the instructions for your DNS provider,
- along with the flag -i apache.
- {{/advanced}}
- {{^advanced}}
- Run this command to get a certificate and have Certbot edit your Apache configuration
- automatically to serve it, turning on HTTPS access in a single step.
-
sudo {{base_command}} --apache
- {{/advanced}}
-
-
-
-
- Or, just get a certificate
-
- {{#advanced}}
- Run one of the commands in the "Examples" section of the instructions for your DNS provider.
- {{/advanced}}
- {{^advanced}}
- If you're feeling more conservative and would like to make the changes to your Apache
- configuration by hand, run this command.
-
- Are you ok with temporarily stopping your website?
-
-
Yes, my web server is not currently running on this machine.
-
- Stop your webserver, then run this command to get a certificate.
- Certbot will temporarily spin up a webserver on your machine.
-
- sudo {{base_command}} certonly --standalone
-
-
-
No, I need to keep my web server running.
-
- If you have a webserver that's already using port 80 and don't want to stop it
- while Certbot runs, run this command and follow the instructions in the terminal.
-
- sudo {{base_command}} certonly --webroot
-
-
-
-
-{{/advanced}}
-
-
- Install your certificate
-
- You'll need to install your new certificate in the configuration file for
- your webserver.
-
- {{#advanced}}
- Run one of the commands in the "Examples" section of the instructions for your DNS provider,
- along with the flag -i nginx.
- {{/advanced}}
- {{^advanced}}
- Run this command to get a certificate and have Certbot edit your Nginx configuration
- automatically to serve it, turning on HTTPS access in a single step.
-
sudo {{base_command}} --nginx
- {{/advanced}}
-
-
-
- Or, just get a certificate
-
- {{#advanced}}
- Run one of the commands in the "Examples" section of the instructions for your DNS provider.
- {{/advanced}}
- {{^advanced}}
- If you're feeling more conservative and would like to make the changes to your Nginx
- configuration by hand, run this command.
-
-For Plesk you won't even need to install Certbot. Instead, use the extension already available in Plesk — it will also give you automatic renewal of your certificates out-of-the-box as well! Read more about the extension here.
-
- The Certbot packages on your system come with a cron job or systemd timer that will renew your certificates
- automatically before they expire. You will not need to run Certbot again, unless you change your
- configuration. You can test automatic renewal for your certificates by running this command:
-
sudo {{base_command}} renew --dry-run
-
-
-
- The command to renew certbot is installed in one of the following locations:
-
-
/etc/crontab/
-
/etc/cron.*/*
-
systemctl list-timers
-
-
-
- {{#certonly}}
-
- If you needed to stop your webserver to run Certbot, you'll want to add hook
- scripts to stop and start your webserver automatically. For example, if your
- webserver is HAProxy, run the following commands:
-
-
-
sudo sh -c 'printf "#!/bin/sh\nservice haproxy stop\n" > /etc/letsencrypt/renewal-hooks/pre/haproxy.sh'
-
sudo sh -c 'printf "#!/bin/sh\nservice haproxy start\n" > /etc/letsencrypt/renewal-hooks/post/haproxy.sh'
- If you needed to stop your webserver to run Certbot, you'll want to
- add --pre-hook and --post-hook flags after {{base_command}} renew to stop
- and start your webserver automatically. For example, if your webserver is HAProxy, modify the
- command as follows:
-
-
- To confirm that your site is set up properly, visit https://yourwebsite.com/ in your browser and
- look for the lock icon in the URL bar.
- If you want to check that you have the top-of-the-line installation, you can head to
- https://www.ssllabs.com/ssltest/.
-
If your hosting provider has full support for HTTPS: good news! You won’t have to do anything further
-
-
If your hosting provider has partial support for HTTPS: good news! You can follow along the linked tutorials for that individual web hosting provider, and get your website on HTTPS without needing Certbot.
-
-
If your hosting provider does not support HTTPS: continue to the steps below.
-
-
If your hosting provider does not support HTTPS, the following options are available:
-
-
You can contact your web hosting provider: tell them you want a free HTTPS certificate through Let’s Encrypt.
-You’re probably not the only one using your web hosting provider service who wants HTTPS. You can request that your web hosting provider offer Let’s Encrypt HTTPS certificates as a free part of their hosting package. An effective way to make this ask is through email, their help desk system, or by contacting the web hosting provider through social media.
-
-
You can switch to a different web hosting provider.
-Find a web hosting provider who offers full HTTPS support as part of their web hosting package by checking our list.
-
-
You might be able to use Certbot.
-If you have SSH access to the server your website is hosted on, you might be able to use Certbot. You will need to know the software and system your server is running on. After you confirm the software and system information, you can use the dropdown menus above to generate specific instructions for running Certbot on your server through the command line.
-
-
-
-
-
-Was this information helpful?
-Certbot is a free project provided by the
-Electronic Frontier Foundation, a 501(c)3 nonprofit.
-We’d be grateful for your support.
-Certbot is now officially available for Windows. If you find that Certbot is not
-the most suitable Let's Encrypt client application for your use case, there are
-many
-other clients written by other organizations and developers that you may be
-able to use to obtain a certificate from Let's Encrypt.
-
-
-
-
Important notes
-
This procedure follows the current Certbot implementation for Windows, in particular the fact that it installs as a system component, and requires administrative privileges. These instructions will be updated when a future version of Certbot switches to a different installation method.
- No installers for HTTP servers are supported for now (Certbot for Windows can currently obtain your certificate from
- Let's Encrypt, but not install it into your web server application).
-
-
-
Specific Windows system requirements and user knowledge requirements
-
-
-
The user needs to be familiar with the command-line interface (CLI), because Certbot is a pure CLI program.
-
The user must use an account with administrative privileges to install and run Certbot.
-
PowerShell and CMD.EXE are supported; both need to be started with elevated privileges before invoking Certbot.
-
Path C:\Certbot must be writable by the current user.
-
-
-
-
-
Specific Windows limitations and configuration
-
-
-
All usual operations to create and manage an account, manage existing certificates, or select the ACME server, are supported.
-
Only standalone, manual and webroot authenticator plugins are supported. DNS plugins will be available soon. This means that Certbot for Windows is currently unable to automatically renew wildcard certificates, since these require a DNS plugin in order to be renewed without user intervention.
-
No installer plugins are supported. The Apache and Nginx plugins will be available soon, and a plugin to install certificates into IIS is under development.
-
Automated certificate renewals (using standalone and webroot plugins) are supported.
-
-
-
-
-
Installation instructions (default)
-
-
-
Connect to the server.
-
Connect locally or remotely (using Remote Desktop) to the server using an account that has administrative privileges for this machine.
Run the installer and follow the wizard. The installer will propose a default installation directory, C:\Program Files(x86), that can be customized.)
-
To start a shell for Certbot, select the Start menu, enter cmd (to run CMD.EXE) or powershell (to run PowerShell), and click on “Run as administrator” in the contextual menu that shows up above.
-
Run Certbot as a shell command.
-
-
-
To run a command on Certbot, enter the name certbot in the shell, followed by the command and its parameters. For instance, to display the inline help, run:
-
-
C:\WINDOWS\system32> certbot --help
-
-
-
-
Choose how you’d like to run Certbot
-
-
Are you ok with temporarily stopping your website?
-
-
Yes, my web server is not currently running on this machine.
-
Stop your webserver, then run this command to get a certificate.
- Certbot will temporarily spin up a webserver on your machine.
- If you have a webserver that's already using port 80 and don't want to stop it
- while Certbot runs, run this command and follow the instructions in the terminal.
You'll need to install your new certificate in the configuration file or interface for your webserver. Certificates are located in C:\Certbot\live\[certificate_name], where [certificate_name] is the name of your certificate (usually the first domain if the --cert-name flag has not been used on the certonly command). Currently, Certbot for Windows cannot automate the installation step; future versions will be able to automate it for specific webserver applications.
-
-
-
Test automatic renewal
-
-
The Certbot installation on your system comes with a pre-installed Scheduled Task that will renew your certificates automatically before they expire. You will not need to run Certbot again, unless you change your configuration. You can test automatic renewal for your certificates by running the command
-
-
C:\WINDOWS\system32> certbot renew --dry-run
-
-
If you needed to stop your webserver to run Certbot (for example, if you used the standalone authenticator on a machine where port 80 is normally in use), you'll want to edit the built-in command to add the --pre-hook and --post-hook flags to stop and start your webserver automatically. For example, if your webserver is Apache 2.4, add the following to the certbot renew command:
More information is available in the Certbot documentation on renewing certificates.
-
-
Confirm that Certbot worked
-
-
- To confirm that your site is set up properly, visit https://yourwebsite.com/ in your browser and
- look for the lock icon in the URL bar.
- If you want to check that you have the top-of-the-line installation, you can head to
- https://www.ssllabs.com/ssltest/.
-
As described in section 5 above, Certbot for Windows currently cannot install the certificate in Apache or Nginx for you. As of the most recent release, you will have to edit your web server application’s configuration to install the certificate yourself after Certbot has obtained it. If this limitation is acceptable to you, please start from the beginning of this document to learn more about installing and using Certbot on Windows.
- You'll need to enable the EPEL (Extra Packages for Enterprise Linux)
- repository and make sure you follow all instructions for your system,
- including enabling any other recommended repositories that may be
- required.
- Follow these instructions at
-
- the Fedora wiki to enable EPEL.
-
- You'll need to set up DNS credentials.
- Follow the steps in the "Credentials" section for your DNS provider to access or create the
- appropriate credential configuration file. Find credentials instructions for your DNS provider
- by clicking the DNS plugin's name on the Documentation list.
-
- You'll need to install snapd and make sure you follow any instructions to enable classic snap support.
- Follow these instructions on snapcraft's site to install snapd.
-
- If you have any Certbot packages installed using an OS package manager like
- apt, dnf, or yum, you should remove them before
- installing the Certbot snap to ensure that when you run the command
- certbot the snap is used rather than the installation from your OS
- package manager. The exact command to do this depends on your OS, but
- common examples are sudo apt-get remove certbot, sudo dnf
- remove certbot, or sudo yum remove certbot.
-
- Run this command on the command line on the machine to acknowledge that the installed
- plugin will have the same classic containment as the Certbot snap.
-
-
sudo snap set certbot trust-plugin-with-root=ok
-
-
- If you encounter issues with running Certbot, you may need to follow this step, then
- the "Install correct DNS plugin" step, again.
-
- You'll need to add the Certbot PPA to your list of repositories. To do so,
- run the following commands on the command line on the machine:
-
sudo apt-get update
-
sudo apt-get install software-properties-common
-
sudo add-apt-repository universe
-
sudo add-apt-repository ppa:certbot/certbot
-
sudo apt-get update
-
-
-{{/ppa}}
-{{^ppa}}
-
- Enable the universe repository
-
- You'll need to make sure Ubuntu universe is in your list of repositories.
- To do so, run the following commands on the command line on the machine:
-
diff --git a/_scripts/main.js b/_scripts/main.js
deleted file mode 100644
index 467c13070..000000000
--- a/_scripts/main.js
+++ /dev/null
@@ -1,123 +0,0 @@
-// js loaded on every page goes here.
-
-/**
- * Client-side code for the Certbot website.
- * Copyright (C) 2016 Electronic Frontier Foundation
- *
- * This program is free software: you can redistribute it and/or modify
- * it under the terms of the GNU Affero General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU Affero General Public License for more details.
- *
- * You should have received a copy of the GNU Affero General Public License
- * along with this program. If not, see .
- */
-
-var Raven = require('raven-js');
-var $ = require('jquery');
-var dt = require('datatables.net');
-
-(function (Raven) {
- 'use strict';
- Raven.config('https://caa5edd9fc344ff69a3e0bd4c05a5a91@sentry.eff.org/20').install();
-})(Raven);
-
-(function() {
- [].forEach.call(document.querySelectorAll('.js-only'), function (el) {
- el.style.visibility = 'visible';
- });
-
- [].forEach.call(document.querySelectorAll('.no-js-only'), function (el) {
- el.style.visibility = 'hidden';
- });
-
- var hamburger = document.getElementById('hamburger');
- var close = document.getElementById('close');
-
- hamburger.addEventListener('click',toggleMenu,false);
- close.addEventListener('click',toggleMenu,false);
-
- function toggleMenu() {
- document.body.classList.toggle('active');
- }
-})();
-
-$(document).ready(function() {
- $('.glossary-term.no-js').remove();
- $('.glossary-term.js-only').removeClass('disabled');
- // Tooltips
- $('.glossary-link').click(function() {
- $('.tooltip').removeClass('open');
- var glossDiv = $(this).parents('.glossary-term');
- $(glossDiv).children('.tooltip').addClass('open');
- });
- $(document).on('click', function(e) {
- if (!$(e.target).closest('.glossary-term').length)
- $('.tooltip').removeClass('open');
- });
- $(document).on('keydown', function(e) {
- if (e.which == 27) {
- $('.tooltip').removeClass('open');
- }
- });
- $('.close-button').on('click', function(e) {
- $('.tooltip').removeClass('open');
- });
- var hosting_table = $('#hosting-providers').DataTable({
- "paging": false,
- "info": false,
- "scrollX": true,
- "responsive": true,
- "language": {
- "search": "Search for your hosting provider"
- }
- });
- hosting_table.column('.category').visible(false);
- $('#all-bounce').on('click', function() {
- $('#all-https').click();
- });
- $('#full-bounce').on('click', function() {
- $('#full-https').click();
- });
- $('#partial-bounce').on('click', function() {
- $('#partial-https').click();
- });
- $('#no-bounce').on('click', function() {
- $('#no-https').click();
- });
- $('#all-https').on('click', function() {
- hosting_table.columns().search('').column('.category').draw();
- $('.tab-header-wrapper').removeClass('visible');
- $('#all-header').addClass('visible');
- $('.hosting-tab').removeClass('active');
- $(this).addClass('active');
- });
- $('#full-https').on('click', function() {
- hosting_table.columns().search('').column('.category').search('full').draw();
- $('.tab-header-wrapper').removeClass('visible');
- $('#full-header').addClass('visible');
- $('.hosting-tab').removeClass('active');
- $(this).addClass('active');
-
- });
- $('#partial-https').on('click', function() {
- hosting_table.columns().search('').column('.category').search('partial').draw();
- $('.tab-header-wrapper').removeClass('visible');
- $('#partial-header').addClass('visible');
- $('.hosting-tab').removeClass('active');
- $(this).addClass('active');
- });
- $('#no-https').on('click', function() {
- hosting_table.columns().search('').column('.category').search('no').draw();
- $('.tab-header-wrapper').removeClass('visible');
- $('#no-header').addClass('visible');
- $('.hosting-tab').removeClass('active');
- $(this).addClass('active');
- });
- $('#all-https').click();
-});
diff --git a/_terms/.command_line.md.swp b/_terms/.command_line.md.swp
deleted file mode 100644
index eb490ed86..000000000
Binary files a/_terms/.command_line.md.swp and /dev/null differ
diff --git a/_terms/admin-access.md b/_terms/admin-access.md
deleted file mode 100644
index 5ed1210e5..000000000
--- a/_terms/admin-access.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Admin Access
-lookup: admin-access
----
-You have administrative access to a server if you are the person who can control that server and perform administrative tasks like installing and removing software or changing the system as a whole. This is often also called “root access.” If you can successfully run “sudo” on a server, you have admin access. This is probably the case if you use a VPS or dedicated server or if someone else has set up the server just for you. It’s probably not the case if you use a shared server or if you can only ever interact with the server via FTP, SFTP, or a control panel interface.
diff --git a/_terms/automatic-renewal.md b/_terms/automatic-renewal.md
deleted file mode 100644
index 7f1b7ec53..000000000
--- a/_terms/automatic-renewal.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Automatic Renewal
-lookup: automatic-renewal
----
-In the context of Certbot, this refers to a feature designed to automatically obtain new versions of a certificate before it expires. This feature is important as helps you avoid gaps between having valid certificates that can be trusted by the users of your server.
\ No newline at end of file
diff --git a/_terms/automatic-updates.md b/_terms/automatic-updates.md
deleted file mode 100644
index 023e14aef..000000000
--- a/_terms/automatic-updates.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Automatic Updates
-lookup: automatic-updates
----
-Automatic updates are when a piece of software downloads a new version of itself automatically, usually as soon as practical after it becomes available. This process is designed to help the software have the latest bug fixes and features that have been released by the developer.
\ No newline at end of file
diff --git a/_terms/backports.md b/_terms/backports.md
deleted file mode 100644
index e71d1638d..000000000
--- a/_terms/backports.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Backports
-lookup: backports
----
-Backports is a feature in some operating systems that provides an option for getting newer versions of software than those that your operating system package manager would otherwise provide you.
-The installation instructions for Certbot in some environments may ask you to follow instructions for enabling the backports feature on your operating system.
\ No newline at end of file
diff --git a/_terms/browser.md b/_terms/browser.md
deleted file mode 100644
index b4c0689e5..000000000
--- a/_terms/browser.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Browser
-lookup: browser
----
-A browser is the program you use to view websites on the Internet. Firefox, Safari, Internet Explorer, and Chrome are all web browsers. Mobile devices have a web browser app for the same purpose.
diff --git a/_terms/certificate-authority.md b/_terms/certificate-authority.md
deleted file mode 100644
index 842bc7d40..000000000
--- a/_terms/certificate-authority.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Certificate Authority
-lookup: certificate-authority
----
-A certificate authority is an organization that gives out certificates to website operators.
\ No newline at end of file
diff --git a/_terms/certificate.md b/_terms/certificate.md
deleted file mode 100644
index 20ba2160e..000000000
--- a/_terms/certificate.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Certificate
-lookup: certificate
----
-A certificate is a file that mathematically shows browsers or other software that they’ve made an encrypted connection to the site they attempted to connect to.
\ No newline at end of file
diff --git a/_terms/cloud-hosting.md b/_terms/cloud-hosting.md
deleted file mode 100644
index 61f739224..000000000
--- a/_terms/cloud-hosting.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Cloud Hosting
-lookup: cloud-hosting
----
-Cloud hosting can refer to any situation in which your web site is hosted using someone else's infrastructure, typically on servers belonging to a web hosting company. This could be contrasted with a web site that's hosted on your own personal server, such as a physical machine running in your home.
\ No newline at end of file
diff --git a/_terms/command-line.md b/_terms/command-line.md
deleted file mode 100644
index fbc65e7c5..000000000
--- a/_terms/command-line.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Command Line
-lookup: 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.
\ No newline at end of file
diff --git a/_terms/control-panel.md b/_terms/control-panel.md
deleted file mode 100644
index 9b8beda23..000000000
--- a/_terms/control-panel.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Control Panel
-lookup: control-panel
----
-A control panel is a type of software that provides an interface for configuring websites, such as cPanel.
\ No newline at end of file
diff --git a/_terms/cron-job.md b/_terms/cron-job.md
deleted file mode 100644
index f992fe7ad..000000000
--- a/_terms/cron-job.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Cron Job
-lookup: cron-job
----
-A cron job is a task to be run at a scheduled time by the program cron.
\ No newline at end of file
diff --git a/_terms/crontab.md b/_terms/crontab.md
deleted file mode 100644
index eadc5e110..000000000
--- a/_terms/crontab.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Crontab
-lookup: crontab
----
-The “cron table” is a specific file that contains tasks to be run at a scheduled time by the program cron.
\ No newline at end of file
diff --git a/_terms/dedicated-server.md b/_terms/dedicated-server.md
deleted file mode 100644
index 5a426c22b..000000000
--- a/_terms/dedicated-server.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Server - Dedicated Server
-lookup: dedicated-server
----
-A dedicated server is a server that only hosts the contents or services for a single website administrator.
\ No newline at end of file
diff --git a/_terms/dns-credentials.md b/_terms/dns-credentials.md
deleted file mode 100644
index 27433067a..000000000
--- a/_terms/dns-credentials.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: DNS Credentials
-lookup: 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.
\ No newline at end of file
diff --git a/_terms/dns-provider.md b/_terms/dns-provider.md
deleted file mode 100644
index 275c2a6d7..000000000
--- a/_terms/dns-provider.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: DNS Provider
-lookup: dns-provider
----
-A Domain Name System (DNS) provider is an organization that runs DNS servers (also called nameservers) to host DNS records for domain names. Your DNS provider could be the same as, or different from, your DNS registrar (whom you pay to register your domain name), or your hosting provider (whom you pay to host your web site). You can also change your DNS provider if your current provider doesn’t offer the features that you want. Your DNS provider must follow various Internet technical standards in order for Let’s Encrypt to confirm that it’s you who controls your domain name when you request a certificate. You need to interact with your DNS provider in order to change the DNS records that refer to your domain name.
-Some DNS providers can help you create Let’s Encrypt certificates (including wildcard certificates) easily using Let’s Encrypt’s DNS validation method, including by providing a software interface that Certbot can use for updating DNS records automatically.
\ No newline at end of file
diff --git a/_terms/dns-record.md b/_terms/dns-record.md
deleted file mode 100644
index fb219665b..000000000
--- a/_terms/dns-record.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: DNS Record
-lookup: dns-record
----
-A DNS record is an entry in a nameserver that tells machines on the Internet some information about the domain. For example, an “A record” describes which IPv4 address a particular domain name should point to.
\ No newline at end of file
diff --git a/_terms/dns-validation.md b/_terms/dns-validation.md
deleted file mode 100644
index 3198c5a3e..000000000
--- a/_terms/dns-validation.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: DNS Validation
-lookup: dns-validation
----
-DNS validation is a method to prove your control over your domain name by asking you to create specific DNS TXT records within the domain. This requires you to have appropriate credentials to change your DNS records. DNS validation is one of the options provided by Let’s Encrypt to prove your control over your domain name.
-If you have a DNS provider that’s supported by Certbot, Certbot can automate this process. Otherwise, you would have to perform it yourself every time you renew your certificate. Most Certbot users don’t need to perform DNS validation, but it’s required by Let’s Encrypt if you want a wildcard certificate, and it can also be a useful option if your web server can’t receive connections from the Internet (for example, because it’s on a private network behind a firewall).
\ No newline at end of file
diff --git a/_terms/dns.md b/_terms/dns.md
deleted file mode 100644
index f6c47d737..000000000
--- a/_terms/dns.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: DNS
-lookup: dns
----
-DNS is the Domain Name System which creates a worldwide directory of domain names, like example.com, certbot.eff.org, community.letsencrypt.org, or millions of others. These domain names can be looked up by Internet users’ software anywhere in the world to learn IP addresses and other technical data that’s used to make connections to servers. DNS is an important part of Internet infrastructure and is operated collectively by hundreds of organizations, including DNS registrars (which let you pay to register your own domain name for your own site) and various DNS providers.
\ No newline at end of file
diff --git a/_terms/docker.md b/_terms/docker.md
deleted file mode 100644
index 6ea73df4d..000000000
--- a/_terms/docker.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Docker
-lookup: docker
----
-Docker is a system that allows website operators to run pre-configured systems called “containers” inside of their server. These containers come with everything needed to perform a task.
-Certbot’s Docker containers ship with Certbot already set up inside of them.
\ No newline at end of file
diff --git a/_terms/domain-name.md b/_terms/domain-name.md
deleted file mode 100644
index e1a3f2d9b..000000000
--- a/_terms/domain-name.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Domain Name
-lookup: domain-name
----
-A domain name is a human-readable identifier for a website that someone can type into the URL bar of their browser to go to that website. The domain name doesn’t include the parts of the URL after the first single slash mark (/).
\ No newline at end of file
diff --git a/_terms/domain-registrar.md b/_terms/domain-registrar.md
deleted file mode 100644
index aaaf88e56..000000000
--- a/_terms/domain-registrar.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Domain Registrar
-lookup: domain-registrar
----
-A domain registrar is an organization that website operators purchase domains from.
\ No newline at end of file
diff --git a/_terms/firewall.md b/_terms/firewall.md
deleted file mode 100644
index 5ed233881..000000000
--- a/_terms/firewall.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Firewall
-lookup: firewall
----
-A firewall monitors and controls network traffic on a machine.
\ No newline at end of file
diff --git a/_terms/ftp.md b/_terms/ftp.md
deleted file mode 100644
index 4329ab7ed..000000000
--- a/_terms/ftp.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: FTP
-lookup: ftp
----
-The File Transfer Protocol (FTP) allows users to move files from one machine to another over the network.
\ No newline at end of file
diff --git a/_terms/hosting-provider.md b/_terms/hosting-provider.md
deleted file mode 100644
index 0b6d0f2a0..000000000
--- a/_terms/hosting-provider.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Hosting Provider
-lookup: hosting-provider
----
-A hosting provider is a company or other organization that helps you get your website online. Hosting providers are usually paid by a customer and offer a variety of different plans and services, including shared hosting, virtual private servers, and dedicated servers. Their servers are usually located in data centers, and the sites or servers they host are usually administered remotely over the Internet.
\ No newline at end of file
diff --git a/_terms/http.md b/_terms/http.md
deleted file mode 100644
index 93abe60bf..000000000
--- a/_terms/http.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: HTTP
-lookup: 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.
\ No newline at end of file
diff --git a/_terms/https.md b/_terms/https.md
deleted file mode 100644
index 5d2650a03..000000000
--- a/_terms/https.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: HTTPS
-lookup: https
----
-HTTPS (Hypertext Transfer Protocol Secure) is the update to HTTP that uses the SSL/TLS protocol to provide security for connections between web browsers and web servers. Using HTTPS normally requires a certificate from a certificate authority, such as Let’s Encrypt, and will also require installing that certificate onto a web server.
-Certbot can help perform both of these steps automatically in many cases. HTTPS is an Internet standard and is normally used with TCP port 443.
\ No newline at end of file
diff --git a/_terms/internet-service-provider.md b/_terms/internet-service-provider.md
deleted file mode 100644
index ba5ecc411..000000000
--- a/_terms/internet-service-provider.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Internet Service Provider
-lookup: internet-service-provider
----
-An Internet Service Provider (ISP) is an organization that people can obtain access to the Internet from.
\ No newline at end of file
diff --git a/_terms/ip-address.md b/_terms/ip-address.md
deleted file mode 100644
index d8f0aa286..000000000
--- a/_terms/ip-address.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: IP Address
-lookup: ip-address
----
-An IP address is a group of numbers, like 198.51.100.55, that identify a computer on the Internet and allow other computers to talk to it.
\ No newline at end of file
diff --git a/_terms/lets-encrypt.md b/_terms/lets-encrypt.md
deleted file mode 100644
index f48ca9c01..000000000
--- a/_terms/lets-encrypt.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Let’s Encrypt
-lookup: lets-encrypt
----
-Let’s Encrypt is a certificate authority that issues digital certificates free of charge to let people get encrypted HTTPS connections to web sites on the Internet, which are substantially more secure than unencrypted connections.
-Certbot is a software tool made by the Electronic Frontier Foundation. Certbot is the most popular way for people who run their own web servers to get a Let’s Encrypt certificate, set up HTTPS on the server, and renew the certificate automatically in the future. There are also many other tools and options for people in different situations to get Let’s Encrypt certificates.
\ No newline at end of file
diff --git a/_terms/operating-system.md b/_terms/operating-system.md
deleted file mode 100644
index fb20c8915..000000000
--- a/_terms/operating-system.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Operating System
-lookup: operating-system
----
-The operating system is the core software running on a computer. The most common operating systems are Windows, macOS, and Linux. Linux is subdivided into “distributions” like Ubuntu, Debian, RedHat, and many more.
\ No newline at end of file
diff --git a/_terms/port-443.md b/_terms/port-443.md
deleted file mode 100644
index b0f73f45d..000000000
--- a/_terms/port-443.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Port 443
-lookup: port-443
----
-Port 443 is the port officially assigned for use with HTTPS. 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.
\ No newline at end of file
diff --git a/_terms/port-80.md b/_terms/port-80.md
deleted file mode 100644
index 31ceeff22..000000000
--- a/_terms/port-80.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Port 80
-lookup: 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.)
\ No newline at end of file
diff --git a/_terms/server-plugin.md b/_terms/server-plugin.md
deleted file mode 100644
index 8f594de9a..000000000
--- a/_terms/server-plugin.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Server Plugin
-lookup: server-plugin
----
-In the context of Certbot, this refers to software that works with Certbot to configure a specific piece of server software. For instance, Certbot has an Apache plugin and a nginx plugin which can be used to obtain and configure certificates with those servers.
\ No newline at end of file
diff --git a/_terms/server.md b/_terms/server.md
deleted file mode 100644
index d2de4e29c..000000000
--- a/_terms/server.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Server
-lookup: 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.
\ No newline at end of file
diff --git a/_terms/sftp.md b/_terms/sftp.md
deleted file mode 100644
index 94076e872..000000000
--- a/_terms/sftp.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: SFTP
-lookup: sftp
----
-SFTP is a more-secure version of FTP.
\ No newline at end of file
diff --git a/_terms/shared-hosting.md b/_terms/shared-hosting.md
deleted file mode 100644
index dab8764ae..000000000
--- a/_terms/shared-hosting.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Shared Hosting
-lookup: shared-hosting
----
-Shared hosting is a kind of web hosting in which several customers’ web sites are hosted by the same server, which is mainly administered by the web hosting provider. Usually customers administer their own sites on a shared server using a web-based control panel interface. This is less expensive than VPS hosting and often calls for less technical knowledge on the customer’s part; overall, it’s the most popular type of web hosting environment.
-
-Certbot is less suitable for use in most shared hosting environments because it’s usually easier and more reliable to ask the hosting provider to set up HTTPS. (Some shared hosting users use Certbot, most often because their hosting providers are uncooperative or don’t have another way to enable HTTPS support for customer sites.)
diff --git a/_terms/shared-server.md b/_terms/shared-server.md
deleted file mode 100644
index dc6904938..000000000
--- a/_terms/shared-server.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Server - Shared Server
-lookup: shared-server
----
-A shared server is a server that hosts content or services run by different people on the same machine. A popular version of this is shared hosting, where websites run by different people are provided by the same server that is shared between them.
\ No newline at end of file
diff --git a/_terms/software-repository-or-repo.md b/_terms/software-repository-or-repo.md
deleted file mode 100644
index 8a5742735..000000000
--- a/_terms/software-repository-or-repo.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Software repository or “repo”
-lookup: software-repository-or-repo
----
-A repo is a place where software is stored to be accessed by others. Examples of this include a GitHub repository that contains the files for a software project, or the repositories offered by popular operating systems such as Debian, Fedora, and Ubuntu, which contain many different pieces of software for their users to download and install.
\ No newline at end of file
diff --git a/_terms/software.md b/_terms/software.md
deleted file mode 100644
index 38baab5e7..000000000
--- a/_terms/software.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Software
-lookup: software
----
-Software is a set of instructions that teach a computer how to perform a particular task.
-Certbot is one software application that can be useful for web site administrators who want to set up HTTPS on their web sites. Certbot documentation will also expect you to know the names and versions of some other software that you use on your web server. For instance, the way to install Certbot is different on different operating systems, so you'll be asked the operating system software that your web server uses.
\ No newline at end of file
diff --git a/_terms/ssh.md b/_terms/ssh.md
deleted file mode 100644
index 5de222cab..000000000
--- a/_terms/ssh.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: SSH
-lookup: 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.
\ No newline at end of file
diff --git a/_terms/ssl-tls.md b/_terms/ssl-tls.md
deleted file mode 100644
index 8143e0408..000000000
--- a/_terms/ssl-tls.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: SSL/TLS
-lookup: ssl-tls
----
-SSL, aka TLS, is a protocol used to encrypt data sent between two computers. When you browse the web with encryption using HTTPS (instead of HTTP), your web browser is using SSL/TLS to talk to web sites under the hood. Sometimes SSL and TLS are used to distinguish different protocol versions, but for most common purposes they are synonyms.
\ No newline at end of file
diff --git a/_terms/sudo.md b/_terms/sudo.md
deleted file mode 100644
index dcf29c334..000000000
--- a/_terms/sudo.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: sudo
-lookup: 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.)
\ No newline at end of file
diff --git a/_terms/tcp.md b/_terms/tcp.md
deleted file mode 100644
index 5e4aaf3ae..000000000
--- a/_terms/tcp.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: TCP
-lookup: tcp
----
-TCP is a protocol that allows two computers to send data to each other. More complex protocols like HTTP, HTTPS, SSH, and FTP, are built using TCP as a building block.
\ No newline at end of file
diff --git a/_terms/updates.md b/_terms/updates.md
deleted file mode 100644
index 4d2520d5f..000000000
--- a/_terms/updates.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Updates
-lookup: updates
----
-It is important to keep software up-to-date so that the latest security fixes and features can be applied.
\ No newline at end of file
diff --git a/_terms/virtual-private-server.md b/_terms/virtual-private-server.md
deleted file mode 100644
index 8d73d7868..000000000
--- a/_terms/virtual-private-server.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Server - Virtual Private Server (VPS)
-lookup: virtual-private-server
----
-A virtual private server is a complete server environment within which the customer can control the entire operating system and software environment. That allows the customer to be the system administrator for this server environment. This is the second-most common kind of web hosting environment (following shared hosting), and is offered by major providers like Amazon AWS, Azure, DigitalOcean, and Linode, among others.
-Most successful Certbot users are running Certbot in a VPS environment.
\ No newline at end of file
diff --git a/_terms/web-server.md b/_terms/web-server.md
deleted file mode 100644
index ec15ca407..000000000
--- a/_terms/web-server.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Server - Web Server
-lookup: web-server
----
-“Web server” can refer to either the server (computer), application (software), or the combination of the two that’s used to provide your web site’s content to the rest of the Internet.
\ No newline at end of file
diff --git a/_terms/website-thats-already-online.md b/_terms/website-thats-already-online.md
deleted file mode 100644
index 686b21501..000000000
--- a/_terms/website-thats-already-online.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Website That’s Already Online
-lookup: website-thats-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.)
\ No newline at end of file
diff --git a/_terms/wildcard-certificate.md b/_terms/wildcard-certificate.md
deleted file mode 100644
index fc94ae646..000000000
--- a/_terms/wildcard-certificate.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-title: Wildcard Certificate
-lookup: wildcard-certificate
----
-A wildcard certificate is a certificate that covers one or more names starting with *. and that will be accepted by a web browser for any subdomain name with any label in place of the * character. For example, a certificate for *.example.com will be valid for www.example.com, mail.example.com, hello.example.com, or goodbye.example.com, but not for example.com.
\ No newline at end of file
diff --git a/about/index.md b/about/index.md
deleted file mode 100644
index 01dbc3339..000000000
--- a/about/index.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: page
-title: About Certbot
-class: about
----
-
-
-
-
-
-
-
-## What’s Certbot?
-Certbot is a free, open source software tool for automatically using [Let’s Encrypt](https://letsencrypt.org/) certificates on manually-administrated websites to enable HTTPS.
-
-Certbot is made by the [Electronic Frontier Foundation (EFF)](https://www.eff.org/), a 501(c)3 nonprofit based in San Francisco, CA, that defends digital privacy, free speech, and innovation.
-
-
-
-
-
-
-
-## Is Certbot right for me?
-If you’re looking to add the security and privacy benefits of an HTTPS certificate to your website, you may not need Certbot. Many hosting providers have internal tools to enable HTTPS. Before using Certbot, [check if your hosting provider is one of them](/hosting_providers).
-
-Certbot might be right for you if you:
-
-
- have comfort with the {% include tooltip.html term-name="command-line" text="command line" %},
-
-
- have {% include tooltip.html term-name="website-thats-already-online" text="an HTTP website that’s already online" %}, with {% include tooltip.html term-name="port-80" text="port 80 open" %},
-
-
- and administer your website via a {% include tooltip.html term-name="dedicated-server" text="dedicated server" %}, {% include tooltip.html term-name="virtual-private-server" text="virtual private server" %}, or {% include tooltip.html term-name="cloud-hosting" text="cloud-hosted server" %}, which you can access via {% include tooltip.html term-name="ssh" %}, and have the ability to {% include tooltip.html term-name="sudo" %}.
-
-
-
-If you’re ready to use Certbot, we provide customized instructions for your setup at the [Certbot Instructions](/instructions) page.
-
-Certbot renews certificates every 60 days. For more information about how Certbot works and for community managed resources, check out our [Get Help](/help) page.
-
-For more information around the codebase for Certbot and how to get involved as a developer, check out our [Contribute to Certbot](/contribute) page.
-
-Certbot is part of EFF’s larger effort to [encrypt the entire Internet](https://eff.org/encrypt-the-web). Websites need to use HTTPS to secure the web. Along with [HTTPS Everywhere](https://www.eff.org/https-everywhere), Certbot aims to build a network that is more structurally private, safe, and protected against censorship.
-
-Certbot is the work of [many authors](https://github.com/certbot/certbot/graphs/contributors), including a team of EFF staff and numerous open source contributors.
-
-For more information about privacy practices, check out [Certbot’s privacy policy](/privacy).
-
-Want to keep this project (and other EFF projects) alive? [Donate here](https://supporters.eff.org/donate/support-lets-encrypt).
diff --git a/all-instructions/index.html b/all-instructions/index.html
deleted file mode 100644
index 9710d127c..000000000
--- a/all-instructions/index.html
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: All Instructions
-layout: page
----
-
-
-
diff --git a/build_key.enc b/build_key.enc
deleted file mode 100644
index ace4b5b4c..000000000
Binary files a/build_key.enc and /dev/null differ
diff --git a/certbot-deploy b/certbot-deploy
deleted file mode 100755
index 7fc8282af..000000000
--- a/certbot-deploy
+++ /dev/null
@@ -1,21 +0,0 @@
-#!/bin/bash
-# Script to build and deploy certbot-website
-#
-SOURCE_REPO=https://github.com/certbot/website.git
-SOURCE_DOCS=/opt/certbot/
-COMPILED_DOCS=/certbot-compiled/
-#Update the source and documentation submodule, then build
-cd $SOURCE_DOCS && \
- git remote set-url origin $SOURCE_REPO && \
- git checkout . &&\
- git checkout master && \
- git pull origin master && \
- git submodule update && \
- cd $SOURCE_DOCS/_docs && \
- git checkout master && \
- git pull && \
- cd $SOURCE_DOCS && \
- gulp build --env production && \
- npm test && \
- rsync -a -O --delete --exclude=".*" _site/ $COMPILED_DOCS && \
- echo "Certbot site built"
diff --git a/contribute/index.md b/contribute/index.md
deleted file mode 100644
index 7b4501978..000000000
--- a/contribute/index.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-layout: page
-title: Contribute to Certbot
-class: contribute
----
-## Want to help Certbot?
-
-There are lots of ways to contribute to Certbot.
-
-For many of them, you’ll want to come chat with us on [the Certbot channel](https://opensource.eff.org/eff-open-source/channels/certbot) in [EFF’s Mattermost instance for its open source projects](https://opensource.eff.org/signup_user_complete/?id=6iqur37ucfrctfswrs14iscobw) as described below.
-
-You can get involved with several of EFF's software projects such as Certbot at the [EFF Open Source Contributor Chat Platform](https://opensource.eff.org/signup_user_complete/?id=6iqur37ucfrctfswrs14iscobw).
-
-
-
-
-Note: By signing up for the EFF Open Source Contributor Chat Platform, you consent to share your personal information with the Electronic Frontier Foundation, which is the operator and data controller for this platform. The channels will be available both to EFF, and to other users of EFFOSCCP, who may use or disclose information in these channels outside of EFFOSCCP. EFF will use your information, according to the Privacy Policy, to further the mission of EFF, including hosting and moderating the discussions on this platform.
-
-
-
-Use of EFFOSCCP is subject to the EFF Code of Conduct. When investigating an alleged Code of Conduct violation, EFF may review discussion channels or direct messages.
-
-
-
-Below are the main ways ways we’d appreciate help.
-
-{% include contrib/main_list.html %}
-
-## Want to learn more about what makes Certbot tick?
-Aside from the Certbot [Get Help](/help) page, we have a few resources available for developers to better understand how Certbot works.
-
-{% include contrib/code_list.html %}
diff --git a/docker-compose.yml b/docker-compose.yml
deleted file mode 100644
index 2bc6f333c..000000000
--- a/docker-compose.yml
+++ /dev/null
@@ -1,22 +0,0 @@
-version: '2.1'
-services:
- nginx:
- image: nginx
- ports:
- - '4000:4000'
- volumes:
- - assets:/usr/share/nginx/html:ro
- - ./nginx.conf:/etc/nginx/conf.d/default.conf
- links:
- - site
- site:
- build: .
- volumes:
- - .:/opt/certbot/
- - /opt/certbot/node_modules
- - /opt/certbot/instructions
- - /opt/certbot/_docs
- - assets:/opt/certbot/_site
-
-volumes:
- assets:
diff --git a/faq/index.html b/faq/index.html
deleted file mode 100644
index 1b742cff8..000000000
--- a/faq/index.html
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: page
-title: Frequently Asked Questions
-class: faq
----
-
-
- {% assign sorted_faq = site.faq_entries | sort: 'weight' %}
- {% for faq_entry in sorted_faq %}
-
-{{ term.content | markdownify }}
-{% endfor %}
diff --git a/gulpfile.js b/gulpfile.js
deleted file mode 100644
index cc13dd078..000000000
--- a/gulpfile.js
+++ /dev/null
@@ -1,29 +0,0 @@
-/*
- gulpfile.js
- ===========
- Rather than manage one giant configuration file responsible
- for creating multiple tasks, each task has been broken out into
- its own file in gulp/tasks. Any file in that folder gets automatically
- required by the loop in ./gulp/index.js (required below).
- To add a new task, simply add a new task file to gulp/tasks.
-*/
-
-/**
- * Build system for the Certbot website.
- * Copyright (C) 2016 Electronic Frontier Foundation
- *
- * This program is free software: you can redistribute it and/or modify
- * it under the terms of the GNU Affero General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- * GNU Affero General Public License for more details.
- *
- * You should have received a copy of the GNU Affero General Public License
- * along with this program. If not, see .
- */
-
-require('./_gulp');
\ No newline at end of file
diff --git a/help/index.md b/help/index.md
deleted file mode 100644
index 12b46658c..000000000
--- a/help/index.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-layout: page
-title: Get Help
-class: help
----
-## What can I find on this page?
-
-
-This page contains resources for learning about turning on {% include tooltip.html term-name="https" %} and the role Certbot plays in that process. We think they’re pretty helpful!
-
-
-If they don’t answer your questions, there’s a large community of people familiar with the project who might have the answers you’re looking for at [https://community.letsencrypt.org/](https://community.letsencrypt.org/).
-
-## Learn about Certbot and HTTPS
-{% include help/learn_more.html %}
-
-
Not finding what you need?
-{% include help/not_finding.html %}
diff --git a/hosting_providers/index.md b/hosting_providers/index.md
deleted file mode 100644
index 5aa6e5a81..000000000
--- a/hosting_providers/index.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: hosting_providers
-title: Does My Hosting Provider Offer HTTPS?
-class: hosting
----
-
-
-
This page is for users of {% include tooltip.html term-name="shared-hosting" text="shared hosting" %}.
-
-
- If you're not using the shared hosting product, or if your provider doesn't appear here, check out our instructions for using Certbot or get help. Note that your shared hosting is not the same as your {% include tooltip.html term-name="domain-registrar" text="domain registrar" %}.
-
-
Full HTTPS Support: Hosting providers that offer free Let’s Encrypt HTTPS certificates automatically for their shared hosting product. No need to do anything on your end if you use their service.
-
-
Partial HTTPS Support: Hosting providers that offer free Let’s Encrypt HTTPS certificates for their shared hosting product, but require configuration. You’ll need to follow a tutorial.
-
-
No HTTPS Support: Hosting providers that do not offer free HTTPS certificates for their shared hosting product. It may or may not be possible to use Certbot with other products that the provider offers, such as their VPS product.
-Certbot locally stores a variety of information provided by you, including internal housekeeping information created by the ACME protocol, the certificate information (domain name, public key, time, and specifically selected options), the IP address of the server, a user agent string, which is the operating system the server is running, plus which plugins you're using with Certbot. If you use the "manual" authenticator plugin on your own laptop, the IP address logged by the CA would be the one your ISP gave you, rather than that of the public server.
-
-In addition to the minimal information necessary to create certificates Certbot may also transmit additional information to facilitate reliable operation and debugging of ACME client and server software. By default this includes a detailed User Agent string, which may contain a variety of values, such as the operating system and version of the machine on which Certbot is run and the software version, the plugins that the user selected, the command with which you called Certbot, and certain flags on the command line or fields in config files. You can alter or remove this with the `--user-agent` flag. We may also ask you questions in the interface, and Certbot may also transmit the answers to the CA. Certbot also may transmit contact information such as an email address, if you choose to supply one, so that the CA can notify you about matters such as expiring, unrenewed certificates; security vulnerabilities; or important changes to its policies.
-
-Certbot never transmits the private key associated with your certificate to the CA, EFF, or anyone else.
-
-Certbot may also ask you to provide information to EFF, such as your contact information, bug reports or information to help with technology research, which generally will not include personally identifiable information.
-
-
Information Disclosure
-Certbot provides this information to the CA you select.
-
-Currently, Certbot works with Let’s Encrypt by default, which, as of April 2016, has three documents that discuss its privacy practices for this information; the [Let’s Encrypt Privacy Policy](https://letsencrypt.org/privacy/) section on Subscribers, it’s [Certification Practice Statement](https://letsencrypt.org/documents/ISRG-CPS-March-16-2016.pdf) (which, as of April 2016, just references back to the Privacy Policy), and the [Let’s Encrypt Subscriber Agreement](https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf) (Section 4.1).
-
-Let’s Encrypt also operates [Community Forums](https://community.letsencrypt.org/), using [Discourse](https://www.discourse.org/), where you may want to look to find answers to your questions about Certbot. These are subject to the [Let’s Encrypt](https://letsencrypt.org/privacy/) and [Discourse](http://www.discourse.org/hosted-forum-privacy-policy/) privacy policies.
-
-Let’s Encrypt may change these policies or providers from time to time. If you have questions about Let’s Encrypt’s privacy practices, please contact them directly at [security@letsencrypt.org](mailto:security@letsencrypt.org).
-
-The Certbot community can be contacted through the Freenode Project’s IRC service, chat.freenode.net, on the #certbot-devel channel. This IRC service is operated by Freenode, which does not publish a privacy policy.
-
-In addition, you may elect to provide information to EFF through Certbot, such as your contact information or bug reports. That information will be protected by the [EFF Technology Project Privacy Policy](https://www.eff.org/code/privacy/policy).
-
-
Changes to This Policy
-
-EFF's Certbot Privacy Policy may change from time to time. However, any revised privacy policy will be consistent with EFF's mission.
-
-*Updated on April 2nd, 2020 to change Freenode IRC channel.*
-
-*Updated on October 25th, 2018 to reflect changes to IRC services used.*
-
-*Updated on June 23rd, 2017 to add additional IRC services.*
-
-*Updated on June 7th, 2017 to clarify which values are collected in the User Agent string.*
-
-#### Previous Privacy Policies
-
-[October 25, 2018 - April 2, 2020](https://github.com/certbot/website/blob/eedd40a1a55b0ac6b27a96adfb23e707356b834a/privacy/index.md)
-
-[June 23, 2017 - October 25, 2018](https://github.com/certbot/website/blob/446a47c51fb74db05b8240ddb24174a36e71cc82/privacy/index.md)
-
-[June 7, 2017 - June 23, 2017](https://github.com/certbot/website/blob/21901280e8c6b1e64bbb595a97e8129e2c28b31b/privacy/index.md)
-
-[May 12, 2016 - June 7, 2017](https://github.com/certbot/website/blob/ec3b4a66316d42f6c40f2853686f5e665f8da64a/privacy/index.md)
diff --git a/push-build.sh b/push-build.sh
deleted file mode 100755
index f23138d3f..000000000
--- a/push-build.sh
+++ /dev/null
@@ -1,38 +0,0 @@
-#!/bin/bash -e
-
-BRANCH=$TRAVIS_BRANCH
-BUILD=$(git rev-parse --short HEAD)
-
-if [ $TRAVIS == "true" ]
-then
- openssl aes-256-cbc -K $encrypted_e5009b71da55_key -iv $encrypted_e5009b71da55_iv -in build_key.enc -out build_key -d
-fi
-chmod 600 build_key
-eval `ssh-agent -s`
-ssh-add build_key
-
-cd _site
-git init
-git config user.name "Travis CI"
-git config user.email "builds@travis-ci.com"
-git remote add upstream "git@github.com:certbot/website-builds.git"
-
-if git fetch upstream "$BRANCH"
-then
- # Manually set which branch HEAD points to to avoid changes to the
- # working tree caused by "git checkout".
- git symbolic-ref HEAD refs/heads/$BRANCH
- git reset upstream/$BRANCH
-else
- # Branch from master to more easily compare across branches.
- git fetch upstream master
- git branch $BRANCH upstream/master
- git symbolic-ref HEAD refs/heads/$BRANCH
- git reset
-fi
-
-touch .
-
-git add -A
-git commit -m "Build website at ${BUILD}"
-git push -q upstream $BRANCH
diff --git a/support/index.md b/support/index.md
deleted file mode 100644
index d05c8bf0a..000000000
--- a/support/index.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-layout: page
-title: Support
-class: support
----
-For most questions about Certbot, and all questions about Let’s Encrypt, it’s best to start with the [Let’s Encrypt Community Forums](https://community.letsencrypt.org/) (these are hosted by [Discourse](https://www.discourse.org/)).
-
-If you have a technical bug report, you can file it against the [Certbot github issue tracker](https://github.com/certbot/certbot/issues). Be sure to search for related issues first!