Edit online

Document Loading Issues

Problem

I received a Document could not be loaded error message when trying to open a document.

Cause

If the document is stored on a file server that uses HTTPS, a possible cause is that the server uses a self-signed or invalid certificate.

Solution

If you encounter this issue, an administrator can do the following:
  1. Go to the Administration Page and click on Connection.
  2. Select the Automatically accept a security certificate, even if invalid option.
  3. Click Apply.

Cause

If the document fails to load with the Document could not be loaded message after a long wait (for example, 30 to 60 seconds), there might be a reverse proxy server in front of Oxygen XML Web Author that times out.

To confirm if this is the case, a system administrator should look in the browser's Developer Tools in the Network tab to see if the status code of the failed request is 504 (Gateway timeout).

Solution

The solution is to either configure the reverse proxy to use a larger timeout, or to troubleshoot why loading the document takes too long.