My BruteProtect Dashboard not available

Yes, you can use Jetpack monitoring in lieu of BruteProtect’s. Thanks for sending the debug info, too.

Jamil,

Thanks for the report. It looks like when our API tries to connect to your site, we get
Curl Error 35: Cannot communicate securely with peer: no common encryption algorithm(s).

Could you talk to your hosting provider / server administrator and see if they know why incoming CURL requests would result in that error?

Thanks, and sorry for the frustration.

I’m currently working on better error handling, so anyone who is experiencing a connection error, you’ll see a more meaningful message.

Thanks for your patience everyone.

I’m getting this error because I’m using a self-signed certificate. I did some troubleshooting, then submitted a support request at Bruteprotect, but never heard back.

My setup:
Site hosted at DreamHost with their free self-signed certificate.
I’m using Cloudflare, also with an SSL certificate, but it’s not self-signed, so no warnings when using a browser.

However, since Bruteprotect is calling curl locally, my DreamHost site is local, so it’s bypassing Cloudflare.

If I could find a way to get Curl to ignore SSL errors in this instance, I think I’d be set.

I stand corrected. Full cURL verbosity shows that it’s attempting to reach the same IP address (Cloudflare) whether from the DreamHost command line or my Mac’s command line.

It would appear it’s an issue with cURL at DreamHost. I’ve submitted a support request.

Thanks sdayman.

Keep us posted. We are seeing this issue on a few other sites as well.

DreamHost support responded. They’re running an older version of cURL on Debian.

They’re in the process up upgrading servers to Ubuntu which should also fix cURL. They expect to get to mine this month, so I’ll post back later.

Thanks!

Jamil,

Thanks for the report. It looks like when our API tries to connect to your site, we get
Curl Error 35: Cannot communicate securely with peer: no common encryption algorithm(s).

Could you talk to your hosting provider / server administrator and see if they know why incoming CURL requests would result in that error?

Thanks, and sorry for the frustration.

I’m currently working on better error handling, so anyone who is experiencing a connection error, you’ll see a more meaningful message.

Thanks for your patience everyone.

I have contacted Hosting support and they asked about IP to track
“we would need the IP address for the incoming Curl requests.”

Can you send me IP please ?

Good news and bad news…
DreamHost upgraded the server, and cURL now works. My “Simple Lightbox” plugin now works via an internal cURL call.
The bad news is that BruteProtect still doesn’t work. Now that I read the posts more closely, I realize it’s *your* cURL that isn’t working.

Thanks for the reports guys. We are working to get our API servers up-to-date with cURL.
We’ll keep you posted.

Jamil, the IP range for our API can be found here:
https://forums.aws.amazon.com/ann.jspa?annID=1701

We are in the US East (Northern Virginia), range. Be forewarned that range can change without notice. It may be best if you and your hosting company can come up with a better solution.

I wanted to clarify my post for people scanning this thread…

The cURL issue doesn’t stop BruteProtect from working – it’s still doing its job. The cURL issue stops the fancy my.bruteprotect.com dashboard from tying all my sites together in one display.

The devs realized that is most likely the issue and we’re currently looking into the update. Thanks for the help on this one!