Error message at when checking out with Paypal after upgrade

@apothecarytravels No, no problems at all so far … knock on wood. I don’t know much about this stuff and I know we had encryption at some point (before the WP 4.4 upgrade) so I am not really sure why all of a sudden we had to buy a SSL Certificate or what Comodo does that works over what we had before the upgrade. Maybe you have to upgrade your certificates or switch them? I’d ask BlueHost. Use their live chat. Much quicker than email. Glad you like Rajibul Islam. I’m on the East Coast and he’s 11 hours ahead so working with him works quite well with me – either early morning or in the evening. Very nice guy. He makes good recommendations for WP plugins too. I wish I could be more helpful. I’m so out of my league on all of this.

@apothecarytravels – I’ve managed to get Paypal working again on my site by following the instructions in Marcelo Pedra’s reply at:

https://www.ads-software.com/support/topic/cant-update-wordpress-ssl-certificate-problem-error14090086s

It looks as though changes to that certificate file in v4.4 caused the problem. Hopefully, they will be reverted in the next WordPress update.

@apothecarytravels @minielli @markwarner5 @jaswsinc

WordPress v4.4 removed several SSL certificates from its trust store and that caused issues with servers running a version of OpenSSL less than v1.01g. The issue will be fixed in the next WordPress update (v4.4.1) by adding those removed certificates back into the trust store: https://core.trac.www.ads-software.com/ticket/34935

Ok dudes. Thanks for all the extremely helpful links and comments. I know what to do now….fix this issue and then hire a developer to take care of these headaches for me ??

@raamdev – So it sounds like what you are saying is that I just spent $275 for a SSL certificate due to the WP 4.4 update because the update made our original SSL certificate unusable? And that you are going to put back those unusable SSL certificates in the next update?

Wow.

Good luck @apothecarytravels and to everyone else.

@minielli This was not an s2Member issue at all. This was a WordPress issue. We (makers of the s2Member plugin) are not doing anything to fix this problem. I’m sorry that you spent money before the root cause of the issue was discovered here, but there is nothing that s2Member could have done to avoid this issue: WordPress released an update (WP 4.4) that caused this issue and now WordPress is releasing another update (WP 4.4.1, coming soon) that should resolve it.

s2Member is not the only plugin affected by this issue–there are many other WordPress plugins that had problems with the latest WordPress update.