DNSOnly - Failed update

[HollyRidge]

DNSOnly server will not update to 11.60.0.3. It fails with the following error...

[2016-10-11 22:55:24 -0400] W NOTE: A system upgrade was not possible due to the following blockers:
[2016-10-11 22:55:24 -0400] W [FATAL] - Your system does not support [output,abbr,SNI,Server Name Indication], which [asis,cPanel & WHM] requires in order to upgrade to the next version.

I have tried 2 different DNSOnly servers with the same result. Full cPanel servers update without issue.

 

[cPanelKenneth]

Hello,

What is the operating system version in use on these servers?

 

[HollyRidge]

Hello,

What is the operating system version in use on these servers?

CentOS 6.8 and CentOS 7.2

 

[cPanelKenneth]

CentOS 6.8 and CentOS 7.2

Thank you for that information. I spotted the bug (we rely upon an installed webserver to report whether SNI is supported) and filed a bug report: CPANEL-9221. Right now I don't have any work arounds to suggest. We'll get this fixed.

 

[HollyRidge]

Thanks Kenneth. I submitted a ticket earlier too (#7777067) but thought I would try here as well to see if anyone else was having the issue.

 

[cPanelKenneth]

Thanks Kenneth. I submitted a ticket earlier too (#7777067) but thought I would try here as well to see if anyone else was having the issue.

Excellent! I associated your ticket with the defect report so the analysts are aware of the problem and be able to track it.

 

[HollyRidge]

Thank you!

 

[cPanelKenneth]

Thank you!

You're welcome. We have a fix in review right now. Assuming all goes well we should get it out today.

 

[cPanelMichael]

Hello @HollyRidge,

cPanel version 60.0.4 is now published to the "Current" build tier and includes the resolution for CPANEL-9221:

Fixed case CPANEL-9221: Exempt DNSONLY from the SNI blocker.

Let us know if you encounter any additional issues.

Thanks!

 

[HollyRidge]

You're welcome. We have a fix in review right now. Assuming all goes well we should get it out today.

Thank you! I have verified that this appears to be fixed now.