SSL/TLS handshake fails only for one free subdomain on the same hosting IP

Hosting Support
1

Website URL

https://althea.synergize.co/

Error Message

Hello,

I’m having an SSL/TLS issue with one of my free subdomains:

althea . synergize . co

The domain resolves correctly to:

185.27.134.150

HTTP works normally, but HTTPS fails with:

ERR_SSL_PROTOCOL_ERROR

Windows curl output:
Trying 185.27.134.150:443…
Connected to althea . synergize . co (185.27.134.150) port 443
ALPN: offers http/1.1

schannel: next InitializeSecurityContext failed:
SEC_E_ILLEGAL_MESSAGE (0x80090326)

curl: (35) schannel: next InitializeSecurityContext failed:
SEC_E_ILLEGAL_MESSAGE

SSL Labs also fails with:
Assessment failed: Failed to communicate with the secure server
The important detail is that another free subdomain on the same hosting account and the same IP address works correctly over HTTPS:

helios2 . page . gd

Both resolve to:

185.27.134.150

For helios2 . page . gd, the TLS handshake succeeds:
Connected to helios2 . page . gd (185.27.134.150) port 443
ALPN: server accepted http/1.1
using HTTP/1.1

while for althea . synergize . co the TLS handshake fails before any HTTP request can be processed.

The SSL Certificates page says:
Custom SSL certificates are no longer supported for free subdomains.
All free subdomains have SSL by default.

So I cannot reinstall or request a new certificate manually.

Could you please check the system SSL / SNI configuration for althea . synergize . co?

It appears to be a domain-specific SSL mapping issue rather than a general server/IP outage.

Thank you.

2

Welcome to the forum.

First thing to note is that curl is never going to work. The servers are set up to only respond to browser requests.

As for the problem is ssl, there were some problems the other day so maybe it’s just a leftover taking longer to resolve.

Hopefully admin can shed some light on it when he’s next on

3

Thanks. Yes, I also noticed the recent SSL issues.
What seems unusual here is that another free subdomain on the same account and the same IP currently works over HTTPS, while althea . synergize . co still gives ERR_SSL_PROTOCOL_ERROR in normal browsers.
I’ll wait for an admin to check it.

4

I just checked your site and it’s working fine from here, using both HTTP and HTTPS. SSLShopper’s SSL Checker also says that the certificate is good.

The currently installed certificate for synergize.co was issued yesterday, and certificate renewals were responsible for the bigger outage we had on Monday.

So it’s possible the issues are related, but it’s strange that you were getting it today while the certificate was already renewed. But regardless of what happened, it seems to be resolved now.

5

Thank you for checking.
I can confirm that HTTPS is working normally again from my side as well.

The issue lasted for a while after the certificate renewal, so it may indeed have been related to the recent SSL renewal problems.

Thanks again for your help and for looking into it.