You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Collabora Online - Built-in CODE Server in Nextcloud docker. Documents do not load #1896
I am using Docker behind nginx proxy manager and everything works fine. I installed Collabora Online - Built-in CODE Server and Nextcloud office and that also seems fine. But opening an document does not work, it keeps spinning.
Error | richdocuments | GuzzleHttp\Exception\ConnectException: cURL error 28: Operation timed out after 45000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://example.com/custom_apps/richdocumentscode/proxy.php?req=/hosting/capabilities
-- | -- | --
I also tried a different docker image (linuxserver.io) on a different local server without nginx proxy manager. The exact same thing happens. Driving me nuts. Is Collabora built in app with nextcloud office simply not working with docker? Does anyone successfully use this at all?
I can use it fine, on first set up in integration app nextcloud office you should look at the logs, in my case im missing libfuse2 library so the appimage wont load at all. then i disable/enable again, and the CODE run correctly.
Nextcloud Office app does show all the options and green check Collabora online is indeed reachable. However Opening a file takes forever and ends up like this
I checked /data/nextcloud.log and don't see anything weird except for WOPI. Never set those addresses before with built in collabora app. But creating a white list doesn't help anyway.
Any suggestions which logs I should take a look at?
I cant really tell much, aside im on glibc based docker image, and the libfuse2 that preventing appimage startup. Im gonna say, go into container console and try execute the appimage manually. 🤔 should be throw error if something not right/preventing it to run.
I am using a valid certificate in nginx proxy manager and set up Nextcloud to work behind a proxy just like Nextcloud explains in it's documents. But SSL shouldn't be an issue when using the built in collabora app right? Should work out of the box, at least that's my experience (before I started using docker ;))
I am using a valid certificate in nginx proxy manager and set up Nextcloud to work behind a proxy just like Nextcloud explains in it's documents. But SSL shouldn't be an issue when using the built in collabora app right? Should work out of the box, at least that's my experience (before I started using docker ;))
so what im experiencing is when loading using https://someip:port the CODE wont load at all, the log show 400 something, vice versa when access using a valid domain it load successfully. Maybe affecting you or not, cant really tell. ☕ good luck in finding out which one your issue is.
I think it might be missing libfuse. I just tried creating a spreadsheet using the built in CODE server and found this in my logs
...
192.168.0.11 - - [22/Jan/2023:20:03:22 -0800] "PROPFIND /remote.php/dav/files/ckuethe/test.ods HTTP/1.1" 207 1375 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36"
dlopen(): error loading libfuse.so.2
AppImages require FUSE to run.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
...
Saving the (empty) field "Allow list for WOPI requests" in the Office settings - using the arrow at the end of the input box - fixed this issue (Failed to load Nextcloud Office - please try again later) for me.
To avoid confusion: I did not experience any errors related to libfuse.
Reacted by Dedy Martadinata S, cableTh0rn, Julian Petri and Mihail
Fresh installation.
Indeed, the CODE application is installed and located in the correct directory. However, I'm encountering an issue with launching it. When I attempt to run the application by executing
"./Collabora_Online.AppImage"
in the
"/var/www/html/custom_apps/richdocumentscode/collabora" folder, I receive the error message
"sh: ./Collabora_Online.AppImage: not found".
Additionally, when I try to select the Collabora instance, I encounter the following error: "PHP message: richdocumentscode (proxy.php) error exit, PID: 68, Message: no_glibc".
For the built-in collabora CODE server to work, you have to ensure that:
You use one of the Debian-based images (not-alpine) and
you set the environment variable APPIMAGE_EXTRACT_AND_RUN=1 (for example using docker run -e or by adding it to the environment:-key inside docker-compose.yml)
This is necessary because alpine does not ship with bash by default which the CODE AppImage needs (among possibly other things) and FUSE is not available inside docker, so the AppImage has to be unpacked in order to run.
Reacted by kochinc, Thore Göbel, Vasko Mihaylov and Felix Eckhofer
You use one of the Debian-based images (not-alpine) and
you set the environment variable APPIMAGE_EXTRACT_AND_RUN=1 (for example using docker run -e or by adding it to the environment:-key inside docker-compose.yml)
Thanks for the clue. Once I switched to nextcloud:fpm image instead of nextcloud:fpm-alpine, the Collabora CODE is able to open files without issues. I don't even have to set the APPIMAGE_EXTRACT_AND_RUN variable.
Saving the (empty) field "Allow list for WOPI requests" in the Office settings - using the arrow at the end of the input box - fixed this issue (Failed to load Nextcloud Office - please try again later) for me. To avoid confusion: I did not experience any errors related to libfuse.
This fixed my issue thanks (documents do not load, spinning)
Activity
Japhys commentedon Jan 13, 2023
The log says this, no sure what to do
Japhys commentedon Jan 14, 2023
I also tried a different docker image (linuxserver.io) on a different local server without nginx proxy manager. The exact same thing happens. Driving me nuts. Is Collabora built in app with nextcloud office simply not working with docker? Does anyone successfully use this at all?
martadinata666 commentedon Jan 15, 2023
I can use it fine, on first set up in integration app
nextcloud officeyou should look at the logs, in my case im missinglibfuse2library so the appimage wont load at all. then i disable/enable again, and the CODE run correctly.If the appimage run correctly then the
Nextcloud Officeapp will show many options and green checkCollabora online reachableJaphys commentedon Jan 15, 2023
Thanks @martadinata666
Nextcloud Office app does show all the options and green check Collabora online is indeed reachable. However Opening a file takes forever and ends up like this
I checked /data/nextcloud.log and don't see anything weird except for WOPI. Never set those addresses before with built in collabora app. But creating a white list doesn't help anyway.
Any suggestions which logs I should take a look at?
martadinata666 commentedon Jan 15, 2023
I cant really tell much, aside im on glibc based docker image, and the
libfuse2that preventing appimage startup. Im gonna say, go into container console and try execute the appimage manually. 🤔 should be throw error if something not right/preventing it to run.Japhys commentedon Jan 15, 2023
Thanks! I will dive into it a bit more and try a few things
martadinata666 commentedon Jan 15, 2023
oh almost forgotten, also check the SSL thing, should use valid one. or disabling it completely (http) only.
Japhys commentedon Jan 15, 2023
I am using a valid certificate in nginx proxy manager and set up Nextcloud to work behind a proxy just like Nextcloud explains in it's documents. But SSL shouldn't be an issue when using the built in collabora app right? Should work out of the box, at least that's my experience (before I started using docker ;))
martadinata666 commentedon Jan 15, 2023
so what im experiencing is when loading using
https://someip:portthe CODE wont load at all, the log show 400 something, vice versa when access using a valid domain it load successfully. Maybe affecting you or not, cant really tell. ☕ good luck in finding out which one your issue is.ckuethe commentedon Jan 23, 2023
I think it might be missing libfuse. I just tried creating a spreadsheet using the built in CODE server and found this in my logs
kosmosac commentedon Feb 17, 2023
Saving the (empty) field "Allow list for WOPI requests" in the Office settings - using the arrow at the end of the input box - fixed this issue (Failed to load Nextcloud Office - please try again later) for me.
To avoid confusion: I did not experience any errors related to libfuse.
kacperpaczos commentedon Apr 17, 2023
The bug is still persisting in version 26 of Nextcloud, which was installed on Docker and accessed through a reverse proxy.
/var/www/html/custom_apps/richdocumentscode/collabora/Collabora_Online.AppImage: not foundkacperpaczos commentedon May 7, 2023
Fresh installation.
Indeed, the CODE application is installed and located in the correct directory. However, I'm encountering an issue with launching it. When I attempt to run the application by executing
"./Collabora_Online.AppImage"
in the
"/var/www/html/custom_apps/richdocumentscode/collabora" folder, I receive the error message
"sh: ./Collabora_Online.AppImage: not found".
Additionally, when I try to select the Collabora instance, I encounter the following error: "PHP message: richdocumentscode (proxy.php) error exit, PID: 68, Message: no_glibc".
kacperpaczos commentedon May 7, 2023
From: https://github.com/CollaboraOnline/richdocumentscode#system-requirements
Nextcloud 19 with Collabora Online app 3.7.0 or higher
glibc (AppImage/AppImageKit#1015)
Fontconfig (libfontconfig.so.1 - required by Collabora_Online.AppImage)
tribut commentedon May 23, 2023
For the built-in collabora CODE server to work, you have to ensure that:
-alpine) anddocker run -eor by adding it to theenvironment:-key inside docker-compose.yml)This is necessary because alpine does not ship with bash by default which the CODE AppImage needs (among possibly other things) and FUSE is not available inside docker, so the AppImage has to be unpacked in order to run.
kochinc commentedon Jun 21, 2023
Thanks for the clue. Once I switched to nextcloud:fpm image instead of nextcloud:fpm-alpine, the Collabora CODE is able to open files without issues. I don't even have to set the APPIMAGE_EXTRACT_AND_RUN variable.
thgoebel commentedon Jun 26, 2023
I recently run into the same problem. Documents don't load, and the request to https://cloud.example.com/custom_apps/richdocumentscode/proxy.php?status times out with 504.
After seeing this thread I set
APPIMAGE_EXTRACT_AND_RUN=1. This resulted in:After seeing this error message it clicked: I recently followed Nextcloud Recognize's advice of mounting tmp as tmpfs: https://github.com/nextcloud/recognize#tmp
The solution is to add
:exec(see StackOverflow):Now it works again, I don't even need APPIMAGE_EXTRACT_AND_RUN.
Add exec flag to tmpfs
Add exec flag to tmpfs
cableTh0rn commentedon Oct 4, 2023
This fixed my issue thanks (documents do not load, spinning)
(README) Add note about Alpine based image compatibility
joshtrichards commentedon Jun 1, 2024
Closing since this isn't really an image matter.