By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

What is the current behavior?
https://<onlyoffice_ip>/ConvertService.ashx is requested by Nextcloud, but the page results in

even without going through a reverse-proxy (I mean that http://<onlyoffice_ip>/ConvertService.ashx returns the same result).

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

What is the expected behavior?
Not this

Did this work in previous versions of DocumentServer?
First time

DocumentServer Docker tag:
latest-arm64

Host Operating System:
Ubuntu 20.04

https://<onlyoffice_ip>/ConvertService.ashx is requested by Nextcloud, but the page results in

If you opened this page in browser it work as GET request and there is nothing to convert so this is not an error (but may be a little bit clear, I can agree)

You need to use POST request according to docs to convert file via convert service

I thought the webpage would help figure out what went wrong, but I guess not.
This is the original error message from Nextcloud

The only noteworthy log I could find is

==> /var/log/onlyoffice/documentserver/nginx.error.log <==
2022/07/12 10:18:43 [error] 382#382: *1 upstream prematurely closed connection while reading response header from upstream, client: 10.0.0.5, server: , request: "POST /ConvertService.ashx HTTP/1.1", upstream: "http://127.0.0.1:8000/ConvertService.ashx", host: "REDACTED"

This is hosted on a cloud server, 10.0.0.5 is the IP of the reverse-proxy (hosted on a different server at the same cloud provider).

Could you check that http://docserverurl/example can convert file (uploading doc for example) without any error?
If such - there is problem with nextcloud and I'll redirect your to another repo

Me ----> VPN ----> http://docserver_LAN_ip/example/ ----> cannot edit any file & conversion failure (Nextcloud fail)
Me ----> reverse-proxy ----> https://docserver_public_url/example/ ----> all good (Nextcloud fail)
Me ----> http://docserver_public_ip/example/ ----> all good

The VPN & reverse-proxy are on server A, OnlyOffice container on server B, but A and B are on the same network.

Hopefully, my explanation is clear.

I think your explanation is clear enough, but I have no idea why this happen, seems something is wrong on VPN side 🤷

If anyone has any idea what may be reason of this - welcome

To be honest, I will be happy as long as the reverse-proxy setup works.
I mentioned the others for completeness :P

Would it help if I logged the traffic request that Nextcloud does?

If such - there is problem with nextcloud and I'll redirect your to another repo

Should I ask the Nextcloud / OnlyOffice Document Server repo about this?

Hello
I've got the same problem:
on nextcloud : Server error: POST https://******.com/ConvertService.ashx resulted in a `504 Gateway Time-out

On the onlyoffice logs :

[2023-02-21T14:35:32.046] [ERROR] [localhost] [conv_check_1149903374_docx] [userId] nodeJS - error downloadFile:url=https://*****.com/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.sAUrBs3XZjVaKZawZ_V4lOvO8WgRrFm7HdQwk0ziPfE;attempt=1;code:ETIMEDOUT;connect:undefined Error: Error: whole request cycle timeout
at raiseError (/snapshot/server/build/server/Common/sources/utils.js)
at Timeout._onTimeout (/snapshot/server/build/server/Common/sources/utils.js)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)

But on both server I can, ping, telnet 443, curl and wget each other.
It was working until this morning, the service stop without explanation..

I am not sure exactly why, but I forced Traefik (my reverse-proxy) to add the headers X-Forwarded-Proto: https and access-control-allow-origin: * using a middleware and it worked.
I hope it helps someone else who had a similar problem.

Thank you @ShockwaveNN and @SergeyKorneyev for the replies :)