bitnami
myip.bitnami.com does not work for IP detection from IPv6-only instances
Platform
AWS
bndiagnostic ID
not applicable
cloud-init error output
warn: Unable to resolve IP address using http://myip.bitnami.com/ connect ETIMEDOUT
warn: Unable to resolve IP address using http://myip2.bitnami.com/ connect ETIMEDOUT
...
bndiagnostic was not useful. Could you please tell us why?
network issue is with myip.bitnami.com
Describe your issue as much as you can
dig myip.bitnami.com AAAA
Produces no records in the answer.
But even if it worked correctly, are bitnami cloud-init scripts ready to work in IPv6-only situations?
Hello! @paxan
Platform AWS
bndiagnostic ID not applicable
cloud-init error output warn: Unable to resolve IP address using http://myip.bitnami.com/ connect ETIMEDOUT warn: Unable to resolve IP address using http://myip2.bitnami.com/ connect ETIMEDOUT ... bndiagnostic was not useful. Could you please tell us why? network issue is with thedisneyhub myip.bitnami.com
Describe your issue as much as you can dig myip.bitnami.com AAAA Produces no records in the answer.
But even if it worked correctly, are bitnami cloud-init scripts ready to work in IPv6-only situations?
The issue arises because myip.bitnami.com and myip2.bitnami.com do not resolve in IPv6-only environments, causing network timeouts. These services lack AAAA records, indicating no IPv6 support, which makes Bitnami cloud-init scripts incompatible with IPv6-only setups. To resolve this, check your network configuration and consider modifying the cloud-init scripts to use an alternative service like http://ipv6.whatismyip.akamai.com/ for IP resolution in IPv6 environments. If issues persist, consult Bitnami support for assistance.
Hope this helps!
@paxan can you tell us which application are you trying to deploy with IPv6-only support? Can you also tell us if you are using AWS Lightsail or regular EC2 images and for which region? I did a test recently (February this year) and I was able to properly launch a WordPress instance in EC2 with IPv6-only support.
Apart from getting those warnings in the cloud-init log, was your application properly deployed?
https://bitnami.com/stack/mean
This was noticed on a IPv6-only Lightsail instance running in us-east-1.
cloud-init succeeded after about ten minutes of trying and failing to interact with myip and myip2 endpoints (all of errors are "Unable to resolve IP").
This long delay in cloud-init blocks launch scripts that run after cloud-init. Resulting in pain caused by this latency.
Hi @paxan,
Thanks for the information. We will take a look into it. I'm adding the on-hold tag. We will keep you posted.