Chat widget error

Hello All,

the customer faced an issue after he deployed the Chat widget on the website ( it's version 2 )
and when I start the chat, I see this error There was an issue starting your chat session. Please verify your connection and that you submitted all required information properly, then try again.
However, when I tested the widget ( without Deploy it ) it works fine.

Please find the deployed chat on the website :Welcome to Zamil Industrial
and my Chatwidget that if you tested it will work:

Img Width Attribute

Start Chat

How I can solve this issue?

Thanks in advance!

I don't know why I can't post my configuration.
any idea?

The error is being caused by the request to start the chat being made to https://protect-eu.mimecast.com/s/TvAdCEPMof394ApupaMLO?domain=api.mypurecloud.de/api/v2/webchat/guest/conversations. I can't find any reason that the request should be routed through mimecast. If this isn't something on your end injecting mimecast into it, please open a case with Geneys Cloud Care to investigate further.

Code must be in code blocks or it get scrubbed from the post. More info about discourse markdown can be found here: Post format reference documentation - faq - Discourse Meta

ETA: that link to discourse markdown is kinda low quality. Use triple backticks before and after your code block (on their own line) to make a code fence.

So it's probably from the customer end as I tried the same widget and it's working for me


and as they routed through Mimecast.

Thanks, A lot for your help!

I just noticed that the source code of the deployed page differs from the code you posted in your original post in that it's adding mimecast to the config. This is definitely what's causing the problem. Looks like the customer needs to do some whitelisting in their deployment scripts. :slight_smile:

From the config passed to window._genesys when inspecting the source:

"dataURL": "https://protect-eu.mimecast.com/s/TvAdCEPMof394ApupaMLO?domain=api.mypurecloud.de",

1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.