Collabora/Code not working, WOPI not found / unauthorized

Seafile Server
1

I have just updated my seafile server from 8.x to v9.0.4. Now the collabora integration is broken.
At first collabora did not want to start because of some new environment variables in collabora/code:

docker run -d --rm -p 9980:9980 -e "aliasgroup1=seafile\\.mydomain\\.com" -e "server_name=collabora\\.mydomain\\.com" --cap-add MKNOD collabora/code

Trying to open any file with collabora results in 404 of the url

POST
https://collabora.mydomain.com/browser/eb73aa3/cool.html?WOPISrc=https://seafile.mydomain.com/api2/wopi/files/9de7dae237d94e47e978df3511e542b350f57882&ui=de-DE&rs=de-DE

My search in the collabora docs leads to the proxy settings which are outdated in the current seafile documentation.
For all that have the same Problems have a look at Proxy settings — SDK https://sdk.collaboraonline.com/ documentation

After fixing the proxy settings another problem shows up.
Sometimes it is shown something like “document of the last meeting is cleaned up”
The WS-Connection gets closed with the reason:

Connection Closed: 1008 error: cmd=internal kind=unauthorized

Any ideas?

2

Does nobody knows whats wrong with the authentication?

@daniel.pan @Jonathan

3

We will check whether Seafile can work with the latest Collabora/Code.

4

thanks :slight_smile:

5

With Seafile 9.0.5 it’s still not working

6

Hello, I just deployed the Collabora CODE 22.05 on our demo site (9.0.4 pro): https://demo.seafile.top/demo

It works fine.

The command I used to start a Collabora CODE docker container is:
CODE Docker image — SDK https://sdk.collaboraonline.com/ documentation.

docker run -t -d -p 127.0.0.1:9980:9980 -e "aliasgroup1=https://demo.seafile.top:443" -e "username=***" -e "password=***" --name code --restart always collabora/code

The nginx conf on the Collabora CODE server is:
https://sdk.collaboraonline.com/docs/installation/Proxy_settings.html#reverse-proxy-with-nginx-webserver

server {
 listen       443 ssl;
 server_name  collaboraonline.example.com;


 ssl_certificate /path/to/certificate;
 ssl_certificate_key /path/to/key;


 # static files
 location ^~ /browser {
   proxy_pass https://127.0.0.1:9980;
   proxy_set_header Host $http_host;
 }


 # WOPI discovery URL
 location ^~ /hosting/discovery {
   proxy_pass https://127.0.0.1:9980;
   proxy_set_header Host $http_host;
 }


 # Capabilities
 location ^~ /hosting/capabilities {
   proxy_pass https://127.0.0.1:9980;
   proxy_set_header Host $http_host;
 }


 # main websocket
 location ~ ^/cool/(.*)/ws$ {
   proxy_pass https://127.0.0.1:9980;
   proxy_set_header Upgrade $http_upgrade;
   proxy_set_header Connection "Upgrade";
   proxy_set_header Host $http_host;
   proxy_read_timeout 36000s;
 }


 # download, presentation and image upload
 location ~ ^/(c|l)ool {
   proxy_pass https://127.0.0.1:9980;
   proxy_set_header Host $http_host;
 }


 # Admin Console websocket
 location ^~ /cool/adminws {
   proxy_pass https://127.0.0.1:9980;
   proxy_set_header Upgrade $http_upgrade;
   proxy_set_header Connection "Upgrade";
   proxy_set_header Host $http_host;
   proxy_read_timeout 36000s;
 }
}
7

I have updated to the latest Collabora and seafile server versions, now it works. I have not changed any settings, so it might have been a bug in an older version.

Thanks :slight_smile: