State of a IPv6 only install in 2026

As an experiment I wanted to try to do an ipv6 only install again.

(ipv4 public IP’s are exhausted and often carry additional cost, both in a DC and at home)

IPv6 can fix that.

Things I discovered:

  1. The install script will fail with network unreachable on both alma and debian with slightly different errors both related to networking “error code 7” and something about that it can’t get something it wants from github (notoriously not ipv6 compliant).

The fix: Use NAT64+DNS64 DNS Servers like:

  • 2a01:4f9:c010:3f02::1
  • 2a01:4f8:c2c:123f::1
  • 2a00:1098:2c::1

these are from nat64.net

  1. After that script wil succeed installing correctly; slight cosmetic fault, it will print the IPv6 with port 10000 without Brackets. For a browser to open it the IPv6 should be printed with Brackets like [ and ]

Example:

[SUCCESS] Installation Complete!
[SUCCESS] If there were no errors above, Virtualmin is ready to be configured
[SUCCESS] at https://purev6.vom-bruch.org:10000 (or
[SUCCESS] https://2a0e:97c0:711:38c::1:10000).

Should be

https://[2a0e:97c0:711:38c::1]:10000

  1. After Running through the Wizard you will get the following Errors:
AH00526: Syntax error on line 367 of /etc/httpd/conf/httpd.conf:
<VirtualHost> directive requires additional arguments

this is beacuse is empty and has no IP or port.

You can fix by adding ipv6’s and ports.

for example:

<VirtualHost [2a0e:97c0:711:38c::1]:443>

After fixing those errors you will get a new error:

AH00112: Warning: DocumentRoot \[/home/.\_hostname/public_html\] does not exist
AH00526: Syntax error on line 399 of /etc/httpd/conf/httpd.conf:
SSLCertificateFile: file '/etc/ssl/virtualmin/178156572434850/ssl.combined' does not exist or is empty

to fix you need to add the actual path instead of the placeholder “.\_hostname
and remove the cert line. This applies to the FQDN of the host.

Afterwards you can request a new SSL cert plus wildcard.

Afterwards it appears many things work without errors.

Some odd things, A records despite no IPv4 is on eth0

On Alma with BIND there is no error, on debian 13 there is an error in the re-check config about something with 127.0.0.2 but it still mostly works.

I hope that in the future we can get more ipv6 only friendly.

In the UK a lot of our ISP still only provide IPv4, but we are turning into a backward country,

Wow all of the providers I’ve used in the last 7 years ish have supplied ipv6 connectivity with their inferstructure may it’s different in Wales to England :joy:

probably, plusnet is definitely IPv4 only. Our politicians think that 98% of the population has superfast broadband.

Can you be more specific? I don’t think anything is ever downloaded from github in the installer? If it is, it shouldn’t be.

I think it was this:

Cookie coming from download.virtualmin.com attempted to set domain to github.com

for debian 13

on alma the error is:

[2026-06-15 23:05:23 UTC] [INFO] Installing Virtualmin 8 stable repository: [2026-06-15 23:05:23 UTC] [INFO] Failed with error: 7
[2026-06-15 23:05:24 UTC] [ERROR] Something went wrong. Exiting.

I don’t even know what to make of that.

This was the download script from here: Downloading and Installing | Virtualmin — Open Source Web Hosting Control Panel ?

Yes official script. Maybe I will spin up a test Debian 13 again to copy full error

I wonder what output you get if you run:

wget https://github.com/webmin/webmin-ci-cd/releases/latest/download/install-ci-cd-repo.sh

@Joe, the issue with depending on GitHub during the installation process has been fixed.

@lawk, I’d recommend running the installation one more time—it should work now. Yet, I’d still be interested to see the output of the command from my previous comment.

The installer works now!

The wget command gives failed: Network unreachable

Great!

It sounds like there may be a network issue on your end. Or maybe you should use NAT64 with DNS64 to let your IPv6-only client reach IPv4-only hosts. Otherwise, many things will break for you.

Try you using -6 after wget