All,
We’ve experienced captcha issues on our site twice in the last 30 days, once before Thanksgiving and again, today. Hopefully, this is limited to our site and not others. We have a ticket in with support. It might be worth spot checking to see things are still working on your sites.
It’s after hours on the east coast. Support was able to resolve the issue previously for us. We are normally on captcha2 and support temporarily put on us captcha3 over Thanksgiving. For today, we could only get math working to resolve the issue. -Dave
We have had this issue at least twice in the last couple of weeks. If there are two of us, I expect there are other groups having this issue as well. Hopefully, Ethos will get it resolved permanently. Maybe they can provide an update to everyone.
What you are describing is exactly what we experienced too - at the time they had mentioned moving us to the math problem instead but when I inquired they said no issues with Captcha 3 so they did that. If this is going to be ongoing I’d rather move to something else other than Captcha?
In November and again yesterday, users experienced CAPTCHA issues with forms within EthosCE. These issues affected all customers utilizing CAPTCHA on their forms. Currently, we are investigating the root cause but have not yet determined the specific reason for the disruption or the resolution, as no changes were made to our implementation during this period. We have initiated support tickets with Google to help address the issue and have implemented advanced logging on our account to assist in further diagnostics. As we continue to investigate this issue, we will be providing updates to the community.
As a reminder, if this issue happens again and order to prevent issues creating accounts, site admins can temporarily change the Captcha settings here /admin/config/people/captcha. If you have any additional questions, please open a support ticket and we can help get those answered.
What are we able to/should we do? We were switched to 3 last time, so please provide/point me to instructions for what we can do ourselves, and how this might affect things moving forward.
We are on Captcha 3. I was able to successfully create a new account using Chrome this morning and passed Captcha. I am running the following version: 131.0.6778.140 (Official Build) (64-bit).
Not sure this is any help but thought it was worth posting.
When there is a system wide or product issue, we get notices for eventscribe and elevate. I think I’ve seen a couple for EthosCE here and there. It would be helpful to EthosCE customers to receive additional notices via that service and also Cadmium Status. There might be other opportunities.
For future (if not already doing this), it would streamline things and benefit all if Cadmium can share issues as uncovered.
I would prefer not having to put this in the community and also not having to reach out to other customers to verify or validate. We are all working to benefit our learners and staff. Thank you to support for resolving my issue this morning and investigating. Reducing the time to acknowledge a problem (including third party ones) will better serve Cadmium customers and our customers. Thanks! -Dave
@JAM on that page, you can change your default Captcha choices for all forms. A great option is to change temporarily to the Math option to prevent any issues with end users continuing to create accounts and submit forms.
Thank you for your feedback on the status page. We do have a incident response policy in place which helps to define when we post to the Cadmium Status Page. It is intended to be for major service interruptions, scheduled maintenance, core operational issues. While this was a global issue to EthosCE customers, its a pretty small subsect of customers who use this, not all of which are on core forms such as a create account page. I think the better place for this messaging is on our ticketing system and I will work with our support team to come up with a process for these types of announcements to get posted there in an expedited fashion in the event of future issues like this one.
I’m happy to share that we’ve resolved the Captcha issue! Thanks to our additional logging, we were able to pinpoint a rate limiting error as the root cause of the performance problems. The rate limit was based on account levels, but we’ve taken action by upgrading our account to ensure we won’t hit this rate limit moving forward. This should resolve the issue and improve performance going forward.
