⏱ 1.5 min read
Overview
WebSocket technology allows Wrike to get real-time Workspace updates and enables the collaborative editing of description fields. Future versions of Wrike will require this technology in order for certain features to work. To guarantee the best performance and compatibility, we recommend checking that WebSockets are working properly with Wrike on your device.
Websocket Requirements
Starting September 30, 2018 Wrike will require the use of WebSocket technology by your web browser or client. If WebSockets are not working properly after that date then Wrike will continue to function, but the following features may not work:
- Live editing of task descriptions.
- Getting Inbox notifications (without refreshing the page).
- Seeing various changes made by other users, e.g. adding/removing Projects, Folders or tasks.
Check that WebSockets are Working
- Open Wrike’s Support Tool.
- Under “Access to Wrike Transport”, if it says “Success” that means WebSockets are up and running. If you do not see “Success”, check our troubleshooting steps below.
Troubleshooting Websockets
- Supported browsers. Confirm that you’re using a supported browser. If you’re not, try using one of those and then check that WebSockets are working (see above).
- Proxy servers and firewalls. Check if you have a proxy server or firewall that blocks WebSocket access (you might need your system administrator’s help).
- Wrike requires WebSocket connections to *.www.wrike.com on port 443. You might need to: add an exception to your firewall and/or have your proxy intercept WebSocket connections.
- Check that WebSockets are working (see above).
- WebSockets not working after trying steps 1 and 2. Open a new support request and provide the following information:
- Log data from the browser's developer console. (Our Support team can help provide instructions on how to do this if you're not sure how).
- Support Tool data: Open Support Tool and click “Copy to Clipboard”.
- Details about any network issues you’re aware of.