Thanks to Thomisus for your great work!
Unfortunately, the combination of Nextcloud 28 and Onlyoffice 7.5 is not stable for me. Every few hours I get an error message that the Onlyoffice server cannot be reached. Nextcloud then permanently deactivates the connection to Onlyoffice. I haven’t discovered the cause yet, so I reactivated the old 7.4 container.
OK, here are my OO Log. In /var/log/apache2/… there isn’t anysthing suspicious…
Flushing stats at Mon Jan 01 2024 17:54:02 GMT+0000 (Coordinated Universal Time)
{
counters: {
'statsd.bad_lines_seen': 0,
'statsd.packets_received': 0,
'statsd.metrics_received': 0
},
timers: {},
gauges: { 'statsd.timestamp_lag': 0 },
timer_data: {},
counter_rates: {
'statsd.bad_lines_seen': 0,
'statsd.packets_received': 0,
'statsd.metrics_received': 0
},
sets: {},
pctThreshold: [ 90 ]
}
==> /var/log/onlyoffice/documentserver/converter/out.log <==
[2024-01-01T17:55:05.067] [ERROR] [localhost] [conv_check_767709941_docx] [userId] nodeJS - error downloadFile:url=https://myserver.de/nextcloud/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.8HlucZ9-HMlxRx9BUrlnjxvYOlhtZKxr-Xfi0xks_j8;attempt=1;code:null;connect:null Error: Error response: statusCode:404; headers:{"date":"Mon, 01 Jan 2024 17:55:05 GMT","server":"Apache/2.4.56 (Debian)","content-length":"289","keep-alive":"timeout=5, max=100","connection":"Keep-Alive","content-type":"text/html; charset=iso-8859-1"};
at Request.fResponse (/snapshot/server/build/server/Common/sources/utils.js)
at Request.emit (events.js:400:28)
at Request.onRequestResponse (/snapshot/server/build/server/Common/node_modules/request/request.js:1066:10)
at ClientRequest.emit (events.js:400:28)
at HTTPParser.parserOnIncomingClient (_http_client.js:647:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)
at TLSSocket.socketOnData (_http_client.js:515:22)
at TLSSocket.emit (events.js:400:28)
at addChunk (internal/streams/readable.js:293:12)
at readableAddChunk (internal/streams/readable.js:267:9)
at TLSSocket.Readable.push (internal/streams/readable.js:206:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)
My nextcloud instance is reacheable via nextcloud.myserver.de an not as seen in the log via myserver.de/nextcloud… but i don’t know how to chance that nor that i put in this wrong adress anywhere.
Whats also wired… this error occurs every day between 18:30-18:50 UTC
Do you have a magical tutorial to explain how you compile this docker ? In case you are bored to do it one day ^^
Last time i check, Onlyoffice was very poor in documentation for this
docker pull ghcr.io/thomisus/onlyoffice-documentserver-unlimited:latest
or
docker pull thomisus/onlyoffice-documentserver-unlimited:latest
or
docker pull ghcr.io/thomisus/onlyoffice-documentserver-unlimited:8.0.1
or
docker pull thomisus/onlyoffice-documentserver-unlimited:8.0.1
Can you make this patch as a regular install instead of docked? I tried with my install and it only let me edit text files, couldn’t even open doc files.
This is excellent and I can tell would work, but my install isnt done by docker
If you need mobile apps working you have to manually run
sed -i 's/isSupportEditFeature=function(){return!1}/isSupportEditFeature=function(){return 1}/g' /var/www/onlyoffice/documentserver/web-apps/apps/*/mobile/dist/js/app.js;
I think that sometimes people should start to read git repositories and diffs and try to understand what’s going on and what they are going to install
BTW, I’ll continue to provide builds for new releases as long there’s interest. Maybe in the future I will provide my semi-automatic build script ( at the moment is not well commented and clean )