Closed bkonkle closed 5 years ago
In the meantime, I'll try without a --domain
flag and see if I can successfully ALIAS the result.
This one's on me. I was trying to use a domain that we don't actually control in Route53 - we're just shadowing an existing domain. No wonder lego wasn't able to find the record!
I'm deploying with concourse-up like this:
I have a hosted zone in AWS for
communityfunded.io
. When I try to spin up a whole new deployment, I get this:I also tried adding a hosted zone for
concourse-ci.communityfunded.io
, but got the same result.I'm using v0.19.0, and I also tried reverting to the previous version with the same result.
Any ideas?