SSL Certificate Request Problem

[Hosted]

$ sudo tail -f /var/log/letsencrypt/letsencrypt.log
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/certbot/_internal/client.py”, line 496, in _get_order_and_authorizations
authzr = self.auth_handler.handle_authorizations(orderr, self.config, best_effort)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/certbot/_internal/auth_handler.py”, line 108, in handle_authorizations
self._poll_authorizations(authzrs, max_retries, max_time_mins, best_effort)
File “/usr/lib/python3/dist-packages/certbot/_internal/auth_handler.py”, line 212, in _poll_authorizations
raise errors.AuthorizationError(‘Some challenges have failed.’)
certbot.errors.AuthorizationError: Some challenges have failed.
2024-11-03 08:42:57,364:ERROR:certbot._internal.log:Some challenges have failed.

please anyone help me,
how can i go about it

[QPMReinhard]

it looks like a lookup problem for the domain.
lets encrypt can not find the ip for this host.

what says nslookup ?

[jimr1]

I was checking when you posted … the hostname does not resolve the OP needs to fix that

[Hosted]

But i can see that my domain has already propagate
When i run
nslookup domain >>>>>>>> it return my server-IP

[jimr1]

I’m guess you are trying to get a certificate for

boa.verify.secure-verifybnk.net 

that does not resolve
and also

verify.secure-verifybnk.net  

does not resolve but

secure-verifybnk.net  

does
where are you managing your DNS ?

[Hosted]

I registered the domain in

nicenic

And by way the domain should look like this

boa-verify.secure-verifybnk.net
Not
boa.verify.secure-verifybnk.net

[jimr1]

Ok typo … but google has marked your site as dangerous perhaps fix that then worry about ssl certificate when the domain is clean

[Hosted]

the domain is a clean domain dont know what google really want,
i just bought the domain today, and not site pages on it yet.

[jimr1]

Maybe it was used before something bad and google is unaware that there is a change in ownership and content, never having that problem I’m not sure on the best course of action. Is there any content on the site or just the default virtualmin page ?

[Hosted]

just default virtualmin page

[shoulders]

Just because the IP/domain has propagated for you it does not mean that the lets encrypt servers will see that change at the same time as you. I made this mistake a few times.

Also TTL (time to live) can play a part.