# type certbot
certbot is hashed (/usr/bin/certbot)
To find out where certbot is installed to. Or command -v certbot if you prefer.
Then run head /usr/bin/certbot and note what version of Python it's using:
In my case, it was using Python 3.
I noticed from my pip output it was trying to install a Python 2.7 package:
# pip ...
Now (July 2018), you should be able to use either
pip install certbot-dns-digitalocean
git clone https://github.com/certbot/certbot.git
python setup.py install
You may need sudo privileges for either.
After installing you may not be able to see the plugin with certbot plugins, but you should be able to certbot ...
You have to use Docker to use dns plugins. From DNS Plugins:
These plugins are still in the process of being packaged by many distributions and cannot currently be installed with certbot-auto. If, however, you are comfortable installing the certificates yourself, you can run these plugins with Docker.
You just can not because from Let's Encrypt FAQ:
What IP addresses does Let’s Encrypt use to validate my web server?
We don’t publish a list of IP addresses we use to validate, because
they may change at any time. In the future we may validate from
multiple IP addresses at once.
You will need a reverse proxy (usually a WAF), routing /.well-...
The way you install certbot plugins depends on how you installed certbot itself. If you installed certbot using some package manager (apt, rpm, brew...), then you should look for compatible certbot plugins in that package manager's repository.
Let's Encrypt also support an alternative installation method: the certbot-auto wrapper. This wrapper creates a ...
Thanks for linking your question. Here's the github thread for reference: https://github.com/geerlingguy/ansible-role-certbot/issues/87
There are many different ways to get certs from a CA. certbot (what this repo uses) is just one of the ways which uses letsencrypt as a certificate authority. acme_certificate is more generic and if you can't use ...
Based on @13nilux' answer the following code has been created:
- name: Check whether port 80 is available
When port 80 is listening the run will fail if for example nginx is listening:
TASK [role_under_test : Check whether port 80 is available] ********************
fatal: [localhost]: FAILED! =&...