Problem with installation

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: alteslife.tech

I ran this command: certbot --nginx

It produced this output: Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): http://boutique.alteslife.tech php8.0.17

The operating system my web server runs on is (include version): Ubuntu 20.04

My hosting provider, if applicable, is: pulseheberg ( my vps )

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): no

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

logs say :
2022-05-31 22:34:57,246:DEBUG:urllib3.connectionpool:http://localhost:None "GET /v2/connections?snap=certbot&interface=content HTTP/1.1" 200 97
2022-05-31 22:34:57,688:DEBUG:certbot._internal.main:certbot version: 1.27.0
2022-05-31 22:34:57,688:DEBUG:certbot._internal.main:Location of certbot entry point: /snap/certbot/2035/bin/certbot
2022-05-31 22:34:57,688:DEBUG:certbot._internal.main:Arguments: ['--nginx', '--preconfigured-renewal']
2022-05-31 22:34:57,688:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#apache,PluginEntryPoint#manual,PluginEntryPoint#nginx,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2022-05-31 22:34:57,705:DEBUG:certbot._internal.log:Root logging level set at 30
2022-05-31 22:34:57,706:DEBUG:certbot._internal.plugins.selection:Requested authenticator nginx and installer nginx
2022-05-31 22:34:57,839:DEBUG:certbot._internal.plugins.selection:Single candidate plugin: * nginx
Description: Nginx Web Server plugin
Interfaces: Installer, Authenticator, Plugin
Entry point: nginx = certbot_nginx._internal.configurator:NginxConfigurator
Initialized: <certbot_nginx._internal.configurator.NginxConfigurator object at 0x7f2e47ceab50>
Prep: True
2022-05-31 22:34:57,840:DEBUG:certbot._internal.plugins.selection:Selected authenticator <certbot_nginx._internal.configurator.NginxConfigurator object at 0x7f2e47ceab50> and installer <certbot_nginx._internal.configurator.NginxConfigur>
2022-05-31 22:34:57,840:INFO:certbot._internal.plugins.selection:Plugins selected: Authenticator nginx, Installer nginx
2022-05-31 22:34:57,847:DEBUG:certbot._internal.main:Picked account: <Account(RegistrationResource(body=Registration(key=None, contact=(), agreement=None, status=None, terms_of_service_agreed=None, only_return_existing=None, external_ac>
2022-05-31 22:34:57,848:DEBUG:acme.client:Sending GET request to https://acme-v02.api.letsencrypt.org/directory.
2022-05-31 22:34:57,849:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org:443
2022-05-31 22:34:58,255:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "GET /directory HTTP/1.1" 200 658
2022-05-31 22:34:58,256:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Tue, 31 May 2022 20:34:58 GMT
Content-Type: application/json
Content-Length: 658
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800

{
"IFprguOKxf4": "Adding random entries to the directory",
"keyChange": "https://acme-v02.api.letsencrypt.org/acme/key-change",
"meta": {
"caaIdentities": [
"letsencrypt.org"
],
"termsOfService": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf",
"website": "https://letsencrypt.org"
},
"newAccount": "https://acme-v02.api.letsencrypt.org/acme/new-acct",
"newNonce": "https://acme-v02.api.letsencrypt.org/acme/new-nonce",
"newOrder": "https://acme-v02.api.letsencrypt.org/acme/new-order",
"revokeCert": "https://acme-v02.api.letsencrypt.org/acme/revoke-cert"
}
2022-05-31 22:34:58,260:DEBUG:certbot.util:Not suggesting name "flj"
Traceback (most recent call last):
File "/snap/certbot/2035/lib/python3.8/site-packages/certbot/util.py", line 311, in get_filtered_names
filtered_names.add(enforce_le_validity(name))
File "/snap/certbot/2035/lib/python3.8/site-packages/certbot/util.py", line 503, in enforce_le_validity
raise errors.ConfigurationError(
certbot.errors.ConfigurationError: flj needs at least two labels
2022-05-31 22:34:58,261:DEBUG:certbot.util:Not suggesting name "prometheus"
Traceback (most recent call last):
File "/snap/certbot/2035/lib/python3.8/site-packages/certbot/util.py", line 311, in get_filtered_names
filtered_names.add(enforce_le_validity(name))
File "/snap/certbot/2035/lib/python3.8/site-packages/certbot/util.py", line 503, in enforce_le_validity
raise errors.ConfigurationError(
certbot.errors.ConfigurationError: prometheus needs at least two labels

Hi @Nemesius, and welcome to the LE community forum :slight_smile:

Can you try it with --webroot -w /path/to/site/root ?

2 Likes

Hi thank you but it's say that :

1 Like

Yes, go ahead and add certonly too.
You should provide the domain name(s).
And ensure the webroot path matches the DocumentRoot path for each name.

Example:
certbot certonly --webroot -w /path/1 -d domain.1 -w /path/2 -d domain.2 ...

1 Like

Here's a link to the certbot --webroot documentation:
User Guide — Certbot 1.27.0 documentation (eff-certbot.readthedocs.io)

1 Like