New server creates duplicate ip entries in ssh.conf

This occurs on CentOS 7 . When creating a new virtual server a new IPV6 line is created in ssl.conf 9=(/etc/httpd/conf.d/ssl.conf). This causes httpd to crash and unable to start until the entry is removed.

Deleting the server does not remove the entry.

I think this has only started occurring after the last update as I have not had an issue with it before but there is a comment at https://www.virtualmin.com/node/33637#comment-137155 from 09-10-2014 .

Status: 
Closed (fixed)

Comments

Can you post the two duplicate lines? There was a bug that could cause this, but it should have been fixed in the latest Virtualmin release.

This is the contents at the top of /etc/httpd/conf.d/ssl.conf

#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
Listen 443
Listen 94.xxxx.34.51:8080
Listen 2A02:1A9:4:2000::94.xxxx.34.51:8080
#Listen 2A02:1A9:4:2000::94.xxxx.34.51:8080
#Listen 2A02:1A9:4:2000::94.xxxx.34.51:8080

On finding the duplicate entries I went in and added the '#' . I have also changed the IP addresses in this post to obscure.

I am using port 8080 as have varnish installed.

This occurred yesterday when I was creating the server using the default template, it was the first time I have had this problem.

The address2A02:1A9:4:2000::94.xxxx.34.51 looks wrong - it shouldn't have a mix of : and . separated parts. Is that the actual IPv6 address of the domain?

Thank you for pointing that out. I had not looked into IPV6 before so did not realise it was wrong. Now I have.

In Network Configuration > Network Interfaces the Active Now tab contains the correct entries(and correct IPV6 address as per "#ip addr show") but Activated at Boot contained the weird IPV6 address. I did not enter the weird address by mistake or anything, I do not think I entered one at all.

I will close this issue as I haven't a clue what is going on. Once(if) I get my head round it, if the duplicate thing happens then I will report back.

Thanks for taking the time to check

Edit: Just wanted to mention that the "weird" IPV6 address contained the first half of the correct IPV6 address then the IPV4 address.