NC 19 unable to Use Build in Code Server #26

apg1980 · 2020-06-03T13:39:01Z

Describe the bug
NC 19 stable with Collabora Online - Built in CODE Server throws errors in Apache error.log:

AH01071: Got error 'en(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246'
Nextcloud is displaying error: Connection to Documentserver lost.
New or existing Documents arent opened, white screen appears (see log above).

Settings are correct to use internal CODE Server:

To Reproduce
Steps to reproduce the behavior:

Klick New Document
see

Expected behavior
Document is opening for editiing

Client details:

Browser Latest Firefox

Server details

Operating system: Ubuntu 18.04 LTS

Web server: Apache2

Database: Postgresql

PHP version: PHP7.3-fpm

Nextcloud version: 19

Version of the richdocuments app 3.7.0

Version of Collabora Online 4.2.403

Logs

Nextcloud log (data/nextcloud.log)

No entrys available

The text was updated successfully, but these errors were encountered:

Ecphrasis · 2020-06-03T13:40:26Z

Same problem for me, on 19 released this morning. I can't even connect to the built-in CODE

Apche log : tons of PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246PHP

Server details
Operating system: Debian Buster

Web server: Apache2

Database: MySQL

PHP version: PHP7.4-fpm

Nextcloud version: 19

Version of the richdocuments app 3.7.0

Version of Collabora Online 4.2.403

nextgen-networks · 2020-06-03T17:37:39Z

Same problem for me ...

Added experience also on help.nextcloud.com Forum:
https://help.nextcloud.com/t/built-in-code-server-app/83074/8

nextgen-networks · 2020-06-03T17:48:00Z

Problem also exists when adding this to additian directives if ngingx-config:

location ~ ^\/nextcloud\/(?:index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|oc[ms]-provider\/.+|.+\/richdocumentscode\/proxy)\.php(?:$|\/) {
	fastcgi_split_path_info ^(.+?\.php)(\/.*|)$;
	set $path_info $fastcgi_path_info;
	try_files $fastcgi_script_name =404;
	include fastcgi_params;
	fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
	fastcgi_param PATH_INFO $path_info;
	fastcgi_param HTTPS on;
	# Avoid sending the security headers twice
	fastcgi_param modHeadersAvailable true;
	# Enable pretty urls
	fastcgi_param front_controller_active true;
	fastcgi_intercept_errors on;
	fastcgi_request_buffering off;
}

tgurr · 2020-06-03T18:51:05Z

So I was also getting

[03-Jun-2020 19:51:14 Europe/Berlin] PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/server/htdocs/apps/richdocumentscode/proxy.php on line 246

and the lack of any documentation is really frustrating, I had hoped after the onlyoffice debacle with NC18 that wouldn't repeat, at least the news entry for NC19 states that it's only for personal use.

So there are a few prerequisites which looks like they aren't mentioned anywhere - README.md (?).

There's a Collabora_Online.AppImage executable residing in apps/richdocumentscode/collabora.

After trying to manually launch it
su -c "./Collabora_Online.AppImage" -s /bin/bash www-nextcloud

I first got

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

so that's the first prerequisite.

After I installed fuse2 it wouldn't of course run since my kernel didn't include fuse support.
fuse: device not found, try 'modprobe fuse' first
so recompiling the kernel..

Next I got
Failed to load /tmp/.mount_Collabj8lnLI/opt/collaboraoffice6.2/program/libmergedlo.so: libfontconfig.so.1: cannot open shared object file: No such file or directory
after installing fontconfig I could finally launch the AppImage and afterwards it also worked fine from within Nextcloud.

Note: Somewhere along the line I also had to add /proc/1/cgroup to my open_basedir and I also installed the php proxy module, not sure if those are actually required though.

kendy · 2020-06-03T21:29:05Z

Hello, sorry about the problem! Let me quote:

