SSL not generated

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. https://crt.sh/?q=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: http://34.106.29.112/

I ran this command: ```
./certbot-auto certonly --webroot -w /var/www/html/ -d 34.106.29.112 -d 34.106.29.112


It produced this output:
Setting up libitm1:amd64 (6.3.0-18+deb9u1) ...
Setting up cpp (4:6.3.0-4) ...
Setting up python-pip-whl (9.0.1-2+deb9u1) ...
Setting up libgcc-6-dev:amd64 (6.3.0-18+deb9u1) ...
Setting up libssl-dev:amd64 (1.1.1g-1+0~20200421.17+debian9~1.gbpf6902f) ...
Setting up libaugeas0 (1.8.0-1+deb9u1) ...
Setting up gcc-6 (6.3.0-18+deb9u1) ...
Setting up python3-virtualenv (15.1.0+ds-1) ...
Setting up python-virtualenv (15.1.0+ds-1) ...
Setting up libexpat1-dev:amd64 (2.2.0-2+deb9u3) ...
Setting up libpython2.7-dev:amd64 (2.7.13-2+deb9u3) ...
Setting up virtualenv (15.1.0+ds-1) ...
Setting up python2.7-dev (2.7.13-2+deb9u3) ...
Setting up libpython-dev:amd64 (2.7.13-2) ...
Setting up python-dev (2.7.13-2) ...
Setting up gcc (4:6.3.0-4) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for ca-certificates (20200601~deb9u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
./certbot-auto has insecure permissions!
To learn how to fix them, visit https://community.letsencrypt.org/t/certbot-auto-deployment-best-practices/91979/
Creating virtual environment...
Installing Python packages...
Installation succeeded.
/var/ww/html/ does not exist or is not a directory

My web server is (include version):

The operating system my web server runs on is (include version):
Debian (9.12)

My hosting provider, if applicable, is: google cloud

I can login to a root shell on my machine (yes or no, or I don't know):yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): yes

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot):

Hi,

I think currently let’s Encrypt can’t issue certificates to non-domains.

The issue you are currently facing is: you asked certbot to generate a certificate using webroot, which means it will attempt to place a verification file under the directory. But, the directory didn’t exist.

4 Likes

Hi @mmyy

a domain name abc.com is required, not an ip address.

There exist certificates with ip addresses (see https://1.1.1.1/ ), but Letsencrypt doesn’t allow to create such certificates.

There are some free domain providers (with some limitations) you can use. Then create an A record Yourdomain -> yourIp.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.