Visit Freshworks.com Visit Freshworks
Solved

CAPTCHA Fails on Widget

  • 12 December 2021
  • 6 replies
  • 188 views
jwicker
Rank
Userlevel 1
Badge

We have the widget on our website with the CAPTCHA required to contact us. The CAPTCHA recently started having problems late last week and our customers were not able to contact us. We sent test emails and received the same error message.

No matter what you do, you cannot get around the CAPTCHA as it always states that it fails. So I had to remove the CAPTCHA requirement for the time being. I raised a ticket regarding this matter on Wednesday but it seems that it is still being worked on. 

Is anyone else experiencing this issue and is a fix in progress?

icon

Best answer by hemanth.ramya 27 December 2021, 13:29

View original

6 replies

mojoauth
Rank

We are still facing the same issue in our freshdesk portal.

Couple of our customers reported this from US and Pakistan. For now we have disabled the Captcha from our account.

 

hemanth.ramya
Userlevel 5
Badge +9

The acknowledged issue has been permanently fixed, @jwicker. You should no longer face any trouble with CAPTCHA in help widget. Cheers! :)  

Ramya, Freshworks Community
hemanth.ramya
Userlevel 5
Badge +9

Thanks for sharing the update here, @jwicker. 

Can you toggle on your CAPTCHA again and check if the help widget ticket creation works as expected now? Looking forward to hearing your insights. Cheers! 

Ramya, Freshworks Community
jwicker
Rank
Userlevel 1
Badge

I was informed by FreshDesk Support to leave the CAPTCHA off for now as the problem is awaiting a fix from the developer

Keer
Rank
Userlevel 5
Badge +12

Hello @jwicker, apologies for not getting back to you sooner on this. We did face a temporary glitch in CAPTCHA loading. I am glad it’s working fine for you. Kindly let us know if you are facing any further issues and we would be happy to help. Have a good day! 

Cheers, Keer, Freshworks Community Team
jwicker
Rank
Userlevel 1
Badge

Just tested this again today and it seems to be working again, but I do not know the initial cause of the problem.

Reply


Terms of UseCookie settings