# Installing letsencrypt **URL:** \ **Category:** Server\ **Created:** [December 29, 2015, 10:20am UTC](https://community.letsencrypt.org/t/installing-letsencrypt/7896 "2015-12-29T10:20:10Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\ **Post date:** [December 29, 2015, 11:08am UTC](https://community.letsencrypt.org/t/installing-letsencrypt/7896/5 "2015-12-29T11:08:19Z")
> [@Hendrik](#): > > It's weird, because i checked: > > [INTRODUCTION — letsencrypt latest documentation](https://letsencrypt.readthedocs.org/en/latest/intro.html) > > And i checked the "System Requirements" and there they are saying nothing about EPEL. The documentation is indeed a bit redundant here, and not really in sync with the [more detailed installation guide](https://letsencrypt.readthedocs.org/en/latest/using.html#installation) where this is mentioned. > [@Hendrik](#): > > This will not be a problem later on? And the Python core team is saying that i have to update the Python version (HOW?), but letsencrypt is saying that 2.6 is okay in their "System Requirements". It's fine, CentOS maintains older versions of packages they ship as long as the CentOS version is still supported. I'm not familiar enough with CentOS to say whether upgrading python is a good idea (it's generally a bit of a hassle on debian/ubuntu), but as long as you manage to get your certificates, there shouldn't be any issues in the future (unless letsencrypt drops 2.6 support completely). > [@Hendrik](#): > > And one more question...the mailaddress is from a different domain then the certificate is on, but that's no problem i think, right? That's okay, the email will only be used for renewal reminders (and in the future possibly account recovery if you lose the private key). --- _[View the full topic](https://community.letsencrypt.org/t/installing-letsencrypt/7896)._