Collabora
Collabora Online Development Edition 4.0 RC2
In loolwsd.xml I set the path directly to the letsencrypt certificates. The file properties are set such, that there should be no Permission denied, especially as there is no error message related to privkey and chain.
<cert_file_path desc="Path to the cert file" relative="false">/opt/dehydrated-master/certs/wo-lar.com/cert.pem>
<key_file_path desc="Path to the key file" relative="false">/opt/dehydrated-master/certs/wo-lar.com/privkey.pem>
<ca_file_path desc="Path to the ca file" relative="false">/opt/dehydrated-master/certs/wo-lar.com/fullchain.pem>
I went through the forum here and als googled, but cannot find anything.
That is the reason I hope to find here a solution.
A question: Do I need a sub-domain or can i run nextcloud and collabora on the same domain?
You can run them on the same server but you will need two subdomains. One for collabora and for nextcloud. Think of them as two different websites on the same server.
Your Loolwsd file ca error can be handled by doing a self assigned cert or using cetbot or the certs you created for Apache when you set up the SSL conf file. Or you can turn off ssl in the loolwsd.xml file.
To turn off ssl go to the loolwsd file then find "ssl desc=“SSL settings” header. Under this header you will find the below line. Change the default true to false. resave and run sudo systemctl restart loolwsd.
<termination desc="Connection via proxy where loolwsd acts as working via https, but actually uses http." type="bool" default="true">true</termination>
generate self-signed cert
openssl genrsa -out /etc/loolwsd/privatekey.pem 4096
openssl req -batch -new -x509 -sha512 -days 3650 -key /etc/loolwsd/privatekey.pem -out /etc/loolwsd/fullchain.pem
loolconfig set ssl.cert_file_path /etc/loolwsd/fullchain.pem
loolconfig set ssl.key_file_path /etc/loolwsd/privatekey.pem
loolconfig set ssl.ca_file_path ‘’
loolconfig set storage.wopi.host subname.domian.com
email
agree to Terms of Service
Y or N to sharing your email address with the Electronic Frontier Foundation
select 2: Redirect - Make all requests redirect to secure HTTPS access.
Note the location of your cert it will be needed later.
If using these new certs for the Loolwsd file you may have to copy them to the /etc/loolwsd folder
The /etc/letsencrypt/live/ file path does not have the same permissions.
You will also need to grab the Intermediate Certificates from letsencrypt