But i have error in this line: $ sudo ./certbot-auto --debug -v --server https://acme-v01.api.letsencrypt.org/directory certonly -d payworld.com.br -d www.payworld.com.br
Error:
Sorry, I don’t know how to bootstrap Certbot on your operating system!
You will need to install OS dependencies, configure virtualenv, and run pip install manually.
But I already installed pip and virtualenv.
Version
pip 10.0.1
virtualenv 16.0.0
python 2.7.14
I looked for the solution in previous questions here of the community, but I could not solve.
Could you please fill in the form below so we could have more information?
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Certbot currently doesn't have any fully-supported installation method on Amazon Linux (in particular certbot-auto is not designed for use on this operating system), although I've heard that the situation has been getting better for many people. You could look at this previous thread:
There might be an Amazon-provided version of Certbot in Amazon Linux 2 or a different installation method might work.
The information that you saw about pip is not about having pip installed, but about using pip interactively to install Certbot Python packages from the PyPi repositories.
As suggested in the other thread, there are also many other Let's Encrypt clients that have fewer dependencies and so you might have more success with one of those.
How did you get from the “Sorry, I don’t know how to bootstrap Certbot on your operating system!” error to a specific certificate authentication error, such as you now have?
which describes how to install from EPEL. (However, if you already got the “Unable to find a virtual host” error on the new server, then you already have a working copy of Certbot there.)
Edit: or @bmw says you can try the CentOS instructions on our own site
Cada vez em que você usar sudo ./certbot-auto, está tentando de novo com a versão auto-atualizada, então as tentativas de instalar outros pacotes de acordo com dicas minhas ou de terceiros não deveriam ter influência nenhuma nos resultados de sudo ./certbot-auto.
Os pacotes de EPEL que talvez já instalou ou instalará com yum se usariam como sudo certbot, não sudo ./certbot-auto.
Certbot should already have created a virtual host for you—in that file /etc/httpd/conf/httpd-le-ssl.conf. However, possibly that file isn't included by default? Certbot assumed that every configuration file in /etc/httpd/conf would be included automatically.
Do you have a _default_ virtual host, by any chance?
Sempre agradeço quaisquer oportunidades de falar a língua portuguesa, que já se tornou a minha língua estrangeira preferida.
Também me parece que surgiu o costume nesse fórum do uso da língua da pessoa pedindo ajuda caso isso facilitar a comunicação e alguém saber aquela língua o puder se comunicar nela com a ajuda de tradução automática. Assim até onde eu sei não é obrigatório o uso de inglês aqui.
Mas se preferir continuar em inglês, tudo bem!
Não sei porque não deu certo logo após a emissão do certificado, porque o Certbot disse que o instalou no seu Apache.
Então, eis dois passos possíveis para esclarecer as minhas dúvidas anteriores:
(1) Verificar se todos os arquivos dentro de /etc/httpd/conf se incluem automaticamente na configuração Apache.
(2) Tentar encontrar o virtualhost _default_ com
grep -r _default_ /etc/httpd
... Também deve existir um jeito de exibir a configuração atual inteira, tal como
apachectl -t -D DUMP_VHOSTS
Isso é um pouco diferente em vários sistemas operacionais.
