WordPress Let's Encrypt Plugin - Certificate Generated but Not Associated with Listener

I’m using Media Temple for hosting a Wordpress managed site. I’ve installed the Letsencrypt Wordpress plugin and successfully generated a certificate. So far so good, but what now? I cannot access the site with the secure connection:

domain: helpdeskrealty.com

In Firefox:
Secure Connection Failed

An error occurred during a connection to helpdeskrealty.com. Cannot communicate securely with peer: no common encryption algorithm(s). Error code: SSL_ERROR_NO_CYPHER_OVERLAP

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

In Chrome:
This site can’t provide a secure connection

helpdeskrealty.com uses an unsupported protocol.
Unsupported protocol
The client and server don’t support a common SSL protocol version or cipher suite.

Hi @helpdeskrealty,

It looks like you have a rather significant web server misconfiguration of some sort. Often this kind of problem is related to the ciphersuite configuration in your web server, but I think here the problem is potentially lower-level.

Do you have administrative access to see and modify your web server configuration, or is this a shared hosting situation where you are not the system administrator? In the former case, I’d like to see your server configuration files; in the latter case, I think you’ll need to ask your hosting provider’s support to help debug this problem.

Understood. I’ll have to get with the host to troubleshoot. Thank you.

Just a note for anyone’s reference. MediaTemple, while I have greatly enjoyed their hosting and customer service, do not support 3rd party certificates. They only support their own and GoDaddy’s.

hi @helpdeskrealty

Looks like the port is open but no certificates are associated with the listener (which is probably due to what you were talking above)

Looks like the WordPress Plugin generated the Certificates you requested: https://crt.sh/?q=helpdeskrealty.com


Using a WordPress plugin is going to be tricky for setting SSL.

  1. WordPress runs under Apache, so permissions of running Apache will likely be unable to correctly effect all SSL files, which will likely cause subtle errors.

Refer to ssh + logs to determine if plugin has actually done it’s work correctly + all files/permissions are correct.

  1. Apache will have to be bounced (stop/restart) or reloaded to pull in SSL setup.

Refer to ssh + logs to determine if this has been done + if all’s well.

  1. apachectl -t is your friend. I always run this after doing a new SSL setup just to make sure all’s well before I do my reload.
1 Like

WordPress users can try this step.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.