# Aborting bootstrap? **URL:** \ **Category:** Help\ **Created:** [January 20, 2020, 1:03am UTC](https://community.letsencrypt.org/t/aborting-bootstrap/111044 "2020-01-20T01:03:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![bgroper](https://avatars.discourse-cdn.com/v4/letter/b/b77776/32.png) [@bgroper](https://community.letsencrypt.org/u/bgroper)\ **Post date:** [January 20, 2020, 1:03am UTC](https://community.letsencrypt.org/t/aborting-bootstrap/111044/1 "2020-01-20T01:03:24Z")
**I ran this command as root on patched and updated CentOS 6.10 :** cd /root/letsencrypt/ && ./letsencrypt-auto renew **It produced this output:** Upgrading certbot-auto 1.0.0 to 1.1.0… Replacing certbot-auto… Bootstrapping dependencies for Legacy RedHat-based OSes that will use Python3… (you can skip this with --no-bootstrap) yum is hashed (/usr/bin/yum) To use Certbot on this operating system, packages from the SCL repository need to be installed. Enabling the SCL repository in 3 seconds… (Press Ctrl-C to cancel)e[0KEnabling the SCL repository in 2 seconds… (Press Ctrl-C to cancel)e[0KEnabling the SCL repository in 1 second… (Press Ctrl-C to cancel) Loaded plugins: fastestmirror Setting up Install Process Loading mirror speeds from cached hostfile - base: mirror.ventraip.net.au - epel: [mirror.realcompute.io](http://mirror.realcompute.io) - extras: mirror.ventraip.net.au - updates: [mirror.colocity.com](http://mirror.colocity.com) No package available. Package 10:centos-release-scl-7-4.el6.centos.noarch already installed and latest version Nothing to do No supported Python package available to install. Aborting bootstrap! Any tips or clues for how to fix ? Current cert expires in a few weeks. ---
**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\ **Post date:** [January 20, 2020, 2:02am UTC](https://community.letsencrypt.org/t/aborting-bootstrap/111044/2 "2020-01-20T02:02:12Z")
I think it’d be easier to use different acme client that has less dependency, like [acme.sh](https://github.com/Neilpang/acme.sh) ---
**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\ **Post date:** [January 20, 2020, 2:24am UTC](https://community.letsencrypt.org/t/aborting-bootstrap/111044/3 "2020-01-20T02:24:21Z")
Still, certbot-auto should work. The [release notes](https://community.letsencrypt.org/t/certbot-1-1-0-release/110599) said that “certbot-auto no longer supports architectures other than x86\_64 on RHEL 6 based systems”, but it shouldn’t _stop_ working. ---
**Author:** ![bruncsak](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruncsak/32/18414_2.png) [@bruncsak](https://community.letsencrypt.org/u/bruncsak)\ **Post date:** [January 20, 2020, 8:52am UTC](https://community.letsencrypt.org/t/aborting-bootstrap/111044/4 "2020-01-20T08:52:54Z")
What is the output of the `uname -i` command? If the output is `i386`, than I suggest to use a different tool to get certificate. (I guess, that architecture is not supported any more by the latest python language.) List of software to get a certificate: [https://letsencrypt.org/docs/client-options/](https://letsencrypt.org/docs/client-options/) ---
**Author:** ![bmw](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmw/32/7797_2.png) [@bmw](https://community.letsencrypt.org/u/bmw)\ **Post date:** [January 21, 2020, 6:17pm UTC](https://community.letsencrypt.org/t/aborting-bootstrap/111044/5 "2020-01-21T18:17:34Z")
@bgroper, on x86-64 RHEL 6 based systems, certbot-auto is trying to enable the SCL repository so it can install a version of Python that is still supported by the Python maintainers. Usually this can be done by installing the `centos-release-scl` package, but this doesn’t appear to be working on your system. Do you know why? Have you manually disabled SCL? You can see which repositories are enabled by running a command like `sudo yum repolist`. You may be able to fix the problem by uninstalling and reinstalling the `centos-release-scl` package and its dependency through commands like: ```auto sudo yum remove centos-release-scl-rh centos-release-scl sudo yum install centos-release-scl ``` If none of this helps you resolve the problem, what is the output of `sudo yum repolist` and `sudo tail -n +1 /etc/yum.repos.d/*SCL*` ---
**Author:** ![bgroper](https://avatars.discourse-cdn.com/v4/letter/b/b77776/32.png) [@bgroper](https://community.letsencrypt.org/u/bgroper)\ **Post date:** [January 28, 2020, 4:20am UTC](https://community.letsencrypt.org/t/aborting-bootstrap/111044/6 "2020-01-28T04:20:53Z")
Thanks to bmw for good instructions. Seems to be fixed now. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [February 27, 2020, 4:20am UTC](https://community.letsencrypt.org/t/aborting-bootstrap/111044/7 "2020-02-27T04:20:53Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.