Invalid response from http://logbook.austinrowing.org/.well-known/acme-challenge ... 404

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: logbook.austinrowing.org

I ran this command: sudo ./GetSSL.sh

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for logbook.austinrowing.org
Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:

Domain: logbook.austinrowing.org
Type: unauthorized
Detail: 107.209.253.69: Invalid response from http://logbook.austinrowing.org/.well-known/acme-challenge/J-Ukd9MS3_OADG_5Z3P_kZa3HeIHjhXcHKcPHi5-CeQ: 404
Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded 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.
cp: /etc/letsencrypt/live/logbook.austinrowing.org/fullchain.pem: No such file or directory
cp: /etc/letsencrypt/live/logbook.austinrowing.org/privkey.pem: No such file or directory
chmod: /Library/FileMaker Server/CStore/privkey.pem: No such file or directory
mv: rename /Library/FileMaker Server/CStore/serverKey.pem to /Library/FileMaker Server/CStore/serverKey-old.pem: No such file or directory

fmsadmin: really delete certificate? (y, n) (Warning: server needs to be restarted) n
Error: 10502 (Host unreachable)

My web server is (include version): FileMaker Server 20.1.1.38

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

My hosting provider, if applicable, is: NA

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

Where did you get that getSSL.sh script from?

Because we recently helped someone with a problem with that script. And, there are different repositories one of which has been abandoned and won't work. See a description of the working version

4 Likes

The script I used came from Let's Encrypt SSL Certificates for FileMaker Server for Mac - Blue Feather.

OK. Not the same problem - sorry.

I'm not really sure what to advise. I see your domain has an Apache server responding to HTTP requests but there is no mention of Apache in the Blue Feather page you linked.

Usually with Apache you just make sure Certbot uses the same folder for the --webroot-path (-w folder) as the DocumentRoot in Apache for that domain.

But, I don't know how Apache interacts with FileMaker.

Are you sure you updated the getssl.sh script SERVER_PATH variable according to the instructions?

You might also try the below contact which I saw in the getssl.sh script

# Need help? We can set this up to run on your server for you! Send an email to 
# contact@bluefeathergroup.com or give a call at (770) 765-6258
5 Likes

Yes, I confirmed that it's the standard location, so it didn't need updating.

Now I'll contact Blue Feather Group.

Thanks, MikeMcQ.

—Ham

4 Likes

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