Hi,
Since the update last night we are experiencing the following problem related to ipv6 and how the apache config is written.
When I check /usr/local/directadmin/data/users/xxxx/httpd.conf I see that the ipv6 ports are mixed up in the virtualhost stanza:
<VirtualHost xx.xx.xx.xx:80 [xxxx:xxxx:xxxx:x:x:x:x:x]:443 >
For the non ssl virtualhost and:
<VirtualHost xx.xx.xx.xx:443 [xxxx:xxxx:xxxx:x:x:x:x:x]:80 >
For the ssl virtualhost
Now when you have a site which is ssl enabled you will drop in a redirect loop, changing the port numbers will fix the issue but will probably be wewritten by the next directadmin config update.
Please advice.
Kind regards,
Kevin Phylipsen
Since the update last night we are experiencing the following problem related to ipv6 and how the apache config is written.
When I check /usr/local/directadmin/data/users/xxxx/httpd.conf I see that the ipv6 ports are mixed up in the virtualhost stanza:
<VirtualHost xx.xx.xx.xx:80 [xxxx:xxxx:xxxx:x:x:x:x:x]:443 >
For the non ssl virtualhost and:
<VirtualHost xx.xx.xx.xx:443 [xxxx:xxxx:xxxx:x:x:x:x:x]:80 >
For the ssl virtualhost
Now when you have a site which is ssl enabled you will drop in a redirect loop, changing the port numbers will fix the issue but will probably be wewritten by the next directadmin config update.
Please advice.
Kind regards,
Kevin Phylipsen