# Fail to detect Amazon Linux 2. (Certbot) **URL:** \ **Category:** Client dev\ **Created:** [October 16, 2020, 9:06am UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140 "2020-10-16T09:06:51Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![itoken417](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/itoken417/32/43741_2.png) [@itoken417](https://community.letsencrypt.org/u/itoken417)\ **Post date:** [October 16, 2020, 9:06am UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140/1 "2020-10-16T09:06:51Z")
String 'Amazon Linux' is not appeared in '/etc/issue' on Amazon Linux 2. Correctly, it is written in'/ etc / system-release', so please fix it. ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [October 16, 2020, 9:30am UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140/2 "2020-10-16T09:30:29Z")
The best chance to get Certbot working on Amazon Linux 2 is to install the rpm from EPEL as described here: [https://aws.amazon.com/blogs/compute/extending-amazon-linux-2-with-epel-and-lets-encrypt/](https://aws.amazon.com/blogs/compute/extending-amazon-linux-2-with-epel-and-lets-encrypt/). `certbot-auto`, which itself is being deprecated, has never worked well with Amazon Linux 2 (for reasons unrelated to how it detects distros). From what I can tell the EPEL package works well and is relatively up to date, but if it's not suitable for you, there are some [other client options](https://letsencrypt.org/docs/client-options/). ---
**Author:** ![itoken417](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/itoken417/32/43741_2.png) [@itoken417](https://community.letsencrypt.org/u/itoken417)\ **Post date:** [October 16, 2020, 9:51am UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140/3 "2020-10-16T09:51:39Z")
EPEL certbot package is version 1.7.0 . Last release certbot package is version 1.9.0 . The following message came to appear after certbot auto update to version 1.9.0. ```auto Your system is not supported by certbot-auto anymore. Certbot will no longer receive updates. Please visit https://certbot.eff.org/ to check for other alternatives. ``` It seems to be considered a deprecated OS Amazon Linux 2 by the DEPRECATED\_OS flag. Changed by [https://github.com/certbot/certbot/pull/8324](https://github.com/certbot/certbot/pull/8324) ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [October 16, 2020, 11:52am UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140/4 "2020-10-16T11:52:23Z")
Correct, the certbot-auto script is being deprecated. ---
**Author:** ![itoken417](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/itoken417/32/43741_2.png) [@itoken417](https://community.letsencrypt.org/u/itoken417)\ **Post date:** [October 16, 2020, 3:15pm UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140/5 "2020-10-16T15:15:07Z")
I found that certbot-auto is deprecated. But when the version goes up to 1.9.0 on EPEL, I think it will be the same problem if I don't fix it, is that okay? I want to continue using it on Amazon Linax 2. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [October 16, 2020, 3:46pm UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140/6 "2020-10-16T15:46:24Z")
> [@itoken417](#): > > I found that certbot-auto is deprecated. > But when the version goes up to 1.9.0 on EPEL, I think it will be the same problem if I don't fix it, is that okay? I don't think you understand what the `certbot-auto` script is (emphasis on the **`-auto`** part!): it's a wrapper script around the Python program called certbot ( **without** `-auto` in the name). The script is a method to install the program within a Python virtual environment ("venv") if you don't have an alternate method to install certbot. If you **do** have a different/better method to install certbot, such as the rpm package through EPEL, you won't need the script at all. Because it's the _script_ which is being deprecated and certainly _not_ the program certbot, you can keep using the certbot version through EPEL. It's the task of the EPEL maintainers to bump the version of the certbot package to later releases, so it can indeed be possible that EPEL has an older version than the script (which always downloads the latest version through pip which is very up to date). However, version 1.7.0 is relatively new, so not really a reason to use the certbot-auto **wrapper script**. Just use the certbot **program** through EPEL. ---
**Author:** ![itoken417](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/itoken417/32/43741_2.png) [@itoken417](https://community.letsencrypt.org/u/itoken417)\ **Post date:** [October 17, 2020, 12:52am UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140/7 "2020-10-17T00:52:12Z")
Thank you for your explanation. When EPEL rpm is created, certbot-auto is not included. When I got the message, I was wondering if Amazon Linux 2 would be a deprecated OS. After all, I lacked my knowledge, but if someone who has the same feelings uses EPEL's certbot, I'm relieved. It may not be necessary, but in the case of Amazon Linux2, I'd be happy if the message "Reinstall using EPEL" appears in certbot-auto. thank you everyone. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [November 16, 2020, 12:52am UTC](https://community.letsencrypt.org/t/fail-to-detect-amazon-linux-2-certbot/136140/8 "2020-11-16T00:52:25Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.