Certbot - some challenges failed

Help
1

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: mollywonka.shop

I ran this command:

sudo certbot --apache -d mollywonka.shop

It produced this output:

Requesting a certificate for mollywonka.shop

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: mollywonka.shop
Type: unauthorized
Detail: 2a02:4780:b:1368:0:1edc:a373:2: Invalid response from http://mollywonka.shop/.well-known/acme-challenge/fF6NdC61cXRlLDGVbgg7pF8nogRmMi2vx0XOrGtVtDs: 404

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

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

Apache2

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

Ubuntu 22.04

My hosting provider, if applicable, is:

hostinger

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

nextcloud?

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

certbot 1.21.0

I have honestly spent at least a week trying to follow all the guidelines but i am tied in a knot right now.... i am trying to set up a nextcloud server that is accessible from outside my network but i can't get through the certbot authentication stage ... my domain is registered with hostinger ...

this is my first forray into hosting a server and while everything works perfetly on my local newtork, i would like my server to be accessible remotely .... i think i am at the point where i could do with some hand holding...

thank you

2 Likes
2

That domain is handled by a LiteSpeed server. The Certbot --apache plugin only works with Apache servers.

Request to: mollywonka.shop/2a02:4780:b:1368:0:1edc:a373:2, Result: [Address=2a02:4780:b:1368:0:1edc:a373:2,Address Type=IPv6,Server=LiteSpeed

Your IPv4 and IPv6 addresses are at least pointing to the same place so that's good.

For LiteSpeed you could use the --webroot method.

But, if you want Apache to be handling your requests you may need to consult with Hostinger. They should be able to help you configure your system properly. It looks to me like your DNS records are pointing to a Hostinger server (not your local network).

4 Likes
3

thanks for that

it sort of confirms what i thought - the DNS records are pointed at hostinger - i asssumed they should be

i already contacted hostinger and they told me the nemaeservers should be pointed at nextcloud but that is where i get stuck because i don't know what changes to make to the domain dns in the hostinger panel .... hostinger support told me to speak to nextcloud ... nextcloud told me to speak with letsencrypt admin and so on ....

the support lady at hostinger just sent me some random guides - most of which i have been through already

i am confused by the options in the panel... do i need to add an A record or AAAA etc ...

the hostinger panel gives me this option but i get no further

sever1
sever11166×656 62.3 KB

sorry to sound like an eedjut - i sort of am

1 Like
4

Your dns should point to the public ip address of your Apache server. I don't know exactly how to do that in hostinger. The end result is that you should have an A record for your ipv4 address if you have one. And you should have an AAAA record for your IPV6 address if you have one of those. So first find out what your IP addresses are and then ask hostinger how to use their panel to set that up.

4 Likes
5

thanks very much for your help

i will try contacting hostinger again

3 Likes
7

image
Is your domain "parked"?

3 Likes
8

yes - the domain says it is parked and i don't know how to unpark it

:frowning:

9

How to Park a Domain | Hostinger Help Center

3 Likes
10

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