`AH01071: Got error 'en(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246
PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246
PHP message: PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/nextcloud/apps/richdocumentscode/proxy.php on line 246
[...]
PHP version: PHP7.3-fpm

I believe this is the same bug we are actually working on - that the PHP7.3-fpm refuses to accept connections after some time. Please restart it using something like:

service php7.3-fpm restart

and the CODE server should start working again.

Can you please confirm that this fixes the behavior (until the PHP7.3-fpm stops working again)? To be sure we are working on the same thing.

Thank you in advance!

kendy · 2020-06-03T21:36:57Z

Hello Timo, thank you for writing this down!

So there are a few prerequisites which looks like they aren't mentioned anywhere - README.md (?).

Please is it OK for you if we actually copy info from your post to the README? :-) Or would you like to do a pull request? Very happy to accept patches!

Currently we avoid FUSE (and unpack the AppImage instead) when we run under Docker / LXC, but apparently we should improve the detection code to avoid the use cases like yours...

All the best!

nextgen-networks · 2020-06-03T22:56:10Z

Hello, sorry about the problem! Let me quote:

...

Can you please confirm that this fixes the behavior (until the PHP7.3-fpm stops working again)? To be sure we are working on the same thing.

Thank you in advance!

Hello, Kendy,
thank you for your feedback.
Unfortunately this doesn't help - the behaviour is exactly the same after a new service plesk-php73-fpm restart.
So there seems to be another reason here.
Greetings

Ecphrasis · 2020-06-04T03:34:32Z

Hi,
After a systemctl restart php7.4-fpm, and even a reboot of the server, problem still occurs. I have deactivated the two apps and am waiting for an update :)
Greetings !

apg1980 · 2020-06-04T07:04:46Z

as i can see, after trying to open an document, an ipv6 socket is opened:
tcp6 0 0 :::9982 :::* LISTEN 6061/loolwsd
...but no ipv4, is this the issue?

4001982248998 · 2020-06-04T07:55:16Z

installing fuse, fontconfig and restarting php7.4-fpm fixed it for me.

apg1980 · 2020-06-04T08:30:21Z

On my Ubuntu 18.04 LTS i got already following:

`---:~$ sudo apt-get install fuse
Paketlisten werden gelesen... Fertig
Abhأ¤ngigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
fuse ist schon die neueste Version (2.9.7-1ubuntu1).

