• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 124604, created on Feb 25, 2015, last review on Oct 20, 2015

  • Applies to:
  • Business Automation

Situation

Starting from February 26th 2015 eNom production servers stoped receiving connections over TLS 1.0 protocol. Only TLS 1.2 is supported.

Please upgrade to the following BA versions/install the following hotfixes:

  • BA 5.4.x version: hotfix 124688
  • BA 5.5.x version: hotfix 124560
  • BA 6.0.1 version: hotfix 124689
  • BA 6.0.3 and higher: TLS 1.2 support was added

Call to action

The following workaround is suggested:

Via BA UI change value of Host field at eNom plugins configuration settings to legacyreseller.enom.com

For BA 5.5 and 6.0:

  • eNom Domain plugin should be configured in the following way:

    1. Open in BA provider control panel:

      Home > System > Settings > Domains > eNom Registrar > Configuration tab

    2. Change Host field value to legacyreseller.enom.com

    3. After saving - check connection.
  • eNom Certificate plugin should be configured in the following way:

    1. Open in BA provider control panel:

      Home > System > Settings > Certificates > eNom Registrar > General Configuration tab

    2. Change Host field value to legacyreseller.enom.com

    3. After saving - check connection

For BA 5.4:

  • eNom Domain plugin should be configured in the following way:

    1. Open in BA provider control panel:

      Home > External Systems Director > Domain Manager > Registrars > Registrar Enom > Configuration

    2. Change Host field value to legacyreseller.enom.com

    3. After saving - check connection.
  • eNom Certificate plugin should be configured in the following way:

    1. Open in BA provider control panel:

      Home > External Systems Director > Certificate Manager > Plug-ins > Plug-in EnomSSL

    2. Change Host field value to legacyreseller.enom.com

    3. After saving - check connection

If some issue appears after applying this procedure or you need assistance in applying this workaround, please do not hesitate to contact Parallels Technical Support with:

http://sp.parallels.com/hcap/support/request/

Search Words

Packet is empty

Connection failed. Hide details [XMLPacket] Packet is empty

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF