Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 2600 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

After Certificate Update, can´t start multiple Webservers on the same external IP

seroal

Hi,

I have a problem with the WAF. After I updated the ssl cert on the machine (turn virtual-servers off, then change the certificate and after importing the new certificate) I wanted to reactivate the both virtual servers, that were running on the same ip address before. Now I cannot activate them, i get an errormessage:

The virtual web server domain name 'WAN [a.b.c.d] (Address):443:*.my-name.com' is already in use by the domain list attribute of the virtual webserver object 'test123'.

 

Does somebody know, why I can´t reactivate it? Isn´t SNI not working any more or where is the problem?

 

Would appreciate your help,

 

Regards

Sebastian



This thread was automatically locked due to age.
Parents
  • 0

    Hi all,

    the problem is solved. It is related to the wildcard certificate, that was in use. I found out, that as FQDN/Domain Name the same two entries were configured for two different vservers. That worked before for a long time.... Instead of the real hostname, that matches the SNI Value in the https request, we configured only the second level domains like this

    *.test.com and test.com

    As I said, this worked fine until we had to update the certificate yesterday... But I think the configuration was not totally correct... It was based of a wrong thought in relation to the wildcard certificate.

    Regards

    Sebastian

Reply
  • 0

    Hi all,

    the problem is solved. It is related to the wildcard certificate, that was in use. I found out, that as FQDN/Domain Name the same two entries were configured for two different vservers. That worked before for a long time.... Instead of the real hostname, that matches the SNI Value in the https request, we configured only the second level domains like this

    *.test.com and test.com

    As I said, this worked fine until we had to update the certificate yesterday... But I think the configuration was not totally correct... It was based of a wrong thought in relation to the wildcard certificate.

    Regards

    Sebastian

Children
No Data
Unfiltered HTML