You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using a vanilla three container solutions with Whoami for testing, nothing custom.
The only thing that's causing this issue is an AWS EC2 instance running inside an IPv6 only PVC, meaning no public IPv4. Running this same vanilla test on a dual stack VPC runs absolutely fine.
Here is the error:
Can not init api for: https://acme-v02.api.letsencrypt.org/directory.
Then times out and tries again a minute later with the same result.
Is there a setting I need to change to get acme-companion to successfully access the api endpoint and generate the necessary certs?
The text was updated successfully, but these errors were encountered:
Using a vanilla three container solutions with Whoami for testing, nothing custom.
The only thing that's causing this issue is an AWS EC2 instance running inside an IPv6 only PVC, meaning no public IPv4. Running this same vanilla test on a dual stack VPC runs absolutely fine.
Here is the error:
Then times out and tries again a minute later with the same result.
Is there a setting I need to change to get acme-companion to successfully access the api endpoint and generate the necessary certs?
The text was updated successfully, but these errors were encountered: