Use Onlyoffice on cloudron1 with Nextcloud on cloudron2?
-
From a message in a different thread, I know Onlyoffice will work out of the box with Nextcloud on the same cloudron, but can it be configured to work with a Nextcloud on another cloudron?
Thanks.
-
@ei8fdb You gotta add the domain to the allowed section on onlyoffice(Shown as
OOhere):- install OO on cloudron1
- once installed, click the app and load the web ui, login, and put
[a-zA-Z0-9_\-.]*cloudron2fqdn(Example:[a-zA-Z0-9_\-.]*example.com) (Yes, EXACTLY how it shows there.) - save
- login to nextcloud on cloudron2, admin -> apps -> Install the OO app, then admin settings -> OO Settings -> Domain of the cloudron1 OO install.
-
-
@ei8fdb Can you not put any OO installation domain + secret in https://docs.cloudron.io/apps/onlyoffice/#setup-nextcloud-connector ?
-
-
@girish I've tried that. In the Nextcloud (on coudron2) instance I get the following error:
Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 6.4.2.6)✖While in the OnlyOffice server (on cloudron1) I get the following error in the logs:
Oct 23 02:29:09 [2021-10-23T00:29:09.546] [ERROR] nodeJS - error downloadFile:url=https://cloudron2.domain.com/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.S3x69FuWZ16D_4dqy7koy3tzfCXf0IiAlQOBmEd13r0;attempt=3;code:null;connect:null;(id=conv_check_804935328_docx) Oct 23 02:29:09 Error: Error response: statusCode:403; headers:{"server":"nginx","date":"Sat, 23 Oct 2021 00:38:08 GMT","content-type":"application/json; charset=utf-8","content-length":"27","connection":"keep-alive","set-cookie":["ocypgodjzaf9=h5kjo6g6kcocjagn9ds8nj9v3p; path=/; secure; HttpOnly; SameSite=Lax","oc_sessionPassphrase=1SK19T4Oade2po3d04CvEsxahHofKmCp8w0jWGpbO8WIwNX%2FnNkdDik%2FJA1ZiazwMznzZTFgI4CPtzGV8tIrVeEQJWKsOoztxZep%2BlwPe8VXnDDb1We7wGq3F5ksQp4%2F; path=/; secure; HttpOnly; SameSite=Lax","ocypgodjzaf9=v3ihf0ebst67eq5mg0ndtnkmcn; path=/; secure; HttpOnly; SameSite=Lax","__Host-nc_sameSiteCookielax=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax","__Host-nc_sameSiteCookiestrict=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict"],"expires":"Thu, 19 Nov 1981 08:52:00 GMT","cache-control":"no-cache, no-store, must-revalidate","pragma":"no-cache","content-security-policy":"default-src 'none';base-uri 'none';manifest-src 'self';frame-ancestors 'none'","x-frame-options":"SAMEORIGIN","x-robots-tag":"none","feature-policy":"autoplay 'none';camera 'none';fullscreen 'none';geolocation 'none';microphone 'none';payment 'none'"}; body: Oct 23 02:29:09 {"message":"Access denied"} Oct 23 02:29:09 at Request._callback (/snapshot/server/build/server/Common/sources/utils.js:0:0) Oct 23 02:29:09 at Request.init.self.callback (/snapshot/server/build/server/Common/node_modules/request/request.js:185:22) Oct 23 02:29:09 at Request.emit (events.js:198:13) Oct 23 02:29:09 at Request.<anonymous> (/snapshot/server/build/server/Common/node_modules/request/request.js:1154:10) Oct 23 02:29:09 at Request.emit (events.js:198:13) Oct 23 02:29:09 at IncomingMessage.<anonymous> (/snapshot/server/build/server/Common/node_modules/request/request.js:1076:12) Oct 23 02:29:09 at Object.onceWrapper (events.js:286:20) Oct 23 02:29:09 at IncomingMessage.emit (events.js:203:15) Oct 23 02:29:09 at endReadableNT (_stream_readable.js:1145:12) Oct 23 02:29:09 at process._tickCallback (internal/process/next_tick.js:63:19) Oct 23 02:29:15 2021-10-23 00:29:15,556 INFO reaped unknown pid 18413 Oct 23 02:29:15 2021-10-23 00:29:15,556 INFO reaped unknown pid 18413 Oct 23 02:29:15 2021-10-23 00:29:15,557 INFO reaped unknown pid 18414 Oct 23 02:29:15 2021-10-23 00:29:15,557 INFO reaped unknown pid 18414 Oct 23 02:29:15 2021-10-23 00:29:15,557 INFO reaped unknown pid 18448 Oct 23 02:29:15 2021-10-23 00:29:15,557 INFO reaped unknown pid 18448 Oct 23 02:29:15 2021-10-23 00:29:15,557 INFO reaped unknown pid 18418 Oct 23 02:29:15 2021-10-23 00:29:15,557 INFO reaped unknown pid 18418I had presumed
Oct 23 02:29:09 {"message":"Access denied"}was a result of the cloudron2 nextcloud not having access to the cloudron1 OnlyOffice server.I've confirmed the secret on the nextcloud server matches that in the json config.
-
-
-
@murgero said in Use Onlyoffice on cloudron1 with Nextcloud on cloudron2?:
@ei8fdb Oh, change the secret key
/app/data/config/production-linux.json(2 places to change it in the file!!!)Yup, done that.
Then add the domain you installed OO on cloudron1 to nextcloud on cloudron2 in the nextcloud OO app.
This is where the errors I've mentioned above occur.
-
I've been wondering about this too, so I just did a little test.
All I needed to do was to copy the URL and secret at nexcloudurl.coop/settings/admin/onlyoffice from the Nextcloud on Cloudron1 over to the Nextcloud on Cloudron2 and as far as I can tell I had OnlyOffice working (I created a new doc and typed some text).
I didn't need to do anything in the OnlyOffice app on Cloudron1 (indeed, I don't think I've ever had to touch that since installing it).
-
@girish said in Use Onlyoffice on cloudron1 with Nextcloud on cloudron2?:
@ei8fdb Can you not put any OO installation domain + secret in https://docs.cloudron.io/apps/onlyoffice/#setup-nextcloud-connector ?
Yes, that is correct. At least, that's all I had to do just now and it seemed to work fine. I didn't get any errors.
-
@jdaviescoates said in Use Onlyoffice on cloudron1 with Nextcloud on cloudron2?:
Yes, that is correct. At least, that's all I had to do just now and it seemed to work fine. I didn't get any errors.
Hmm interesting. Would you be willing to give me temporary access to that OO server so I can test? I promise not to write too many documents.
I wonder if it's due to me hosting the OO server on my home server and trying to access it from my company VPS-hosted Nextcloud (hosted on Cloudron).
-
@ei8fdb I also don't seem to be able to reproduce this here. Just to rule out anything obvious, for both collabora or onlyoffice + nextcloud both parties have to be able to reach themselves. So make sure there are no external firewalls or such blocking the oo app to connect to nextcloud and vice-versa. Otherwise the original error looks like the secret is wrong actually. Also likely obvious but just to be safe, when the secret is changed on the app side, it has to be restarted.
-
@nebulon said in Use Onlyoffice on cloudron1 with Nextcloud on cloudron2?:
@ei8fdb I also don't seem to be able to reproduce this here. Just to rule out anything obvious, for both collabora or onlyoffice + nextcloud both parties have to be able to reach themselves. So make sure there are no external firewalls or such blocking the oo app to connect to nextcloud and vice-versa.
@nebulon just checking - is it possible to ping from the OpenOffice terminal? I tried but get:
root@openoffice-container-id:/usr/bin# ping bash: /usr/bin/ping: Operation not permittedI can ping the Nextcloud server from the OO server cloudron server, and vice-versa.
1. bernat@cloudron1:~$ ping nextcloud.cloudron2 PING nextcloud.cloudron2 (AAA.BBB.CCC.DDD) 56(84) bytes of data. 64 bytes from nextcloud.cloudron2 (AAA.BBB.CCC.DDD): icmp_seq=1 ttl=52 time=27.4 ms 2. root@cloudron2:~# ping ootest.cloudron1 PING ootest.cloudron1 (EEE.FFF.GGG.HHH) 56(84) bytes of data. 64 bytes from EEE.FFF.GGG.HHH: icmp_seq=1 ttl=53 time=27.3 msOtherwise the original error looks like the secret is wrong actually. Also likely obvious but just to be safe, when the secret is changed on the app side, it has to be restarted.
I didn't change the secret on the test OO server so it's not caused a wrong password.
@nebulon - could I give you temporary access to my test OO server and see if you can use it?
I'm at a loss to where the issue is.
