Where to look when getting "conversion timeout exceeded" error on new integration

I am building an integration and testing with an instance of the DocumentServer which is installed within a Docker container.

# apt info onlyoffice-documentserver
Package: onlyoffice-documentserver
Version: 8.3.3-18

The docker container has port 80 forwarded to 9080 on my host, and 443 forwarded to 9443. I am using minica to manage a local root ca which I’ve added to my browser as well as system certs in the container, and I also have rejectUnauthorized set to false (for local testing purposes only, this is not a production configuration). I’ve gotten past a few issues and so far I have:

  • ensured a websocket connection is established on the client
  • ensured my read URL is wget-able from the DocumentServer container
  • ensured all my hosts in /etc/hosts are correct on each “side” between the host and container

In the UI I see the document editor open and a box read “loading” for some time until I get an error saying “conversion timeout exceeded”. Where does this error come from? What should I start looking for next?

This was an issue related to my fake systemctl implementation (because systemd can’t run in the container). The systemd unit file for ds-converter has two Environment= entries and I was only taking the second one. That said, maybe the unit file shouldn’t be written like this in the first place.

Hello @eric.dube

Good to know that you resolved the issue. Just for your information, inside the container you should use supervisorctl to work with services of Document Server. For instance, to restart all services you can use supervisorctl restart all.

Should I mark this case as solved?