Setting up certificate with Filemaker Server

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: landfieldstudio.com

I ran this command: sudo sh ./GetSSL.sh

It produced this output: `Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for landfieldstudio.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: landfieldstudio.com
Type: dns
Detail: No valid IP addresses found for landfieldstudio.com

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/landfieldstudio.com/fullchain.pem: No such file or directory
cp: /etc/letsencrypt/live/landfieldstudio.com/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)`

My web server is (include version): Filemaker Server 19.4.2.204

The operating system my web server runs on is (include version): Mac OS Monterey 12.0.1

My hosting provider, if applicable, is: Me (the server is hosted on my own machine. The Domain registrar is GoDaddy).

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 1.22.0

1 Like
2

Welcome to the community @TimeTravlr

Your DNS must point to a public IP but it is set to a private address starting with 192.168...

Maybe look in your router settings for this or go to this website which returns your public IP when you visit

curl ifconfig.co

Also see:

3 Likes
3

Ok I've set up my domain to work with a DDNS service, no-ip.com

I'm still getting an error when I run getSSL.sh

See below:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Requesting a certificate for landfieldstudio.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:

Domain: landfieldstudio.com

Type: connection

Detail: Fetching http://landfieldstudio.com/.well-known/acme-challenge/asRpvge1_Eupc0tlrh8IuxmG-dzqx3pLNrrPtWpqufg: Timeout during connect (likely firewall problem)

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/landfieldstudio.com/fullchain.pem: No such file or directory

cp: /etc/letsencrypt/live/landfieldstudio.com/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

4

You need a functional HTTP site before it can be secured (via HTTP authentication).

2 Likes
5

Agree with what Rudy said ... your port 80 is not working.

But, your Apache responds on port 443 so make sure your port 80 is open like 443 and that Apache has a VirtualHost listening on port 80.

Let's Debug test is better but still not working

2 Likes
6

Ok. I think I've got it working. I set up port forwarding for port 80 and now when I go to my domain through a secure connection https://landfieldstudio.com seems to work. Is there anything I should do to doublecheck that I have certbot set up properly, or is set up to renew the certificate on schedule? Thanks for your help!

1 Like
7

Start with:
certbot certificates
crontab -l

1 Like
8

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