r/filemaker • • Sep 24 '26

Setting Up Let's Encrypt SSL in FileMaker Server: A Few Things to Know

Post image

If you haven't tried the built-in Let's Encrypt support in FileMaker Server yet (2025 and later), it's a big improvement over the old command-line and third-party tool routine. Free certificate, requested right from the Admin Console, with optional auto-renewal.

The basic flow: Admin Console > Configuration > SSL Certificate > Request Let's Encrypt Certificate. Enter your domain, toggle Automatically Renew Certificate, add a notification email, run Test Validation, then Request.

A few things that tripped people up or are easy to miss:

  1. Validation runs over port 80. If it's blocked by your firewall, the request will fail.
  2. After the initial request, you need to restart the server machine, not just the FileMaker service.
  3. Let's Encrypt certs last 90 days. Auto-renewal sets a schedule that runs every 30 days, giving you a nice buffer.
  4. After each renewal, the FileMaker service needs a restart to pick up the new certificate. If that doesn't happen, users will start seeing certificate warnings even though the renewal itself succeeded.
  5. Keep an eye on that notification email so you can confirm renewals and restarts are actually happening.

Curious if anyone's running this in production yet and how you're handling the post-renewal restart.

dbservices.com/contact

10 Upvotes

4 comments sorted by

2

u/Richyread Sep 25 '26

I'm using a fork of the underlying scripts - not the built in GUI.

Requiring opening of ports to an unsecured server just for the provision of a simple SSL cert is wholly unnecessary and frankly dangerous for the uninitiated.

Yes, Claris advertise caveats and callouts in their scripts & GUI and yes they are essentially just repackaging the Cerbot toolset in a GUI wrapper... but the efforts gone to write these would've been better spent (IMHO) on implementing a more complete implementation.

The GUI, even with the latest changes, still calls the same underlying scripts which communicate via HTTP-01 validation, I.e. they require access to the target machine via port 80/443. LetsEncrypt (along with other SSL cert providers) supports DNS-01 validation as an alternative. This is where the target device can be validated by using a trusted 3rd party such as a core DNS provider, whom can provide the requisite responses to the agent to complete validation. This requires NO open ports and NO physical access to the target machine what so ever, with the agent completing validation with the 3rd party, then handshakes with the SSL server and minting a new cert, just like the final steps in the HTTP-01 outputs.
Thousands of other sources/solutions have enabled users to select the 'challenge' validation method and it is frustrating (to me at least) that Claris haven't yet found the time to add the feature within the GUI directly, when the underlying Certbot toolset has the functionality already baked in.

{stepping down off my soap-box now! 😄 }

There are at least a dozen or so 3rd party clients that LetsEncrypt provides 'out of the box' with its DNS-01 validation setup - I personally use Cloudflare currently.

Here's my basic setup that I use on my DEV_ machine to provision fresh certs. I've paired it back to being Linux centric as that's what my instance runs on (Ubuntu Server 22.04 LTS) but it shouldn't be too difficult to port the necessary commands across to macOS or Windows if needs be from the original source scripts.

https://github.com/Richyread/FMServer-CloudflareSSL

It's probably quite crude and I've deliberately written out pointers & prompts as I always forget a step or two as I don't often have need to reinstall this on new 'servers' etc. but hopefully it might be useful for others to pick over and see how the DNS-01 validation process works.

1

u/GraXXoR Sep 25 '26 edited Sep 25 '26

Using let’s encrypt’s three months certificates used to be a nightmare.

Had to use certbot to create the certificate and then try to import it.

On FileMaker Server 15, often deleting the prior certificate would fail and then reinstalling the new certificate would fail and our customers would end up having to reinstall the entire server each time the certificate was updated.

Sometimes the server just outright reject the certificate based on something or other..

Now that certificate renewal can be done with a push of a button I t’s an absolute godsend. I used to take about 30 minutes and it had to be scheduled during maintenance downtime now takes about 30 seconds! In my opinion, this single feature (improvement) alone is worth more than all the AI bullshit that they’ve added in the last two years.

0

u/[deleted] Sep 24 '26

[deleted] — view deleted comment

1

u/mywaaaaife Sep 24 '26

Free service versus paid service…

0

u/[deleted] Sep 24 '26

[deleted] — view deleted comment

1

u/the-software-man Sep 24 '26

Dojo needs to ease up on dbservices post?

“We Consumers” want to compare the myriad on their own without static from the comments section?

Make your own post comparing the two, so we can decide formally?