Troubleshoot Wrike Document Editor
Situation
With the Document Editor, you can edit attachments in Wrike without downloading them. If you run into issues, such as the editing process not starting or new document versions not saving, there are a few potential causes and solutions you can explore.
Troubleshooting
Document Editor is Outdated
If the Document Editor is outdated, you can uninstall the older version and install the latest one. Here's how to do it:
- Go to Installed apps (alternatively, Apps & Features) on your computer and click Uninstall next to Wrike Document Editor
-
Delete the
WrikeDocumentEditorfolder from the/Roaming/folder. The full path looks like this:C:\Users\%username%\AppData\Roaming\WrikeDocumentEditor. - Install the latest version of Document Editor.
Document Editor is Not Launched
By default, Document Editor should start automatically with your computer. If it doesn't, you can start it manually. Here's how to do it:
You can also ensure that Document Editor is added to your startup applications, so you don't have to manually launch it after rebooting or restarting your computer:
- Open System Settings.
- Go to General and select the Login Items.
- Click the ‘+’ button under Open at Login to add an application.
- Navigate to the location of
WrikeDocumentEditorClientand add it.- Open Finder and press ⌘ + Shift + G.
- Enter
~/Library/Wrikeand hit Go. - Select
WrikeDocumentEditorClientand click Open.
Browser Does Not Recognize Document Editor
Your browser facilitates the connection between your files and the Document Editor. If your corporate network uses a proxy, firewall, VPN, or antivirus program, these might be blocking Wrike resources. Here are a few steps you can try to resolve this issue:
- Configure Your Browser - Adjust your browser settings so that it automatically detects the Document Editor connection.
- Configure Your Proxy Server - If you have access to an IT helpdesk, their specialists can assist you with editing proxy settings to allow Wrike through.
- Configure Firewall Whitelisting - Verify with your IT team if any network restrictions are in place and request them to whitelist Wrike resources.
You can run a test to verify if your browser sees the Document Editor:
- Navigate to www.wrike.com/support-tool in your web browser.
- Open the JavaScript developer console in your browser.
-
On macOS: Press
Command (⌘) + Option (⌥) + J. -
On Windows: Press
Control (Ctrl) + Shift + J.
-
On macOS: Press
- Look for any Document Editor related records in the console.
In the example provided above, despite seeing WebSocket error messages, a successful connection to the Document Editor is indicated by activity on one of the three WebSocket connection ports (22112, 22113, and 22114). The tool connects using one port at a time, so errors on the other two are expected. However, if you see WebSocket connection errors for all three ports, there may be a real connection problem.
Local network access to local apps disabled in Chrome and Edge
Following recent updates to Google Chrome and Microsoft Edge (version 147), local network access for WebSockets has been restricted. When users edit a document in Wrike for the first time, the browser prompts them to allow access to local apps. If the prompt is denied or ignored, users must manually enable local network access in their browser settings.
Please follow these steps to ensure the "Apps on device" option in site settings for Wrike is enabled: