Question Collabora in Docker Container

[Larsm]

Hello,

i start to using plesk Onyx with Docker Container and Nextcloud.
Collabora is succesful startet. and listen to an port. But i can get it work with Nextcloud:

:cURL error 7: Failed connect to localhost:9980; Connection refused

is the message from Nextcloud

Collabora tells me this in the Logs:

wsd-00024-00 00:00:00.000341 [ loolwsd ] Initializing wsd
wsd-00024-00 00:00:00.000396 [ loolwsd ] Log level is [8].
wsd-00024-00 00:00:00.000944 [ loolwsd ] SSL support: SSL is enabled.
wsd-00024-00 00:00:00.001005 [ loolwsd ] Launch this in your browser:
wsd-00024-00 00:00:00.001026 [ loolwsd ]     https://localhost:9980/loleaflet/1.8.4/loleaflet.html?file_path=file:///usr/bin/test/data/hello-world.odt

Why localhost? i set an domain as Variable.

https://nextcloud.com/collaboraonline/

Can anyone help me?

best regards

Lars

 

[IgorG]

Why localhost? i set an domain as Variable.

You set DOMAIN, but what about domain? It is localhost.

 

[Larsm]

I try to set domain but I get this error

 

[IgorG]

Could you post is as plain text here at least? I can't translate it from the picture.
Or better in English, if possible.

 

[Larsm]

Could you post is as plain text here at least? I can't translate it from the picture.
Or better in English, if possible.

Sure, it tells me that only uppercase letters are possible.

 

[IgorG]

Yes, I confirm that it is bug. We do not allow to use lowercase in names of Docker settings, but Collabora requires it in your case.
I have forwarded this issue to developers. We will fix it in one of nearest updates.

 

[Larsm]

Can I manually edit the domain?

 

[IgorG]

Can I manually edit the domain?

Just re-create container with docker command and corresponding parameters.

 

[cij]

Hi all,

any updates on this? The issue is still existing with the upper and lower cases letters for the 'domain' name on the collabora docker. Is an fix already in the pipeline?

Thanks

 

[gillesps]

Hello everyone,
So saying that it is a bug is not enough.... when it will be correct. I Pay to get Plesk so I attend to get it right else i want my money back!
Thank you
Regards

 

[IgorG]

So saying that it is a bug is not enough.... when it will be correct. I Pay to get Plesk so I attend to get it right else i want my money back!

Have you contacted Plesk Support Team regarding this issue? Have you received a solution that suits you?

 

[IgorG]

any updates on this?

Should be fixed in upcoming Docker 1.3.2 Plesk extension.

 

[IgorG]

Could someone provide us with steps to reproduce this issue?
Desirable in as much detail as possible.
Thanks.

 

[Zumpel]

I've got the same issue.

You don't need much detail.
1. in plesk click docker in the left menu (last item)
2. use the search bar and enter collabora/code
3. run the collabora image

it will now ask for settings with pre-entered settings. There is a lowercase "domain". You will be unable to change this item because plesk will alert that you are just allowed to user uppercase. that's all. you can't use the container, because you can't define the parameters in plesk.
i would suggest two steps: first: make this test just a warning or remove it, if it's bullshit
second: allow to add command line parameters so we are always able to use more specific docker features

 

[Zumpel]

as you can see there is also a mistake in the helptext with the "'"

 

[Guido Behet]

Something new about the release of docker 1.3.2?

 

[Zoo3]

Please let me question as well.

1. How can I open a specific port via Plesk's UI and create a container? ex. 9980:9980
   

   docker run -t -d -p 9980:9980 -e "domain=sample\\.domain\\.com" --cap-add MKNOD collabora/code

2. This may not be Plesk's question. There are "lool and loleaflet, hosting" settings in the setting of nginx reverse proxy. In the case of Plesk, how do you specify these? ex. location ~ ^/lool
   

   location ~ ^/lool {
       proxy_pass https://localhost:9980;
       proxy_set_header Host $http_host;
   }

 

[Larsm]

Please let me question as well.

1. How can I open a specific port via Plesk's UI and create a container? ex. 9980:9980
   

   docker run -t -d -p 9980:9980 -e "domain=sample\\.domain\\.com" --cap-add MKNOD collabora/code

2. This may not be Plesk's question. There are "lool and loleaflet, hosting" settings in the setting of nginx reverse proxy. In the case of Plesk, how do you specify these? ex. location ~ ^/lool
   

   location ~ ^/lool {
       proxy_pass https://localhost:9980;
       proxy_set_header Host $http_host;
   }

Have a look here. Collabora Online Office – Nextcloud all setup steps explained.

Gesendet von meinem Nexus 5X mit Tapatalk

 

[virtubox]

Please let me question as well.

1. How can I open a specific port via Plesk's UI and create a container? ex. 9980:9980
   

   docker run -t -d -p 9980:9980 -e "domain=sample\\.domain\\.com" --cap-add MKNOD collabora/code

2. This may not be Plesk's question. There are "lool and loleaflet, hosting" settings in the setting of nginx reverse proxy. In the case of Plesk, how do you specify these? ex. location ~ ^/lool
   

   location ~ ^/lool {
       proxy_pass https://localhost:9980;
       proxy_set_header Host $http_host;
   }

Hello @Zoo3 , I have already setup collabora online using docker with NextCloud (without Plesk) but when I have tried to run the container directly from the Plesk interface, I haven't found a way to expose the port 9980. So it will require to use the command line to do so.

For the settings to use, here the docker container command and the nginx configuration : Collabora online for NextCloud with Docker and Nginx · GitHub
But I don't know if it will be easy to do the same on Plesk.

 

[Zoo3]

Thank you for reply.

For the settings to use, here the docker container command and the nginx configuration : Collabora online for NextCloud with Docker and Nginx · GitHub
But I don't know if it will be easy to do the same on Plesk.

I'm typing that way. However, even if the office application main unit is started, data can't be opened.
The reverse proxy setting for that link is entered in the "Website domain > Apache and nginx settings > nginx additional directive" field.
I ignored it even if I wrote it in /etc/nginx/nginx.conf. I write the SSL relationship to nginx.conf and write the location statement in the nginx additional directive of the collabora domain. Is this wrong? *I can't operate font selection, style setting, etc.