# IPv6 support **Project:** Servers | **Board:** Live | **Votes:** 76 **URL:** https://roadmap.ploi.io/projects/1-server-level-requests/items/2-ipv6-support --- 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 --- ## Comments **Peter Kuipers ** (2022-06-06T12:16:05+00:00): oooh yes !!! **Julius Kiekbusch** (2022-06-21T15:07:10+00:00): [@Dennis](/user/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. **Athul Raj** (2022-10-13T15:59:21+00:00): This would let us use the 2.5$ Vultr IPV6-only instance. Kinda awesome for small workers. **Ricardo** (2023-02-13T19:08:34+00:00): [@Athul-Raj](/user/Athul-Raj) Interesante **Tom D.** (2023-12-16T08:10:02+00:00): 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** (2024-03-20T16:42:38+00:00): 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** (2024-04-15T09:45:14+00:00): @Joseph **Iola Christian** (2024-04-15T09:45:44+00:00): .[@Fred](/user/Fred) **Iola Christian** (2024-04-15T09:46:11+00:00): @lola Christian **Mark** (2024-04-25T15:04:07+00:00): Well that is an awkward silence. Anybody care to enlighten us? Regards, Mark **Begono** (2024-04-26T20:38:53+00:00): ![](https://roadmap.ploi.io/storage/Rv6sZK9BuRwcYTmEvjKpOzkxhzyemwJnSh94m5J4.jpg) **Begono** (2024-04-26T20:39:11+00:00): 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** (2024-05-23T12:43:10+00:00): Super important **sebastienfontaine** (2024-06-06T22:05:29+00:00): any news please? **Mbekezeli Mhlanga** (2024-08-28T09:13:25+00:00): 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** (2024-09-30T13:24:54+00:00): Hi, any idea when IPv6 will be implemented? **Dennis** (2024-11-28T15:32:14+00:00): Ok so we're going to actively work on this. Theres 2 parts that need support: 1. Servers need IPv6 support, e.g.; you will be have to be able to install server with IPv6 addresses instead of IPv4 2. 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** (2024-11-29T07:54:00+00:00): Hey [@Dennis](/user/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** (2025-02-09T13:39:01+00:00): Hey [@Dennis](/user/Dennis), **shalom** (2025-02-09T13:39:38+00:00): affa **Lukas** (2025-02-09T20:33:23+00:00): ![](https://roadmap.ploi.io/storage/9hYMZ2JlB0CajQzLUFoWC0zrZ0Wunokl40Uwxnwq.jpg) **Josh Green** (2025-04-02T20:56:22+00:00): 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** (2025-04-18T14:47:12+00:00): Any update on this?.... Will have to stop using Ploi at this rate for the few accounts I manage unfortunately. **Josh Green** (2025-04-18T14:47:39+00:00): [@Dennis](/user/Dennis) **Sebastian Albert** (2025-04-24T05:53:36+00:00): Please add full ipv6 support. We really need that in 2025. Let's encrypt certification fails when a AAAA record is available. **Dennis** (2025-04-28T06:48:27+00:00): Yes, 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. **Dennis** (2025-04-30T06:37:34+00:00): Things are cooking at Ploi HQ 👀 (Oh and, yes, older servers will also be able to use IPv6) ![](https://roadmap.ploi.io/storage/rkhROVaVnVgGTn4vyxgXFtqsgJVdDjesw232EN1v.png) **Dennis** (2025-05-02T16:24:50+00:00): Just 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** (2025-05-04T13:19:46+00:00): I'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. **Tom D.** (2025-05-13T09:26:48+00:00): 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](/user/Dennis) **Josh Green** (2025-06-18T19:36:07+00:00): 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.