Hi @passegua,
WangGuard 1.6 is using port 443 (SSL) by default. If you cannot open that port, go to WangGuard Configuration And look if “Connect to WangGuard API using SSL / TLS”. is unmarked and Save Options.
Then, try if your website is connecting to WangGuard again.
kind regards
José Conti
Hi again @passegua,
Please, update to 1.6.1 and if you have connectivity problems, mark disable secure connection to WangGuard API in WangGuard configuration.
Kind regards
José Conti
Have you considered an option to leave SSL enabled but to not verify the certificate? I am running CentOS 5 and have found that was the fix for some other issues I was having with other plugins (I was able to use a filter since it was using WP_Http() – http://justinsilver.com/technology/wordpress/admin-columns-pro-ssl-upgrade-fix/).
Thanks!
Hi @doublesharp, I can take a look, but i don’t like the idea, because if WangGuard plugin don’t verify the certificate, many people can think that there is something wrong with the certificate or the plugin. And there is a very big hole without verification, if someone hack your server and change the hosts (for example), the certificate will works, so you can be sending the emails for verification to a hackers instead to us.
Read this post, maybe is the solution for your problem.
http://snippets.webaware.com.au/howto/stop-turning-off-curlopt_ssl_verifypeer-and-fix-your-php-config/
Kind regards
José Conti
Awesome, thanks for that link… I tried to figure this out forever and it never occurred to me that curl wasn’t picking up the update cacerts.pem. Once I added it to my php.ini file SSL is working as expected, thanks again!
Actually, I take that back. Even with the updated cacerts.pem specified in php.ini I still cannot connect unless I disable SSL entirely. I have root access to the server running CentOS 5.11 if you have any other suggestions. It would be great to not have to disable SSL entirely, but if I don’t I can’t connect to the WangGuard API IP address.
Because the latest SSL bugs, I’ve disabled some SSL protocols, maybe this is the problem.
I will update you.
Yeah… I suspect it is trying to fall back to SSLv3. The real solution is for me to upgrade to CentOS 6. Now all I have to do is find some free time 🙂
