WebSockets Configuration Troubleshooting

WebSockets have been a long time coming. They allow for truly live content to be displayed on web pages as if they were dynamic applications. Grammarly’s server accepts only these kinds of connections, allowing clients to be embedded within the website to connect to Grammarly.

However, the technology is new and not fully matured; there have been some security issues with WebSockets in the past, causing browsers to temporarily block them. Additionally, there are several things which prevent or block WebSockets entirely:

  • Older browsers
  • Some download managers
  • Some mobile carriers
  • Some firewalls
  • Some antivirus software
  • Some Internet service providers
  • Strict configurations on routers

WebSockets may be totally blocked, in which case you won't be able to use them with your browser.

To test whether you have WebSockets connections in your browser, go to https://app.grammarly.com/diagnostic-test

Does anything in your test results say Failed? That might be the root of the problem. But no worries: just copy/paste the results into your help desk request and submit it to our Support Team.

Software that blocks WebSockets by default:

  • ZoneAlarm Firewall (Adding exceptions for Grammarly does not help. Even if you disable it, it will continue to block Grammarly until it is uninstalled.)
  • AVG
  • Avast
  • Bitdefender
  • IObit Malware Fighter
  • Internet Download Manager
  • Superfish VisualDiscovery
  • Avira Browser Safety
  • Browser Guard
  • Pokki
  • Smart Panel

If any of these programs is installed on a computer, this might prevent establishing the connection with Grammarly’s server.

If none of these programs are installed on your computer but you are still experiencing issues related to your network configuration, we encourage you to get in touch with your network administrator and ask them to check out the following articles on troubleshooting the issue: WebSockets Support Q&A for System Administrators

Was this article helpful?
Have more questions? Submit a request

Comments

websocket websocket configuration websocks websockets network configuration error checking unavailable oops