CODE built-in for collabora and custom port

[Multipass]

The Basics

Nextcloud version : 28.0.11
Operating system and version : Linux 6.6.18 aarch64
Apache or nginx version : Apache 2.4.62 (Debian)
PHP version : 8.1.29

Summary of the issue you are facing:

I’m using the CODE built-in for collabora. Everything was working fine. I decided to use custom port for my server. I updated my router to open another port let’s say XXXX to 443.

I updated the CODE built-in element, everything seems OK : it updated with the custom port and is showing : “Collabora Online server is reachable.”

BUT… I can’t open .odt, .ods… Althought .png, .pdf, .md are fine.

I tried updating the WOPI thing, but even making it blank or with 0.0.0.0/0, it doesn’t work.

Do I need to update something somewhere else ? Or is the issue maybe not related to the port change ?

Reading this : Proxy settings — SDK https://sdk.collaboraonline.com/ documentation

I’m stopped at the very first step : there is no Collabora Online’s configuration file here : /etc/coolwsd/coolwsd.xml.

Actually, I don’t even have a coolwsd folder in /etc/…

[wwe]

likely you broke the integration.

@Multipass

I’m using the CODE built-in for collabora. Everything was working fine. I decided to use custom port for my server. I updated my router to open another port let’s say XXXX to 443.

why do you do this? as collabora-built-in is by design made available through an integrated “reverse proxy” component you would have adjusted this one as well… but in general I would recommend to keep it using the default port there is no good reason to change it.

Please review Collabora integration guide to fully understand the integration.

[Multipass]

Well, I’d like to use non standard port for my server… So not the usual 80 or 443 (I mean for the outside world).

Since I’m using it on a RPi, I had to update de check URL like this :

https://mydomain.cloud.net:XXXX/apps/richdocumentscode_arm64/proxy.php?req=/hosting/capabilities

• XXXX being my custom port
• richdocumentscode_arm64 being where the Collabora code is (I guessed, since I don’t have a richdocumentscode folder)

Then I can see it’s all up and running.

So I guess the question is : how can I adjust the integrated “reverse proxy” component to make it work with my custom port ?

And, do I need to change something somewhere to specify the “_arm64” for the folder name ?

[wwe]

@Multipass

So I guess the question is : how can I adjust the integrated “reverse proxy” component to make it work with my custom port ?

I suppose this is not intended and not supported. Go the hard way read, understand and change the code. repeat after every update.

[Multipass]

So are you saying that no-one using the Build-in CODE uses custom ports for their Nextcloud setup ?

Now, I read that if I want to use my own server for Collabora : Nextcloud Office requires a separate server running Collabora Online to provide editing capabilities. Collabora Online requires a separate server acting as a WOPI-like Client to provide editing capabilities.

Can this be on the same “physical” machine, but a subdomain ? Like I see mentionned for exemple *office*.mycloud.net in some of the guides ? This way I should be able to add specific elements in the VirtualHost stuff, like my custom port, right ?

[Multipass]

Seems my problem is coming from seomthing else, cause I have the same issue even if I go back to the regular 443 port…

[Multipass]

My bad… Sorry for that… I just saw I had a pending update for Collabora, and everything is working fine now