---:~$ sudo apt-get install fontconfig
Paketlisten werden gelesen... Fertig
Abhأ¤ngigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
fontconfig ist schon die neueste Version (2.12.6-0ubuntu2).`

Still opening an IPV6 socket and no connection possible.

domchrgit · 2020-06-04T12:37:59Z

I made a fresh install of Nextcloud 19 from scratch, and Collabora Online doesn't work

To Reproduce
If I try to open a document like the default one in Documents folders "Welcome to Nextcloud Hub.docx", there is a turning circle and after few seconds I obtain the error message "Failed to load Collabora Online - please try again later"
If I look into the settings of Collabora Online, the built-in CODE server is checked but a red cross indicate "Could not establish connection to the Collabora Online server"

Expected behavior
I expect that Collabora Online works ...

Client details:

OS: Linux Centos7
Browser: Chrome
Version: 83
Device: desktop
Server details
Operating system:
Linux h2web20 4.9.0-0.bpo.12-amd64 #1 SMP Debian 4.9.210-1~deb8u1 (2020-02-21) x86_64 GNU/Linux

Web server:
Apache 2.4.34

Database:
MySQL 5.7

PHP version:
7.3

Nextcloud version:
19.0.0

Version of the richdocuments app
Text 3.0.1

Version of Collabora Online
Collabora Online 3.7.0
Collabora Online - Built-in CODE Server 4.2.403

kyrofa · 2020-06-05T00:29:12Z

Same problem for me, on 19 released this morning. I can't even connect to the built-in CODE

That's what it looks like in the snap as well.

pheiduck · 2020-06-05T10:11:58Z

Get the same on docker won’t connect to the Build in Code Server

OS: Arch Linux x86_64
Host: vServer 20171111
Kernel: 5.6.15-arch1-1
CPU: AMD EPYC (with IBPB) (2) @ 2.495GHz

root:~/ # netstat -lnpt | grep docker                                                                                                            
tcp6       0      0 :::80                   :::*                   LISTEN      docker-proxy    
tcp6       0      0 :::443                 :::*                   LISTEN     docker-proxy

kyrofa · 2020-06-05T15:45:40Z

Currently we avoid FUSE (and unpack the AppImage instead) when we run under Docker / LXC, but apparently we should improve the detection code to avoid the use cases like yours...

@kendy can we get that detection logic updated to include the snap as well? I'd be happy to help if you could point me to the right place in code.

kendy · 2020-06-05T15:58:48Z

@kyrofa Thanks for the offer to help! In the meantime, I've done this pull request:

#31

Instead of detection, we just fallback to --appimage-extract-and-run which should sort out even the cases when people are using a normal distro, but don't have the FUSE package installed. Can you try with that stuff applied please?

kyrofa · 2020-06-05T16:18:23Z

@kendy seems like a good approach. The patch still doesn't work on the snap and without a log I can't know for sure, but taking what you did there and running locally gives me a good idea:

# ./Collabora_Online.AppImage --appimage-extract-and-run
terminate called after throwing an instance of 'std::runtime_error'
  what():  Do not run as root. Please run as lool user.
/tmp/appimage_extracted_08b1ce0e45447fbaa468514439b2523c/AppRun: line 35:   917 Aborted                 (core dumped) loolwsd --config-file="${HERE}/etc/loolwsd/loolwsd.xml" --disable-lool-user-checking --port=9982 --lo-template-path="${HERE}/opt/collaboraoffice6.2" --o:sys_template_path="${HERE}/" --o:security.capabilities="false" --o:child_root_path="${WRITABLE}" --o:file_server_root_path="${HERE}/usr/share/loolwsd" --o:ssl.enable="false" --o:net.proxy_prefix="true" --o:storage.wopi.host[0]=".*" --o:storage.wopi.host[0][@allow]="true" --o:memproportion="50" --o:logging.file[@enable]="true" --o:logging.file.property[0][@name]="path" --o:logging.file.property[0]="${WRITABLE}/loolwsd.log" --o:welcome.enable="false" "$@"

Services in the snap run as (confined) root. Is there a way to opt out of that check?

kendy · 2020-06-05T17:10:32Z

@kyrofa Ah cool. Normally the loolwsd has to run under user 'lool' and we already have a switch that overrides this - but works only for "any non-root user". But we should probably allow that even for root; but unfortunately needs a rebuild of the AppImage, hope to include that early next week.

kyrofa · 2020-06-05T17:25:41Z

@kendy excellent, ping me next week then and I'd love to give it a test!

thmo · 2020-06-06T20:03:30Z

Also had some problems connecting to the server on Debian 9, running on a vserver.
Thanks to the comments in this ticket, I learned I had to install fuse and libfuse2, fine.

But then I hit another problem (only to be seen when trying to start the appimage manually):

LibreOfficeKit seccomp security lockdown failed. Exiting.

For anyone else seeing this: It can be fixed with this patch:

--- proxy.php~	2020-06-06 20:40:50.000000000 +0200
+++ proxy.php	2020-06-06 21:43:40.395496132 +0200
@@ -67,6 +67,7 @@
     @chmod($appImage, 0744);
 
     $launchCmd = $appImage;
+    $launchCmd .= ' --override=security.seccomp=false';
 
     // FUSE usually does not work in a docker, unpack instead
     if (preg_match('/(docker|lxc)/', file_get_contents('/proc/1/cgroup')))

Afterwards, the server starts fine (albeit the performance is limited on a small vserver...)

Not sure if it is possible to detect the seccomp issue automatically.

kyrofa · 2020-06-06T20:06:41Z

It tries to do stuff with seccomp? That might prove to be an issue in the snap as well, which is already confined via seccomp. I doubt it will have the permission it needs to further sandbox itself. Time will tell though.

kendy · 2020-06-08T09:03:16Z

@thmo Ah makes sense, thank you! We'll disable this in the AppImage build too.

MrReSc · 2020-06-09T04:57:46Z

Get the same on docker won’t connect to the Build in Code Server

OS: Arch Linux x86_64
Host: vServer 20171111
Kernel: 5.6.15-arch1-1
CPU: AMD EPYC (with IBPB) (2) @ 2.495GHz
root:~/ # netstat -lnpt | grep docker                                                                                                            
tcp6       0      0 :::80                   :::*                   LISTEN      docker-proxy    
tcp6       0      0 :::443                 :::*                   LISTEN     docker-proxy    

I still have the same problem. My NC runs as a docker container. Is there a solution for the docker container?

apg1980 · 2020-06-10T04:35:28Z

I have tryed the new release 4.2.404 but i get this in my log (ending up with connection lost to document server):
{ "reqId":"A3si4btPFK6OKzuTOhsO", "level":3, "time":"2020-06-10T05:55:46+02:00", "remoteAddr":"<ip>", "user":"<userid>", "app":"richdocuments", "method":"GET", "url":"/apps/richdocuments/index?fileId=-1&requesttoken=dRlPcBKJrMQ03KKz8fTd0PLdnsfOUU9tXk6UqJByBGk%3D%3AO0o3B0fY245eitfQvpbsnN2VroqdMmQLZwf7msQ3Vlw%3D", "message":{"Exception":"Exception","Message":"","Code":0,"Trace":[{"file":"/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php","line":170, "function":"index","class":"OCA\\Richdocuments\\Controller\\DocumentController","type":"->", "args":["-1",null]},{"file":"/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php", "line":100, "function":"executeController", "class":"OC\\AppFramework\\Http\\Dispatcher","type":"->", "args":[{"__class__":"OCA\\Richdocuments\\Controller\\DocumentController"},"index"]},{"file":"/var/www/nextcloud/lib/private/AppFramework/App.php","line":137,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OCA\\Richdocuments\\Controller\\DocumentController"},"index"]},{"file":"/var/www/nextcloud/lib/private/AppFramework/Routing/RouteActionHandler.php","line":47, "function":"main","class":"OC\\AppFramework\\App","type":"::","args":["OCA\\Richdocuments\\Controller\\DocumentController", "index",{"__class__":"OC\\AppFramework\\DependencyInjection\\DIContainer"},{"_route":"richdocuments.document.index"}]},{"function":"__invoke","class":"OC\\AppFramework\\Routing\\RouteActionHandler", "type":"->","args":[{"_route":"richdocuments.document.index"}]},{"file":"/var/www/nextcloud/lib/private/Route/Router.php","line":297,"function":"call_user_func", "args":[{"__class__":"OC\\AppFramework\\Routing\\RouteActionHandler"},{"_route":"richdocuments.document.index"}]},{"file":"/var/www/nextcloud/lib/base.php", "line":1007, "function":"match","class":"OC\\Route\\Router","type":"->", "args":["/apps/richdocuments/index"]},{"file":"/var/www/nextcloud/index.php","line":37, "function":"handleRequest","class":"OC","type":"::","args":[]}],"File":"/var/www/nextcloud/apps/richdocuments/lib/Controller/DocumentController.php","Line":234,"CustomMessage":"--"}, "userAgent":"Mozilla/5.0 (Linux; Android 10; LYA-L29) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.101 Mobile Safari/537.36","version":"19.0.0.12","id":"5ee0621c3f0aa"}

adrianmihalko · 2020-06-10T06:11:31Z

I tried 404 and it's still not working:

nextgen-networks · 2020-06-10T06:23:04Z

With the update to .404 the CODE builtin server startet working for me on my Plesk 18 environment (Ubuntu 18.04).

juliusknorr · 2020-09-02T06:09:41Z

#57 might help here as well

kgollmer · 2020-09-14T11:47:07Z

I had the same issue but was able to fix it, so may this helps!

fresh and updated CentOS 8 vm, Nextcloud 19.0.1, Collabora 3.7.3 and CODE 4.2.602

executing ./Collabora_Online.AppImage manually in /var/www/html/nextcloud/apps/richdocumentscode/collabora/ did the trick.
Within the Nextcloud settings I had to say "use your own server" and I used the option to not check the certificate, but that's fine for me.

Within the terminal netstat -ldp showed that port 9982 is listening but it looks like after a reboot it doesn't start automatically.

I had to edit /etc/rc.d/rc.local:
vi /etc/rc.d/rc.local

and added this line to the end
cd /var/www/html/nextcloud/apps/richdocumentscode/collabora/ | ./Collabora_Online.AppImage </dev/null &>/dev/null

afterwards made it executable:
chmod +x /etc/rc.d/rc.local

now CODE is autmatically starting and it works like a charm

...sooo - is there any chance in the not-too-distant-future of getting CODE to run using a shared server (I don't have any access to files or console, just the NC backend)?

DrMxxxxx · 2020-09-16T12:41:02Z

So I was also getting

[03-Jun-2020 19:51:14 Europe/Berlin] PHP Warning: fsockopen(): unable to connect to localhost:9982 (Connection refused) in /var/www/server/htdocs/apps/richdocumentscode/proxy.php on line 246

and the lack of any documentation is really frustrating, I had hoped after the onlyoffice debacle with NC18 that wouldn't repeat, at least the news entry for NC19 states that it's only for personal use.

So there are a few prerequisites which looks like they aren't mentioned anywhere - README.md (?).

There's a Collabora_Online.AppImage executable residing in apps/richdocumentscode/collabora.

After trying to manually launch it
su -c "./Collabora_Online.AppImage" -s /bin/bash www-nextcloud

I first got
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
so that's the first prerequisite.

After I installed fuse2 it wouldn't of course run since my kernel didn't include fuse support.
fuse: device not found, try 'modprobe fuse' first
so recompiling the kernel..

Next I got
Failed to load /tmp/.mount_Collabj8lnLI/opt/collaboraoffice6.2/program/libmergedlo.so: libfontconfig.so.1: cannot open shared object file: No such file or directory
after installing fontconfig I could finally launch the AppImage and afterwards it also worked fine from within Nextcloud.

Note: Somewhere along the line I also had to add /proc/1/cgroup to my open_basedir and I also installed the php proxy module, not sure if those are actually required though.

I have exactly the same error message in my NC 19.0.2 docker installation. Is there any way to get this solved sustainable? Because when I do these things and have to delete the container I can do it again in the new one...

elesiuta · 2020-10-05T15:12:42Z

Since I was getting the same error messages as a lot (but not all) the people here and I see no mention of this here, this should help at least some of the people with this issue.

Your server needs to be connected to a router that supports hairpinning (or NAT loopback).

lukas-frey · 2020-10-06T07:38:08Z

Anyone got a solution to this madness? I've got fuse installed, fontconfig installed, port opened, yet it's still saying
fsockopen(): unable to connect to localhost:9982 (Connection refused)

This is frustrating as hell :/

jorgelloret · 2020-10-08T08:46:50Z

Hi!

I managed to make it work by activating open_basedir in PHP

kendy · 2020-10-08T12:43:59Z

@jorgelloret: Oh cool, thanks for the info! @mrkara - can you add a check for that to proxy.php too please?

Jorgesach · 2020-10-14T12:36:22Z

@TheSkrypt
If you have not been able to find the solution, it has worked for me installing fuse, fontconfig and installing the libraries as explained here: coder/code-server#766

after executing ./Collabora_Online.AppImage manually in /var/www/html/nextcloud/apps/richdocumentscode/collabora/

Then I checked in the nextcloud control panel by clicking again on use CODE. And works for me!!

Terrox · 2020-10-14T21:02:18Z

For reference, when I execute AppImage in console on Centos7 get this

$ ./Collabora_Online.AppImage

/tmp/.mount_CollabDfHRVb/AppRun: line 14: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8): No such file or directory

/tmp/.mount_CollabDfHRVb/AppRun: line 14: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)

loolwsd: /lib64/libstdc++.so.6: version 'GLIBCXX_3.4.20' not found (required by loolwsd)

loolwsd: /lib64/libstdc++.so.6: version 'CXXABI_1.3.9' not found (required by loolwsd)

loolwsd: /lib64/libstdc++.so.6: version 'GLIBCXX_3.4.21' not found (required by loolwsd)

ewm0657 · 2020-10-18T02:44:29Z

I made the app image executable, then I started /var/www/html/"my nextcloud path"/apps/richdocumentscode/collabora/Collabora_Online.AppImage on Ubuntu 20.10 with nginx. After that I made the command line in NextCloud http://localhost9982 and it took it locally and worked (locally). This appears to be a HARD code issue, and NOT a nginx issue. Just saying.

Terrox · 2020-10-20T22:58:42Z

I just realised that leaving these addons enabled while they are not working created around 10 log lines per second and my log quickly grew to 10GIG..

Mbee69 · 2020-11-16T18:33:45Z

Hi, I'm facing the connection issue too using the build in CODE Server with message: "Could not establish connection to the Collabora Online server." in the admin.

The ./custom_apps/richdocumentscode/proxy.php?status returns:
status | "starting"

And in the NC Log i found a message:
Error: count(): Parameter must be an array or an object that implements Countable at /var/www/html/custom_apps/richdocuments/lib/Service/CapabilitiesService.php#63

My installation is based on a opensuse host and docker. Nextcloud running behind a nginx proxy companion solution.

Maybe someone can put me in the right direction to use the collabora server

thanks

ewm0657 · 2020-11-16T18:41:09Z

Add a larger pho cache. The default is to small. Eric Morgenstern

…

On Nov 16, 2020, at 1:34 PM, Mbee69 ***@***.***> wrote: Hi, I'm facing the connection issue too using the build in CODE Server with message: "Could not establish connection to the Collabora Online server." in the admin. The ./custom_apps/richdocumentscode/proxy.php?status returns: status | "starting" And in the NC Log i found a message: Error: count(): Parameter must be an array or an object that implements Countable at /var/www/html/custom_apps/richdocuments/lib/Service/CapabilitiesService.php#63 My installation is based on a opensuse host and docker. Nextcloud running behind a nginx proxy companion solution. Maybe someone can put me in the right direction to use the collabora server thanks — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Mbee69 · 2020-11-16T19:02:21Z

Add a larger pho cache. The default is to small. Eric Morgenstern
…
On Nov 16, 2020, at 1:34 PM, Mbee69 @.***> wrote: Hi, I'm facing the connection issue too using the build in CODE Server with message: "Could not establish connection to the Collabora Online server." in the admin. The ./custom_apps/richdocumentscode/proxy.php?status returns: status | "starting" And in the NC Log i found a message: Error: count(): Parameter must be an array or an object that implements Countable at /var/www/html/custom_apps/richdocuments/lib/Service/CapabilitiesService.php#63 My installation is based on a opensuse host and docker. Nextcloud running behind a nginx proxy companion solution. Maybe someone can put me in the right direction to use the collabora server thanks — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Hi Eric, Realy? Thats my only problem? :D Thanks for your quick replay. I will have a try on it. cheers Ben

ewm0657 · 2020-11-16T19:11:29Z

Let me know. Eric Morgenstern

…

On Nov 16, 2020, at 2:02 PM, Mbee69 ***@***.***> wrote: Add a larger pho cache. The default is to small. Eric Morgenstern … On Nov 16, 2020, at 1:34 PM, Mbee69 @.***> wrote: Hi, I'm facing the connection issue too using the build in CODE Server with message: "Could not establish connection to the Collabora Online server." in the admin. The ./custom_apps/richdocumentscode/proxy.php?status returns: status | "starting" And in the NC Log i found a message: Error: count(): Parameter must be an array or an object that implements Countable at /var/www/html/custom_apps/richdocuments/lib/Service/CapabilitiesService.php#63 My installation is based on a opensuse host and docker. Nextcloud running behind a nginx proxy companion solution. Maybe someone can put me in the right direction to use the collabora server thanks — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Hi Eric, Realy? Thats my only problem? :D Thanks for your quick replay. I will have a try on it. cheers Ben — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Wotisrv · 2020-11-22T08:00:18Z

Hi!

I managed to make it work by activating open_basedir in PHP

What did you do?

Terrox · 2020-11-22T23:42:47Z

I can't change open_basedir on FPM

Mbee69 · 2020-11-29T16:02:30Z

Let me know. Eric Morgenstern
…
On Nov 16, 2020, at 2:02 PM, Mbee69 @.> wrote: Add a larger pho cache. The default is to small. Eric Morgenstern … On Nov 16, 2020, at 1:34 PM, Mbee69 @.> wrote: Hi, I'm facing the connection issue too using the build in CODE Server with message: "Could not establish connection to the Collabora Online server." in the admin. The ./custom_apps/richdocumentscode/proxy.php?status returns: status | "starting" And in the NC Log i found a message: Error: count(): Parameter must be an array or an object that implements Countable at /var/www/html/custom_apps/richdocuments/lib/Service/CapabilitiesService.php#63 My installation is based on a opensuse host and docker. Nextcloud running behind a nginx proxy companion solution. Maybe someone can put me in the right direction to use the collabora server thanks — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Hi Eric, Realy? Thats my only problem? :D Thanks for your quick replay. I will have a try on it. cheers Ben — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Hi Eric,
i did a big change on my docker configuration, switching the nc-apache image to the nc-fpm. Managed do make all working, collabora code response on the path. But collabora online does not recognize it. So collabora code still does not work.
The error message in the log is gone, so i think it was not related to the collabora issue.
Ben

ewm0657 · 2020-11-29T18:01:43Z

Check out file permissions and ownership. I read yesterday about changing the permissions. I just have not gotten that far again. I changed to OpenOffice from Collabra to get it working while I pursued some DR strategies. The FPM is a good call, I used that as part of my install already. Had issues with file sizes but managed to get that resolved. Eric Morgenstern

…

On Nov 29, 2020, at 11:02 AM, Mbee69 ***@***.***> wrote: Let me know. Eric Morgenstern … On Nov 16, 2020, at 2:02 PM, Mbee69 @.> wrote: Add a larger pho cache. The default is to small. Eric Morgenstern … On Nov 16, 2020, at 1:34 PM, Mbee69 @.> wrote: Hi, I'm facing the connection issue too using the build in CODE Server with message: "Could not establish connection to the Collabora Online server." in the admin. The ./custom_apps/richdocumentscode/proxy.php?status returns: status | "starting" And in the NC Log i found a message: Error: count(): Parameter must be an array or an object that implements Countable at /var/www/html/custom_apps/richdocuments/lib/Service/CapabilitiesService.php#63 My installation is based on a opensuse host and docker. Nextcloud running behind a nginx proxy companion solution. Maybe someone can put me in the right direction to use the collabora server thanks — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Hi Eric, Realy? Thats my only problem? :D Thanks for your quick replay. I will have a try on it. cheers Ben — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Hi Eric, i did a big change on my docker configuration, switching the nc-apache image to the nc-fpm. Managed do make all working, collabora code response on the path. But collabora online does not recognize it. So collabora code still does not work. The error message in the log is gone, so i think it was not related to the collabora issue. Ben — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Mbee69 · 2020-11-30T15:54:04Z

Hi @ewm0657 ,

I found here on reply from "Cor Nouws", that my issue may be related to the stable-fpm-alpine image. It looks like alpine image is not supported, because it uses musl libc instead of glibc, and AppImage does not support muls libc yet.
I don't know if he is right but i think it worth to mention here.

Permissions and ownership are ok.

Cheers Ben

maste9 · 2020-12-01T10:37:13Z

@kendy As I'm running into the same problem at the moment with a fresh nc20 instance - did you solve this port problem lately?

@MrReSc @pheiduck: OK, after a long struggle, I've finally managed to reproduce this & find out what is the root of the problem: It is that the apache is running on :80 inside the docker, but mapped to :8080 from the outside. So the check that we do inside fails because it tries to reach the :8080 from inside - which returns a 404 of course.

We have a solution in mind, but it'll take a bit of time to implement I fear; let's see...

pheiduck · 2020-12-01T12:24:58Z

@kendy As I'm running into the same problem at the moment with a fresh nc20 instance - did you solve this port problem lately?

@MrReSc @pheiduck: OK, after a long struggle, I've finally managed to reproduce this & find out what is the root of the problem: It is that the apache is running on :80 inside the docker, but mapped to :8080 from the outside. So the check that we do inside fails because it tries to reach the :8080 from inside - which returns a 404 of course.
We have a solution in mind, but it'll take a bit of time to implement I fear; let's see...

@maste9 Yep, not a real solution, but I switched to the snap

b3nis · 2021-01-26T23:12:52Z

Seems to be semi-working in 20.0.6 - but new bug has arised!

https://github.com/nextcloud/server/issues/25339

timar · 2021-03-21T18:37:12Z

Let's close this, then.

hoshi411 · 2023-09-16T15:11:44Z

nope. still broken

gsanchietti mentioned this issue Jun 4, 2020

Nextcloud 19.0.0 NethServer/dev#6178

Closed

tgurr mentioned this issue Jun 4, 2020

Add more system requirements #28

Merged

kyrofa mentioned this issue Jun 5, 2020

nextcloud: update to 19.0.0 nextcloud-snap/nextcloud-snap#1353

Merged

olegchensky mentioned this issue Jun 8, 2020

Compatibility with NC 19 nextcloud/documentserver_community#144

Closed

mrkara self-assigned this Oct 14, 2020

danielrheinbay mentioned this issue Nov 16, 2020

Could not establish connection to the Collabora Online server #89

Closed

kyrofa mentioned this issue Dec 9, 2020

RichDocuments built-in CODE causes significant slowdown/timeout issues nextcloud/richdocuments#1282

Closed

timar closed this as completed Mar 21, 2021

gdamjan mentioned this issue Jan 27, 2022

Installing the "Collabora Online - Built-in CODE Server" blocks the service gdamjan/nextcloud-service#2

Open

NC 19 unable to Use Build in Code Server #26

NC 19 unable to Use Build in Code Server #26

Comments

apg1980 commented Jun 3, 2020

Server details

Nextcloud log (data/nextcloud.log)

Ecphrasis commented Jun 3, 2020

nextgen-networks commented Jun 3, 2020

nextgen-networks commented Jun 3, 2020 • edited Loading

tgurr commented Jun 3, 2020 • edited Loading

kendy commented Jun 3, 2020

kendy commented Jun 3, 2020 • edited Loading

nextgen-networks commented Jun 3, 2020

Ecphrasis commented Jun 4, 2020

apg1980 commented Jun 4, 2020

4001982248998 commented Jun 4, 2020

apg1980 commented Jun 4, 2020

domchrgit commented Jun 4, 2020

kyrofa commented Jun 5, 2020

pheiduck commented Jun 5, 2020 • edited Loading

kyrofa commented Jun 5, 2020

kendy commented Jun 5, 2020

kyrofa commented Jun 5, 2020 • edited Loading

kendy commented Jun 5, 2020

kyrofa commented Jun 5, 2020

thmo commented Jun 6, 2020

kyrofa commented Jun 6, 2020 • edited Loading

kendy commented Jun 8, 2020

MrReSc commented Jun 9, 2020

apg1980 commented Jun 10, 2020 • edited Loading

adrianmihalko commented Jun 10, 2020

nextgen-networks commented Jun 10, 2020

juliusknorr commented Sep 2, 2020

kgollmer commented Sep 14, 2020

DrMxxxxx commented Sep 16, 2020

elesiuta commented Oct 5, 2020 • edited Loading

lukas-frey commented Oct 6, 2020

jorgelloret commented Oct 8, 2020

kendy commented Oct 8, 2020

Jorgesach commented Oct 14, 2020

Terrox commented Oct 14, 2020 • edited Loading

ewm0657 commented Oct 18, 2020

Terrox commented Oct 20, 2020

Mbee69 commented Nov 16, 2020

ewm0657 commented Nov 16, 2020 via email

Mbee69 commented Nov 16, 2020

ewm0657 commented Nov 16, 2020 via email

Wotisrv commented Nov 22, 2020

Terrox commented Nov 22, 2020

Mbee69 commented Nov 29, 2020

ewm0657 commented Nov 29, 2020 via email

Mbee69 commented Nov 30, 2020

maste9 commented Dec 1, 2020

pheiduck commented Dec 1, 2020 • edited Loading

b3nis commented Jan 26, 2021

timar commented Mar 21, 2021

hoshi411 commented Sep 16, 2023

nextgen-networks commented Jun 3, 2020 •

edited

Loading

tgurr commented Jun 3, 2020 •

edited

Loading

kendy commented Jun 3, 2020 •

edited

Loading

pheiduck commented Jun 5, 2020 •

edited

Loading

kyrofa commented Jun 5, 2020 •

edited

Loading

kyrofa commented Jun 6, 2020 •

edited

Loading

apg1980 commented Jun 10, 2020 •

edited

Loading

elesiuta commented Oct 5, 2020 •

edited

Loading

Terrox commented Oct 14, 2020 •

edited

Loading

pheiduck commented Dec 1, 2020 •

edited

Loading