Safepay Cloudflare captcha loop

Hello,

I have just run into a brick wall trying to use Safepay on a site protected by Cloudflare. I end up in what looks like an infinite loop on a captcha. The message is :

***<protected site name>

Verify you are human by completing the action below :

***

With the usual tick box underneath.

If I tick it, then after a few seconds, it pops up again. This repeats at least 4 or 5 times. The page footer has Cloudflare branding, so I assume it's coming from them.

I note there is another recent forum thread saying that a Cloudflare associated issue has just been fixed in Safepay. The symptoms are different, but I was wondering if the underlying cause was the same, so the same fix would resolve this as well ? Or are the root causes likely to be different ?

Thanks.

Find more posts tagged with

safepay

cloudflare.com

Accepted answers

All comments

Scott

@camarie since Paisley227 knows about the other thread, it doesn't seem to be addressing their issue. Could you look into this for them, please?

Kind regards.

camarie

@Scott I'm afraid I don't understand what "to be addressing the issue" means.

Scott

https://community.bitdefender.com/en/discussion/comment/351840#Comment_351840

I was my way of wording the below from his post. Sorry, maybe poor choice of words on my part :)

The symptoms are different, but I was wondering if the underlying cause was the same….

Paisley227

All, apologies for any confusion caused by my comments.

What I was trying to say was that I know a new version of Safepay was on its way, which addressed a different issue related to Cloudflare. I was wondering if anyone knew if it was likely to help with the problem I saw, or if what I was encountering a different underlying issue. I'm in no position to know, but I wondered if the person who worked on this had got to the point of understanding enough of Cloudflare's behaviour to know if what I saw was related to the same underlying cause.

Hope that makes things clearer.

camarie

Yes, I have tested multiple websites with the CLoudflare 600010 error, and the fix was the same for all of them.

Apparently, if a browser does not support Notifications API (?!) it is considered some sort of automated agent. Enabling (against my will) this solves the issue.

camarie

Followup: yes, the infinite loop, errors 600010, 100040 were all caused by the same problem. At least after our tests with the updated unreleased version, all the websites reported to me exhibiting the issue are all functioning (CAPTCHA/Cloudflare error) after the fix. I cannot, obviously, complete the full test without a valid bank account, but from what I isolated as differences between "it works" and "it doesn't" mainly was the Notification API enabling that gets the bug out of the way.

Paisley227

All,

Thanks - that's good to know.

The transaction I'm trying to do is time-sensitive, and needs to be completed in the next couple of days. From the comments in the other thread, I was hoping that the fix would be released to the public soon enough to be helpful to me. Was I perhaps being too optimistic ?

Regardless of that, I really appreciate the speed and responsiveness on this thread. Kudos to all involved.

camarie

I'm afraid we won't release the next update in the next couple of days. Although it pains me to say this, I would recommend to do what's best for you and use this time another browser with Incognito mode, at least until we manage to release the fix.