Dennis
Since RIPE has run out of IPv4 addresses it is time to officially support IPv6.
www.ripe.net/publications/news/about-ripe-ncc-and-ripe/the-ripe-ncc-has-run-out-of-ipv4-addresses
Peter Kuipers
oooh yes !!!
Begono
Vel enim sint ad quisquam excepturi ut aspernatur optio et ipsum earum et voluptates itaque? Et sequi velit aut aliquid quos qui nisi omnis eos ullam nihil cum harum error eum voluptas optio.
Julius Kiekbusch
@Dennis what is currently blocking the IPv6 Support for Let`s Encrypt?
Certbot should be able to install the Certificate without any Problem: https://letsencrypt.org/docs/ipv6-support/
There are already Server/Cloud Providers where an IPv4 Address costs monthly more.
Dennis
Item authorThere's not really something blocking at the moment, we're in the works of prepping for IPv6 support.
Athul Raj
This would let us use the 2.5$ Vultr IPV6-only instance. Kinda awesome for small workers.
Tom D.
Hi @Dennis, when is going to be ready? I just did a test and could not add a custom server with ip6 only. It has been a year already :) that you announced it was time to support...
Joseph Szobody
Now that AWS is charging for IPv4 addresses, this is urgent.
Our servers don't need public IPs since they sit behind load balancers. However Ploi requires public IPs to connect. We are now paying well over $100/month to AWS just to have public IPs available to Ploi.
Iola Christian
@Joseph
Iola Christian
@lola Christian
Mark
Well that is an awkward silence. Anybody care to enlighten us?
Regards, Mark
Begono
Begono
Quo rerum repellendus qui labore eius sed animi quidem? Eum accusamus quia ea excepturi doloribus ut mollitia deserunt. Et sint rerum non earum quos eos nostrum eaque.
Tim Hoepfner
Super important
sebastienfontaine
any news please?
Mbekezeli Mhlanga
This is a required thing to be supported since the world is rapidly adopting IPv6.
Can we pretty please get an update on this ?
Kris
Hi, any idea when IPv6 will be implemented?
Dennis
Item authorOk so we're going to actively work on this. Theres 2 parts that need support:
- Servers need IPv6 support, e.g.; you will be have to be able to install server with IPv6 addresses instead of IPv4
- Webserver support, we'll need to adjust the vhost creations more properly to support IPv6, currently, it's basically already in there, but it needs fine-tuning.
Will get back very soon on this 🥰
Julius Kiekbusch
Hey @Dennis,
Thank you for taking this up!
Does this mean the following combinations will be possible:
- IPv4 only (like the current servers)
- IPv6 only (e.g. worker servers)
- IPv4 and IPv6 hybrid (probably the new default for many servers)
The ploi worker servers should also have IPv6 and should probably be added to the whitelist, if the connection happens over IPv6 instead of IPv4: https://ploi.io/documentation/introduction/ploi-ip-for-whitelisting
shalom
affa
Lukas
Josh Green
Any update on this? Want to start really using Ploi for myself, my customers and other companies I freelance for and IPv6 only setup + connection is required!
Josh Green
Any update on this?.... Will have to stop using Ploi at this rate for the few accounts I manage unfortunately.
Dennis
Item authorAre you specifically in need for IPv6 for the server connection? Or are you talking about webserver?
Ansgar Hofmann
There are providers, like hetzner, where the ipv4 costs extra per month. So this feature would need to manage a server that just has no ipv4 address.
Stephan Pfleger
I need to +1 this, we also have many servers hosted on Hetzner. But e.g. our worker servers only need an IPv4 address to be compatible with Ploi. They do not need the address otherwise.
Josh Green
Exactly this, but not only with Hetzner, most cloud providers are moving in this direction (rightly). Our AWS bill is almost 300usd more expensive a month due to having to pay for ipv4 addresses that we would not actually need to use. (CF routes v6 addr via its cdn via v4)
Josh Green
I wan't to setup + manage my server using IPv6 only, e.g. I paste in the v6 IP, you connect via v6, setup the server and allow me to use ploi just over v6.
I do not want to have to pay for ipv4 as the costs are going up and we hit our upper limits with AWS and Hetzner without having to give justifying reasons for why we need more IPv4.
We don't actually need any IPv4, IPv6 will route via v4 via CF which all if not all of our services use.
Is this still planning to be done? If so, how urgent is it? This thread is years old and is the only thing Ploi is missing from being the main deployment pipeline I can recommend to clients and use for all our services.
Josh Green
@Dennis, sorry to continue to tag you but it seems this is how we get a response, this ticket is #1 upvoted. This is a major selling point for Ploi once integrated, MAJOR.
We are all CRYING out for this update, please can you provide us an update on this and if there is going to be a delay, is there a reason?
Dennis
Item authorHi @Josh-Green,
Did you manage to provision a server yet with IPv6? Would love to hear your experiences.
Dennis
Item authorHi @Josh-Green,
Another friendly reminder, did you manage to test this yet? Seeing from the amount of requests you made here it looked urgent, but now I am not hearing anything anymore from you 😢
Josh Green
Hi @Dennis,
Unfortunatley this co-incided with a very busy period with many deadlines. I was able to test it on one of my clients instances, and found the GitHub issue. This isn't ideal at all and currently trying to contact them to find out how far down the pipeline that will be, alternatively we will have to work out how to proxy ipv4 maybe via WireGuard.
I will come back to you ASAP on further developments, but ultimately I am very happy as we hopefully can now ditch a bunch of AWS costs providing we work out a solution to the above.
Sebastian Albert
Please add full ipv6 support. We really need that in 2025. Let's encrypt certification fails when a AAAA record is available.
Josh Green
Using v4 when not needed is crazy as well in 2025, we are paying for it literally.
Dennis
Item authorYes, it is coming 🙌 I will see if we can get that sorted this month, and otherwise it'll be May.
We've already prepared the server connections. NGINX configurations are next.
Josh Green
Thank you so, so much !
Tom D.
Looking forward to that! Thx
Jelle
The screenshot on X looked very promising!!
Dennis
Item authorThings are cooking at Ploi HQ 👀 (Oh and, yes, older servers will also be able to use IPv6)
Dennis
Item authorJust to give you some updates here, we've been hard at work! We are at 98% of completion.
We've just finished up testing all the native providers, which I can talk about here (which will be in the newsletter as well):
What providers work with IPv6?
Basically all providers work with IPv6, it’s just a matter of provisioning the server that’s different.
- UpCloud: Works completely
- DigitalOcean: Works, but you always get an IPv4 record as well, it is not possible to create IPv6-only servers
- Hetzner: Works completely
- Amazon: Works completely
- Vultr: Works completely
- Hostinger: Works, but you always get an IPv4 record as well, it is not possible to create IPv6-only servers
- Linode: Works, but you always get an IPv4 record as well, it is not possible to create IPv6-only servers
- Katapult: Works, but you always get an IPv4 record as well, it is not possible to create IPv6-only servers
Other than that all the UI, validation and custom logic has been refactored, it's working really nice. All our workers have been equipped with IPv6 as well, which will be listed in our article as well soon.
Dennis
Item authorI've just silently released IPv6 support!
Ff you'd like to test it: send me a DM on Discord or Twitter (https://x.com/dennis_smink, or a tweet if you can't DM me).
My personal tests just now looked really, really promising. Will be doing a short testing period of 2/3 days with testers, gather some feedback and then officially launch.
Josh Green
What is your discord?
Dennis
Item authordennissmink (367360521764339722)
Tom D.
I have tested ip6 with hetzner. Everything went smooth as expected. The only issue I had was with Github. As it turns out, Github does not support ip6. I was not able to install my repository. Gitlab does support ip6... and the installation went smooth as well. Good job @Dennis
Josh Green
Has anyone tested IPv6 with AWS? Got around the IPv4 issue with Github using a NAT instance setup, so that the instances CAN use v4 for GH. Can't set the server up it says its not accessible but ipv6 port checkers online can see the service.
IPv6 support
-
Dennis moved item to board Live
2 months ago -
Dennis moved item to board In progress
2 months ago -
Dennis moved item to board Planned
3 years ago -
Dennis moved item to project Server Level Requests
3 years ago -
Dennis opened
3 years ago