Hello everyone,
Does anyone know if there is an expected timeline for IPv6 support in HestiaCP?
I’m currently dealing with a high demand for IP addresses and need to use IPv6. Has anyone managed to get it working this way? Or is there any information on whether the upcoming version will include native IPv6 support?
Thank you in advance!
I would also be interested as well 4 days ago my Datacenter that used to give away free blocks of IPv4s are now going to charge for them in April.
However we got a /48 block of IPv6 addresses and would love to use them for some of my HestiaCP Platforms
Hestiacp.com and forum.hestiacp.com have an IPv6 address. Maybe they are running a dev version of HestiaCP that has IPv6 support.
Which gives me hope it might be just around the bend.
Hi,
@Corianito and @asmcc worked on it but their changes were not merged. It’s difficult to add it now because there are so many pending PRs and you would need to change many things. However, as far as I know, they want to work on it again.
@sahsanu thanks for confirming. Im just glad there is some work being done with IPv6.
Hestiacp.com must nut use their own Web Hosting Control Panel hestiaCP.
@johnny You do not need IPV6 support inevitably directly under HESTIA to use a IPV6 address. Also alternytive ways for it are possible. For example cloudflare. And I assume, that HESTIA team uses one of these alternative ways. And please, no conspiracy theories here. Hestia CP team does not have a especially and secret version of IPV6 support. And no one else besides @Corianito and myself is dealing with this topic here.
Before I began to work on this topic here 3 years ago a rudimentary version of IPV6 support has existed here. But it was really very rudimentary and does not work. Based on this version I began to work on the topic an until end of 2023 I rewritten the main required functions, like add / delete IP address, Web-Domain, E-Mail and DNS functions including Web Interface, Templates and so on. A part of these changes was commited to the ipv6 branch of HESTIA on GITHUB. The rest you can find in the IPV6 branch of my fork on GITHUB. But I stopped my work in October 2023, since it was to complicated for me each time to adjust my scripts acoording to changes in the main branch. And end of 2023 there have been a number of changes here in the main branch. That was contraproductive and demotivating for me to follow these changes in parallel.
In the spring 2025 @Corianito continues the work on IPV6. Unfortunately he took a itterim version of my work, which was available on the IPV6 branch under HESTIACP GITHUB. The last version was available only under my own fork. @Corianito didn’t know that. @Corianito tried to check in his work into HESTIACP main branch as PR, but due to various problems with testing procedures, review process under HESTIACP and low interest of HESTIA team to IPV6 topic his activities are frosen here since Summer 2025.
2-3 weeks ago I came back here and will continue my work. I do not know, if I will manage it, but I will try it again. First of all I actualised my old stuff from October 2023 to the actual HESTIA. That is a very complicate merging with a lot manually decisions of conflicts. But that is done yet. In the next step I made my own IPV6 branch DEBIAN13-ready (thanks to @sahsanu). That is important, because DEBIAN13 is already stable since middle 2025 and I would not start here with an old system. In parallel I contacted @Corianito to synchronise my further steps with him. And we are still in contact. Thereafter I cloned the IPV6 branch from @Corianito fork and extracted its commits to separate patches. Now I can (theoretically) make a so named “CherryPicking” and merge the stuff of @Corianito into my own. “Theoretically” because practically it does not always work. In the end you need review and manual merging, almost always. But I still working on it. Sometimes I can copy-paste the stuff of @Corianito, sometimes I have to rewrite it. That is a long-long process, but I’m still working on it. If you are familar with GITHUB, you can track all the steps on my GITHUB Fork. See my activities on the IPV6 branch:
Network Graph of asmcc / hestiacp
If we are more or less ready with the work, we can commit it to the IPV6 branch under HESTIACP GITHUB. But merge into the main branch could be really very complicated because of a lot serious changes, as @sahsanu already said.
The problem with all of this is the lack of motivation.
In other words, if the Hestia team isn’t truly committed to the implementation and keeps pushing changes in Hestia while neglecting the IPv6 work, it’s impossible, because IPv6 involves so many changes that they’re simply unfeasible. I just hope @asmmc isn’t doing any work that will be for nothing.
Honestly, it’s not a motivation issue — it’s a time issue.
We’re still here and still working on it. Progress is slower than we’d like due to real-life commitments, but the project is not abandoned.
Sorry! No, no, I wasn’t referring to your lack of motivation, not at all. I’m totally grateful to you all, without a doubt!
I’m referring to our lack of motivation… let me explain… if we do a lot of work modifying many files and then Hestia’s modifications with the PRs overwrite them, it forces us to review everything again. I don’t know if I’m explaining myself clearly, sorry, but I’m using a translator.
I think the problem with Hestia is that people want everything to work at once, which is often impossible. Perhaps it’s better to introduce small improvements that don’t break the entire project. For example, uploading a PR file where IPv6 addresses can be added, edited, or deleted, even if it doesn’t really do much good at first. Then uploading another file that allows firewall rules. I don’t know… I’m not really sure what the best approach would be, but we can’t break such a huge project as enabling IPv6 support; it involves so many changes across so many files.