search

CollaboraOnline / richdocumentscode

Built-in CODE Server app
https://apps.nextcloud.com/apps/richdocumentscode
Apache License 2.0
121 stars 29 forks source link

Nextcloud 24.0.1 - Office 6.1.1 / Built-in CODE 22.5.301 endlessly loading documents #191

Open MegadoomerX opened 2 years ago

MegadoomerX commented 2 years ago

Hi everyone,

I've recently updated Nextcloud Office from 6.1.0 to 6.1.1 and the built-in CODE server from 21.11.402 to 22.5.301.

Previously, everything worked fine. However now, any document, existing or newly created, just leads to an endless loading screen "Loading (document).(file)...". There is no error or other prompt, except for canceling.

Also, apparently, nothing is getting redirected in the browser (no domains on the bottom left). I can't find any hints in the system logs.

The settings say that the built-in CODE server is reachable, although when clicking on it, the connection is lost, but this seems like a menu issue, when reloading, the server status is green again.

Since there is unfortunately no way to easily roll back to a previous version, is there anything to further analyze the issue or something to try to get it back to working?

rarealphacat commented 2 years ago

Restart the apache2 fixed it for me, but I was going from 22.5.301 to 22.5.401. See if that helps. e.g. sudo systemctl restart apache2

ashworksco commented 2 years ago

Restarting Apache didn't work for me, and I have this problem. No logs are output. I've narrowed it down to the server hanging, and not something else about NextCloud, but I'm stumped from here.

I'm on a direct install into the web directory on a synology device. I've checked other discussions and I'm not confident I can replicate the directions given for people with similar set-ups as my own.

System: Synology DS220+ Server: Apache 2.4 Service: NextCloud 24.0.3 CODE version: 22.5.401 Nextcloud Office version: 6.1.1

I have attempted to add the reverse proxy settings in my Apache 2.4 config file, but it either breaks (SSL version) or doesn't do anything (HTTP-only version). I am pretty new to this level of tinkering, so I am open to suggestions, but flying blind here.

wck86 commented 2 years ago

I had this issue also. It started when upgrading from version 23.XX to the current version 24.0.3. In settings, it can't connect to the built-in CODE server, and when attempting to open a document for editing, it fails. All NC apps are current. Is there a fix for this?

ashworksco commented 2 years ago

This seems to be a constant issue in many different NextCloud installations (I've tried several different installation types--the AIO, docker, direct via both CentOS and Debian distros and adjusted packages), and I am starting to think it might be on their end, and not on Collabora's, but it's hard to say as someone who's not quite knowledgeable enough to find the fix, myself.

I have gotten Collabora to work twice out of... many installations, one on ARM and once on x86 by testing with the demo server, both locally and on a VPS with a static IP and SSL,. It's confusing to know where to find answers but I keep hoping, as I like using this over OpenOffice.

PS: it's occurring in NextCloud 22, 23, and 24, from what I can tell.

PalmTreeVI commented 2 years ago

I have 2 servers, one is arm64, both have Collabra v22.5.502. Collabra works without issue on the arm64 server, it just endlessly loads on the x86 server.

SevHub commented 2 years ago

Same problem. Installed Ubuntu 22 and included the snap packackge of nextcloud. Installed the built-in CODE Server thorugh the GUI and also the CLI, both did not work. Just endless loading when trying to open a document. In the Settings, a green arrow tells me that the CODE Server is running and reachable. Whatever, I give up at this point.

sergedc commented 2 years ago

Same for me:

Shows the green tick in the settings. When I click on any document, it goes into endless loading...

Do you think the problem is with Nextcloud / Nextcloud office / Build in CODE server? If we know which one we can try another version

HaleyACS commented 2 years ago

Using the official nextcloud docker images in kubernetes (k3s) with nginx-ingress. Same issue, adding on top that the entire NC UI Freezes if I activate collabora online + code server.

I have a special redis setup (nutcracker+2 redis instances for HA/LB). Logs only show something about unable to write session data when enabling Collabora Online.

endotom commented 2 years ago

Same Problem: new Dokuments not loading, old Documents very slow..., Browser crash if Document is edited with more than three words...

nc 24.0.06 HanssoniT VM NC Office 6.3.1 Problems with the last 2 upates now: 22.5.802 crashes the complet browsert down. Working anymore not possible.. No entry in log (what i can see ...)

stephen304 commented 8 months ago

This is constantly happening for me with the built in code server, currently using nextcloud:28.0.2-fpm-alpine with the Nextcloud Office 8.3.2 plugin and built in code server plugin 23.5.904.

The odd thing is, even though this has happened to me through many major versions of Nextcloud (since like 24 or 25 at least), I'm usually able to fix it just by going to Administrative Settings > Nextcloud Office and clicking the "Use the built-in CODE" radio button, even though it's already selected. Often after an update I have to click this again to make it say "Setting up a new server" and then it works fine.

If the built in code server becomes broken due to update or some other issue, it would be nice if NC could automatically restart because it's become somewhat of a ritual for me to find that documents don't open, so I just go there and click that radio button a bunch and then try again.

timur-g commented 8 months ago

Many reporters here but issue does not sem actionalble. I understand that this works in the end. If not after NC upgrade, than that is an issue for NC, not here for Built in CODE. I set NeedInfo for clarification.

stephen304 commented 1 month ago

I'm experiencing this again after upgrading to NC 30. It seems the request to /apps/richdocuments/token returns 500 with "Failed to generate token". The server logs show nothing unusual. As before I'm using nextcloud:30.0.0-fpm with Nextcloud Office 8.5.1 plugin with nextcloud built in code plugin 24.4.702.

Is there any way I can help clarify this issue? It's really frustrating and it seems the only way to get it to work in these cases is to restart things a bunch until it works.

I can create a new issue if that's better