This is the hard way especially if you are juggling between dozens of websites. You can either script this or copy and paste the IPv4 configs to the IPv6 configs for the new IPv6 listeners in httpd_config.conf, like so. Note the pattern in the map sections.
listener Default {
address *:80
secure 0
map websitea.com websitea.com
map subdomaina.websitea.com subdomaina.websitea.com
}
listener Default IPv6 {
address [ANY]:80
secure 0
map websitea.com websitea.com
map subdomaina.websitea.com subdomaina.websitea.com
}
listener SSL {
address *:443
secure 1
keyFile /etc/letsencrypt/live/hostdomain.com/privkey.pem
certFile /etc/letsencrypt/live/hostdomain.com/fullchain.pem
certChain 1
sslProtocol 24
enableECDHE 1
renegProtection 1
sslSessionCache 1
enableSpdy 15
enableStapling 1
ocspRespMaxAge 86400
map websitea.com websitea.com
map subdomaina.websitea.com subdomaina.websitea.com
}
listener SSL IPv6 {
address [ANY]:443
secure 1
keyFile /etc/letsencrypt/live/websitea.com/privkey.pem
certFile /etc/letsencrypt/live/websitea.com/fullchain.pem
certChain 1
sslProtocol 24
enableECDHE 1
renegProtection 1
sslSessionCache 1
enableSpdy 15
enableStapling 1
ocspRespMaxAge 86400
map websitea.com websitea.com
map subdomaina.websitea.com subdomaina.websitea.com
}
Ideally, CyberPanel would be updating all of this in the background. It would be running the same bit of parsing code as it already does when creating a new website and adding a new domain, except it would be adding the domain mappings to the two IPv6 listeners as well. @usmannasir, could you update the website script to add IPv6 listeners to simultaneously update them along with the IPv4 listeners? I am pushing a commit for your approval.