David Hamel

Clint,

I wanted to let you know that we have figured out what the issue is with this and it seems to be activating correctly now.

Essentially we had a slow-process kill implemented in PHP. the plugin was exceeding the time allowed on the slow process and it kept killing it. We didn’t find it until we added additional logging to php when we were digging deeper.

It seems to be working now.

Thanks for your help.

Clint,

Thanks for looking into it.

In further digging around in the logs we have found the following items that relate to the issue, but don’t seem to help us narrow down where the problem might be:

From our ssl_request_log
/wp-admin/network/plugins.php?action=activate&plugin=delete-me%2Fdelete-me.php&plugin_status=all&paged=1&s&_wpnonce=6a5847dc53 HTTP/1.1″ –
/wp-admin/network/plugins.php?error=true&plugin=delete-me%2Fdelete-me.php&_error_nonce=59f72ad036 HTTP/1.1″ 380286
/wp-admin/plugins.php?action=error_scrape&plugin=delete-me%2Fdelete-me.php&_wpnonce=59f72ad036 HTTP/1.1″ –

With some similar entries in our access_logs

We believe it is a resource issue and are still running more tests to try to figure out where it might be.

If you have any suggestions, let us know.

Regards
Dave

Well, we’ve finally had success, and it wasn’t using the SAN cert.

We used ssllabs.com to evaluate the system and altered both the cipher suite and protocols. the change allows all versions of TLS with an extended set of suites.

thanks for the assistance and comments.

Thanks for the thoughts.

We ran through what you suggested and the server is showing the successful connection at TLSv1.2 with the certificate and other information including cert chain, cipher, keys and session ticket info.

What we did notice is that the certificate was issued with only the wordpress DNS name. We are reissuing it as a SAN cert with both the server FQDN and wordpress DNS names included. I’m not confident that will correct the situation, but we’ll give it a try.

Any other suggestions or thoughts?

I truly appreciate your feedback.

Regards
Dave

Thanks for the follow-up. I have solved my issue also, and although it relates to your findings it is a bit different.

using the command that you indicate i get the CURL error also, however, I’m not on a hosted system and my system does have access to the CA.

What I am finding the issue is on my system is our security services have required us to set the SSL Version to TLSv1.2 ONLY. System won’t accept any connections less. whenever I change the system to accept just SSLv2 or 3, everything works fine. Once I move it to TLSv1.2 I get a variety of SSL connection errors on everything from Network upgrades to RSS Feeds/Cron jobs.

I have been looking for a way to force PHP/CURL to use TLSv1.2 but have not found a way yet.

Any suggestions out there?

Good afternoon,

Unfortunately, no.

We originally had only the admin component set for SSL. We’ve since migrated the entire system to ssl and still get the error.

I’ve gotten around the issue by upgrading the sites individually when i get the error messages during network upgrades.

Sorry, wish I had a better answer.

David

an update on this issue.

I finally found the issue – it was some plugins we developed that had closing php tags and white space in the files.

After I removed the closing tag and removed white space everything is working correctly now.

yes thanks