Is anyone else having issues with the anti-bot validation?
Randomly this morning, anyone logging into the front end gets " Error Sorry, the anti-bot validation has failed. Please try again."
I have tried myself, and even if I type the incorrect password intentionally, it still says this instead of password incorrect. Nothing has been installed/changed/modified on the website, which makes me think it could be a Google issue?
When I click the box for validation, it does show the green tick suggesting it is happy I’m not a bot but still fails. It also doesn’t show a failed login attempt in the admin panel. I’ve disabled the reCAPTCHA for login forms temporarily so customers can login but this isn’t ideal of course.
We’ve also noticed PDFs are not being generated when we click on “Print invoice (PDF)” or “Print dispatch note (PDF)”. Is CS-Cart causing this issue? We are having to print the invoice then select the “save as PDF” option as the printer as a workaround
We are now unable to take any payments, it keeps saying “Transaction was canceled by the customer”. This also happens if a customer tries to place the order online. Is this is a CS-Cart issue? It’s strange we are having so many issues all of a sudden linked to the website.
The issues I was having seemed to have resolved themself after 4 days, couldn’t work out what started the issue or fixed it as I didn’t change or modify anything, neither did my hosting provider
Same problem here too. Losing plenty of money whilst this is happening. Firstly a customer was getting a "Error. Sorry, the anti-bot validation has failed. If you’re seeing this message, please contact us and let us know about it.
This I read could be something in regards Google Captcha. So I removed the Captcha from Login.
After extensive testing, I worked out that the IP addresses were not resolving. I could ping IP addresses from the server but not domain names. My hosting provider checked the /etc/resolv.conf file and noticed it only had “127.0.0.1” instead of the usual details. They have re-added the Google resolvers and this fixed the issue instantly.