We host a number of servers for customers, sharing a public IP range. We have been having intermittent problems with customers receiving ReCAPTCHA challenges in a loop. They are presented with an endless stream of images and therefore can't reach the website they need. This problem is particularly frequent when using a particular piece of software which uses the CefSharp framework as an integrated web browser. We believe that our IP range has a poor reputation with ReCAPTCHA, perhaps due to the high volume of users sharing the IP range. Is there anything we can do about this?
ReCAPTCHA IP reputation problem
+1
+7Hello,
are your servers sharing an IP range, or are your customers sharing an IP range?
if you trust your users' IP addresses, it is now possible to configure an IP address allowlist for your reCAPTCHA key. You can learn more from the documentation here: https://cloud.google.com/recaptcha/docs/allowlist-ip
+1Hi Faube, thanks for this. Our servers share an IP range, with one customer using each server and several servers using each IP address. We do not control the website in question, but we are forwarding this info to the website owner (Sage) along with our IP range. We suspect that the volume of traffic from each IP address to ReCAPTCHA protected websites combined with the fact that the website is being accessed through CefSharp (embedded in the Sage 50 Accounts software) is making the traffic look suspicious to ReCAPTCHA.
+1Hi Faube, thanks for this. Our servers share an IP range, with one customer using each server and several servers using each IP address. We do not control the website in question, but we are forwarding this info to the website owner (Sage) along with our IP range. We suspect that the volume of traffic from each IP address to ReCAPTCHA-protected websites, combined with the fact that the website is being accessed through CefSharp (embedded in the Sage 50 Accounts software), is making the traffic look suspicious to ReCAPTCHA.
I also have the same issue, and the fact that the CAPTCHA challenges become an endless loop when many customers are sharing the same public IP range makes the reputation theory seem worth investigating. If reCAPTCHA sees a large number of unrelated users coming from the same addresses, it may have difficulty distinguishing normal traffic from automated or unusual activity, especially when the requests are being generated through an embedded browser such as CefSharp. What I find particularly interesting is that the problem seems more frequent with that specific software rather than simply affecting every customer using a normal browser. That could mean there are additional browser fingerprint, JavaScript, cookie, or session characteristics involved alongside the shared IP reputation. I would be interested to know whether the same customers experience the loop when accessing the same websites through Chrome or another standard browser from the identical public IP.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.