Thank you for the review!
To provide a bit more insight here:
We’re big fans of running only the latest software/technology – as we often benefit from increased security, performance, and stability, when doing so.
OpenVZ [our virtualization platform] released a new update on December 20th, 2022: https://download.openvz.org/virtuozz….0/x86_64/iso/
After running it in a test lab for a while, we saw no issues at all – and deployed it to production on a brand new node we added.
However… after a few weeks, it became apparent this new version has a bug concerning IPv6 connectivity, namely, after a while, IPv6 ARP traffic dies off, and the only way to restore it is to restart networking on the hypervisor (which in itself isn’t ideal because doing so knocks out connectivity for customer VMs, and requires them to be restarted).
What does this have to do with CyberPanel, you may be wondering:
A lot of scripts make the [rather poor] assumption that if a server has an IPv6 address assigned to it, that it must have valid connectivity. That’s most definitely not the case.
DirectAdmin, for example, in their most recent [unreleased] update ( https://docs.directadmin.com/changel…n-da-installer ) have implemented checking to ensure IPv6 does actually work properly, otherwise, it causes all kinds of problems down the line.
CyberPanel is no exception here, and just as bad.
The reason your install took so long initially was because of this same issue – CyberPanel assumed that just because the server has an IPv6 address, it should work perfectly, and so it was favouring IPv6 connectivity when trying to retrieve the necessary files for the installation – leading to it eventually timing out, and failing back to IPv4.
SolusVM is another good example of poor coding standards. If IPv6 is assigned, but not working, it can easily take an hour to run a software update, because it constantly tries to use the IPv6 address, times out, tries again, and repeat – until eventually realizing it needs to use IPv4 instead.
In your case, I removed the IPv6 address, re-ran the CyberPanel installer and then it took something like 10-15 minutes to complete.
If IPv6 is something you’d like, that’s not a problem – we still have plenty of nodes running a slightly older version of OpenVZ which doesn’t have this IPv6 bug, and can place your VPS on one of those.
I’m going to speak to the developers of CyberPanel to see if they’d be willing to implement proper IPv6 connectivity checks, just like DirectAdmin have done in an upcoming update.
We are also working with the OpenVZ developers to try and reach a solution concerning IPv6 not working as it should do.
