[Wordpress] Support IPv6 only stack on AWS Lightsail

[enapupe]

Describe your suggestion as much as you can

I currently run a wordpress instance under a load balancer on AWS Lightsail, I'd like to have the instance running just on IPv6 to save $ on the unnecessary public IPv4. The base image currently doesn't support the Ipv6 only stack. Is that something you plan addressing anytime soon? THanks!

[gongomgra]

Hi @enapupe,

Thanks for using Bitnami. I have launched an EC2 instance with IPv6 address and I am able to see the WordPress website using the IPv6 public address without any change in the Apache or WordPress configuration. Which issue are you facing?

[enapupe]

Hello!
I'm unable to create a IPv6 only instance on Lightsail. Other base images can, so I assumed this is related to wordpress the base image, which I understand is maintained by you.
Thanks again!

The blueprint doesn't show up in the print but it's: WordPress Certified by Bitnami and Automattic 6.4.2-13

[gongomgra]

Hi @enapupe,

Sorry for the delay. Can you try it in other regions? With regular EC2 instances I had to launch it in a different region (us-east-2) because us-east-1 region didn't support IPv6 instances.

[enapupe]

That's not it. I tried all regions but as I mentioned earlier, some blueprints seem to support ipv6-only (no matter the region) but wordpress by bitnami doesn't.

Blueprints that seem to support ipv6-only:
MEAN Packaged by Bitnami 6.0.13-2
LAMP (PHP 8) Packaged by Bitnami 8.2.15-0

[enapupe]

By the way, maybe this issue should have been opened in https://github.com/bitnami/containers/ ? I'm not really sure if there's a repo for Lightsail blueprints

[gongomgra]

Hi @enapupe,

Can you try to launch an EC2 instance instead of a Lightsail one? Regarding the repo, I don't think your question belongs to that repo. If it is an AWS vm, you are in the correct forum.

[gongomgra]

@enapupe There is another question in this forum from a user who seems to have launched an IPv6 instance (not sure if IPv4 + IPv6 though). Can you ask him for further information? Not sure if you need to create anything else in Lightsail panel, but for EC2 instances I had to create my own VPC with IPv6 support and a public IPv6 range of addresses.

#1423

Hope it helps!

[enapupe]

Not sure if that issue is related.
My concern is that AWS Lightsail doesn't allow you to create a IPv6 ONLY instance for the Wordpress blueprint by Bitnami, only IPv4+IPv6.

I'm starting to consider picking a base OS blueprint and installing WP myself.

[gongomgra]

Hi @enapupe,

I have reproduced your issue of not being able to launch a WordPress instance in Lightsail with IPv6 only. We have an internal task to review and fix that, but we have not being able to check it yet. I suggested asking the other user in case he can provide more information on the exact steps he followed or if it is available for some of our assets only. Sorry for the inconveniences.

[enapupe]

Cool, thanks I'm still not convinced that other issue has any relation to this. In any case, I've spinned a regular ec2 instance with bitnami's image rather than Lightsail, that gave me enough customization to skip the public ipv4 and life is good.

…

On Wed, Mar 6, 2024, 13:00 Gonzalo Gómez Gracia ***@***.***> wrote: Hi @enapupe <https://github.com/enapupe>, I have reproduced your issue of not being able to launch a WordPress instance in Lightsail with IPv6 only. We have an internal task to review and fix that, but we have not being able to check it yet. I suggested asking the other user in case he can provide more information on the exact steps he followed or if it is available for some of our assets only. Sorry for the inconveniences. — Reply to this email directly, view it on GitHub <#1419 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACHCCUWJDDEIWWW3WMYLXTYW44Q7AVCNFSM6AAAAABDRBDJ4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBRGIYDIOBXGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gongomgra]

Hi @enapupe,

Thanks for your message. I'm glad launching a regular EC2 instance worked for you. We will close this ticket as solved. Please do not hesitate to open a new one with any other questions you may have.