Even if you don't notice your connection dropping, your computer and Olark may be unable to communicate with each for a brief period.

Symptoms of this may include undelivered messages, being set to "away", or an incorrect status being shown to visitors. This can be caused by a number of things. In order of easiest to least fun to troubleshoot, they are: browser, network (either yours or the network on your visitor's end) and computer.

If you or your visitor lose connection for just a few seconds, our system will attempt to resend until the network connection is re-established. But, if you lose communication with the server for 2 minutes, the chat console will automatically attempt to reconnect. When this happens successfully, you'll see a message and you can continue to chat as normal.

During the 2 minutes before a reconnect attempt, operator messages may appear to be grayed out. While they remain gray, it means that they have not been sent successfully yet, but will try again automatically.

You may see the chat console appear to be "reconnecting" for a long time, or the dark "away" status background is all that appears. In this case, reload your browser tab/window.

(If you are having trouble seeing the chatbox on your website, or on someone else's website, try this guide for troubleshooting tips.)

Troubleshooting

How can you know where the issue lies? Here are some common debugging steps you can try (these work for any number of web-based issues for other sites and services, feel free to try these tips out when you run into other problems online too):

  1. Browsers:

    • Try an incognito (Chrome) or private (Firefox) session of the browser you're currently trying in. If this works, you've already narrowed down your solution to your cache/ cookies or a browser extension.
    • Try a different browser. This helps us know if there is an issue with a particular browser version or installed plugins/extensions.
    • If steps a or b work, try clearing your cache and cookies in the affected browser and then retry.
    • If you use any of the extensions below or similar ones, try switching the extension off and see if the problem resolves. Extensions and third party apps which can interfere with the Olark chat console can include, but are not limited to:
      • Ghostery
      • Adblock Plus
      • Pop-up Blocker Pro
      • Easyprivacy list
      • Covenant Eyes
      • Avira Browser Safety
      • Cloudflare Rocket loader
  2. Network:

    • Connect to a different network. Where possible, this helps us figure out if the issue is localized to a specific network, particularly in cases where several operators in the same location are disconnected at the same time.
    • If you have a wired and a wireless connection in your workplace and neither of them seem to be working, if you have a laptop or are very determined, bring your computer to a non-work connection (your home or a coffee shop) and see if you are experiencing the same issues.
  3. Check the Olark status page for reports of system-wide outages. You can sign up for proactive email and SMS notifications. If this is the case, we're very sorry.

  4. Find out if you have a firewall enabled. Firewalls can be installed both on your computer and for the network itself.

  5. Olark uses the standard ports, 80 and 443. You may want to check that your firewall is permitting websockets traffic. It travels over SSL (port 443) but can sometimes be treated differently by some set ups. If you visit this site, you can check your websockets connection and get a result ID which you can include in any support request.

  6. Ask your IT team if there have been logs of network interruptions at the time you experienced an issue.

    • If you are behind a proxy connection you might wish to try the following:
    • Try whitelisting our ip address ( 208.117.48.32) and our domain at olark.com.
    • If you want to be extra specific, you can also include our web opconsole at chat.olark.com or just simply *.olark.com

Next steps

If this happens frequently, be sure to create a support ticket, letting us know when it happens and links to Transcripts that were affected.