: Log into your Document Server (using docker exec if applicable) and run: curl -I [URL_of_your_document]
If the error is deterministic (only happening to certain files), check the extension. Try renaming files to use lowercase extensions and see if they load correctly. download failed press ok to return to document list
Ensure that the URL where the file is stored is reachable from the server where the Document Server is installed. : Log into your Document Server (using docker
If you are using JWT protection, ensure the header name is consistent across both the connector (e.g., Nextcloud/Mattermost) and the Document Server settings. For Mattermost users, change the JWT_HEADER from "Authorization" to a custom value to avoid security blocks. 3. Adjust HTTPS/SSL Settings If you are using JWT protection, ensure the
If you receive a timeout or a 404/403 error, the Document Server cannot reach the file. 2. Check JWT Signature Settings
If using self-signed certificates, you may need to disable certificate verification in your configuration files (e.g., local.json ) to allow internal communication: Set rejectUnauthorized to false in your server settings.
In many instances, a simple restart of the Docker container or the internal services (like RabbitMQ or PostgreSQL) resolves temporary communication hang-ups. 5. Lowercase File Extensions