Cert Renewal Failure

My domain is: skytechsecure.com

I ran this command: doas certbot -v certonly --standalone --http-01-port=8888 -d skytechsecure.com

It produced this output: Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: skytechsecure.com
Type: connection
Detail: 66.42.84.127: Fetching http://skytechsecure.com/.well-known/acme-challenge/gEHHPbrv-x9H8gNkRlbsbqthTXV6KdWzYF-wNl4CunM: Timeout during connect (likely firewall problem)

My web server is (include version): N/A

The operating system my web server runs on is (include version): FreeBSD 15.1-RELEASE-p5

My hosting provider, if applicable, is: VULTR

I can login to a root shell on my machine (yes or no, or I don't know): no

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): 4.2.0

I have the port open via anchor in PF, and a port scan shows the port as open.

HTTP-01 must use port 80 (or port 443 after a redirect to HTTPS), is port 80 on your router/firewall being forwarded to port 8888?

Have you verified this IP address?

I can only connect to TCP port 22 (SSH) and 25 (SMTP), TCP port 80 and 443 are both filtered (not refused like with other ports). Have you checked the control panel to see if these ports are blocked?

Port 80 redirect to a jail when HAProxy is running and it handles the TLS. I thought I used port 8888 when setting my cert up initially. Is there a different test I can use?

If HAProxy is handling TLS...
Isn't that who should be requesting the cert?

Does HAProxy do that?

Enable TLS by using the ACME protocol | HAProxy config tutorials

ACME: native haproxy · haproxy/wiki Wiki · GitHub

Since HAProxy terminates TLS, the jail only needs to pass the challenge token, not to hold the cert. Two clean ways out: have HAProxy answer HTTP-01 by routing /.well-known/acme-challenge/ to the jail on 8888, or drop inbound ports altogether and use certbot's DNS-01 plugin for whichever provider holds the zone. Before rerunning, fetch that challenge path from outside once - a timeout versus a 404 tells you whether the Vultr panel or your pf anchor is eating it.