# Unable to get a Certificate using current FileMaker Server **URL:** \ **Category:** Help\ **Created:** [February 4, 2026, 7:09pm UTC](https://community.letsencrypt.org/t/unable-to-get-a-certificate-using-current-filemaker-server/245132 "2026-02-04T19:09:18Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [February 5, 2026, 3:46pm UTC](https://community.letsencrypt.org/t/unable-to-get-a-certificate-using-current-filemaker-server/245132/8 "2026-02-05T15:46:22Z")
> [@stevemaser](#): > > Does Let's Encrypt have a specific set of source IPs we can set on the firewall so that 80/443 are not fully open to the world, but just open for these certificate requests/renewals? Let's Encrypt does not publish a list of IP addresses used by its validation servers (currently 5 different centers world-wide with rotating IP). You only need to allow URI of format `/.well-known/acme-challenge/(token)` on port 80. Any other inbound requests can be blocked or, perhaps better, redirected to 443. You don't need to open anything different inbound on port 443 to satisfy an HTTP challenge unless you redirect the original HTTP request to port 443. That is under your control at your server. Alternatively, there is a DNS Challenge which does not require any HTTP request inbound but has its own security concerns given you use a security token to update DNS records (adding and deleting TXT records). This explains the multi-perspective validation in detail: [Multi-Perspective Validation & Geoblocking FAQ](https://community.letsencrypt.org/t/multi-perspective-validation-geoblocking-faq/218158) --- _[View the full topic](https://community.letsencrypt.org/t/unable-to-get-a-certificate-using-current-filemaker-server/245132)._