Search Engine: Elastic

Article ID: 130581, created on Apr 5, 2017, last review on Apr 5, 2017

  • Applies to:
  • Operations Automation 7.0


When used in par with wildcard subdomain on shared IP of NG server (cluster or standalone), wildcard certificate is not used for SSL connections. Default cert is used instead.

Wildcard domains hosted on exclusive IP addresses are not affected.


In case of shared IP, the record like ssl-by-hostname:*.example.local is propagated to Redis DB which is a source of webspace information for Apache NG. It interprets it as a separate domain, not like wildcard and does not apply certificate. This issue was passed to OA Engineering team for further investigation as request POA-110827.


Currently there is no workaround for the issue, except of switching main (one for which wildcard domain is created) domain to exclusive IP.

Please contact your technical manager or a member of Pooled Technical Associates team in order to clarify status of POA-110827.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF