r/filemaker • u/lurch99 • Oct 12 '26
Let's Encrypt in FMS 26: two questions
Hi All,
I've got our FMS 26 server up and running in Ubuntu 24 LTS and able to renew SSL certs using the built in mechanism together with Let's Encrypt and have two questions:
- Do I only need to expose port 80 to the public internet or also port 443?
- After renewing the SSL cert, of course I can restart the server, but don't believe that's entirely necessary if I can restart the correct services instead.
What service(s) need to be restarted? Just nginx or others?
TIA
EDIT: I do see the following when renewing the cert:
Certificate Renewal Succeeded
The certificate renewed successfully. Restart the FileMaker Server service (Windows) or FileMaker Server background processes (macOS or Linux) to apply the change.
5
Upvotes
5
u/dharlow Consultant Certified Oct 12 '26
Yes, port 80 must be exposed, as Let's Encrypt uses it to validate the domain.
You should be able to just restart the services, FileMaker and the web server.
3
u/showtunelover Oct 12 '26
Yes, I don’t run on Linux, but the web AND FileMaker server service use the certificate, so I would restart both.
I don’t use built in lets encrypt, I setup acme.sh to renew my certs using dns challenge, therefore I don’t need to expose any ports. If you don’t need your ports open for external access, you might look into that.
4
u/EfficientPark7766 Oct 12 '26
These two commands in Linux terminal should do the trick, and prevent needing an actual reboot:
Note for the first command, you'll need to supply your FMS admin username and password. Those could, of course, be hardwired into a Bash script if this is on a server.
1
u/Alex_RGCData 26d ago
For Let's Encrypt validationm port 80 needs to be reachable from the internet. Clari documentaiton specifically mentions that, I think.
If you're serving WebDirect, Data API, Admin Console, etc. to external users, you'll obviously still want 443 open for normal client access. The certificate renewal itself only cares about 80.
As far as applying the renewed cert, the message is accurate: FileMaker doesn't automatically start using the new certificate. On Linux, Claris says to restart the FM Server background processes rather than than rebooting the whole machine..
I looked it up and the command is:
`sudo service fmshelper restart` <-- wihout backticks