Letsencrypt and Floating IP over HAProxy problem

Hello,

It seems you’re having trouble with ACME challenges when your domain is pointed to a floating IP.

The ACME protocol, which is used by Let’s Encrypt, performs a check on the domain to ensure that you have control over it. When it fails, it’s typically because the ACME challenge request isn’t reaching your server or HAProxy isn’t routing it correctly.

Here are some things you could check or try:

1. Check DNS Settings: Ensure that the DNS settings for domainB.com are correctly pointing to the Floating IP (20.20.20.20). It may take some time for DNS changes to propagate.

2. Check Firewall Rules: Make sure there are no firewall rules blocking ACME challenge requests to the floating IP.

3. Check HAProxy Logs: Inspect your HAProxy logs to see if requests for the ACME challenge (i.e., requests to domainB.com/.well-known/acme-challenge/) are coming in and whether they are being correctly proxied to your backend server.

4. Check HAProxy Configuration: You might want to ensure your HAProxy is correctly configured to handle requests to domainB.com and route them to the backend server. Your acl and use_backend directives should look something like this:

acl letsencrypt-acl path_beg /.well-known/acme-challenge/
use_backend letsencrypt-backend if letsencrypt-acl

5. Check acmetool Configuration: Make sure acmetool is configured to correctly respond to challenge requests for domainB.com.

6. Test Without Floating IP: As a test, you might try pointing domainB.com to the public IP, similar to domainA.com, and see if it works. If it does, it indicates that the problem is likely related to the use of the floating IP.

Remember to restart HAProxy after making changes to its configuration.