When adding a custom cert, it seems to be refusing to show a AAAA record to create. I can confirm the same in the dashboard, only showing an A record and won’t let me progress. I have a machine created that is started, and have not had this issue with other apps.
It gave me an IPv4 to use for an A record, and seems to recognize that is set just fine.
Deleting the cert and IP and re-adding shows this:
➜ dangoodman: ~/code/aspiring.dev git:(main) ✗ fly certs add aspiring.dev 5:25PM
A Record (168.220.92.66) does not match app's IP ()
Address resolution (168.220.92.66) does not match app's IP (/)
You are creating a certificate for aspiring.dev
We are using lets_encrypt for this certificate.
You can direct traffic to aspiring.dev by:
1: Adding an A record to your DNS service which reads
A @
You can validate your ownership of aspiring.dev by:
2: Adding an AAAA record to your DNS service which reads:
AAAA @
but no IPs so not sure where it’s getting that one
➜ dangoodman: ~/code/aspiring.dev git:(main) ✗ fly ips list 5:26PM
VERSION IP TYPE REGION CREATED AT
Learn more about Fly.io public, private, shared and dedicated IP addresses in our docs: https://fly.io/docs/reference/services/#ip-addresses
Ah ok I had to allocate both v6 and v4, IIRC v6 used to auto generate!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.