We updated the statuspage here: Fly.io Status - Routing issues for newly allocated IPv6 addresses
If you’re currently having cert errors, this is the most likely reason.
We updated the statuspage here: Fly.io Status - Routing issues for newly allocated IPv6 addresses
If you’re currently having cert errors, this is the most likely reason.
Workaround worked for me too. Thanks.
A fix has been rolled out. Sorry about all of that, there are more rough edges with shared IPs than we initially thought.
IPv6 routing appears to still be an issue. I had to remove the AAAA DNS records for my domain to get certificates issued.
We actually won’t issue a cert at all unless there is an AAAA record. Can you give us some more details on the sequence here?
I am not 100% sure of the steps since I did not expect to run into issues
I think the order of events was:
Your certificate for <domain> is being issued. Status is Awaiting certificates.
_acme-challenge
and tried deleting and recreating the certificateCurrently my domain does not have an AAAA record. Weirdly, the UI still shows that Fly thinks that I do have an AAAA record (I tried hitting Check again
and nothing changes).
This one worked out for me.
Currently experiencing this same issue. Tried different stuffs, Nothing seems to be working