Web widget is invisible on localhost | Community
Skip to main content

Web widget is invisible on localhost

  • June 15, 2021
  • 3 replies
  • 0 views
S

When I try to open page with web widget on localhost it stays invisible.

I can see iframe with right code

<iframe title="Opens a widget where you can find more information" id="launcher"

and the page has full API, for example I can call

zE('webWidget', 'open');

but it doesn't have any effect or error.

Outside localhost everything works fine

      3 replies

      Tipene
      • Tipene
      • July 21, 2021

      Hi Sergey,

      This issue can often be caused by the specific domain (localhost in this case) not being on the "allowlist". If you or an administrator for your Zendesk instance head to Admin > Channels/Widget > Security settings > Configure , you'll be able to enter the required domain which should resolve the issue.

      Feel free to follow up if you have any questions!

      Tipene

        Tal19
        • Tal19
        • September 14, 2022

        Keep getting banned, even after setting localhost in my allowlist under "Web Widget (Classic) security settings" (at https://my-company-help.zendesk.com/admin/channels/classic/web-widget).

        Refreshed all caches. And in fact I could see I'm reaching the updated configuration, because I'm getting the latest appearance (changed colors, etc for indication). And it takes a second or two to get the ban. I even manage to open the chat and start writing, then it disappears and I see the console message:

        Zendesk Chat Web SDK: Error: init: Visitor has been banned

        And ze.activate() won't open it at that point.

        At the allowlist setting - only the keyword localhost is accepted. No port, wildcards, quotes, dots,  colon, nothing. Just: localhost

        Anything else I can do?

        Thanks!

        Dave12
        • Dave12
        • September 14, 2022
        Hi Tal, it looks like one of our support agents has responded to your inquiry - looks like they're asking for some additional information. If you can go back to our messaging window, you should be able to continue your conversation there.
        Terms & ConditionsCookie settingsAccessibility statement