Hi @stephdl
I would like to report the same effect (Collabora neu installed).
My 2 cents
And best wishes for the season!
Andy
2 Likes
fun, nothing in logs @Andy_Wismer
1 Like
Salut @stephdl
What logs exactly do you need - and where do I find them?
I am aware about the âlogsâ section. I should be able to retrieve them there.
My 2 cents
Andy
I think what we need to understand is why it does not work when in nextcloud you try to access to collabora to edit a file, so do it and check journald
journalctl -f
however do you have enable lets encrypt for both collabora and nextcloud ?
Salut @stephdl
Yes, I have LE enabled for both.
To be honest, the first time I activated Collabora without LE (forgot it) but NextCloud has always used LE.
I changed LE for Collabora, LE is now good.
But the App opens up and starts loading the file, but never finishes rotating / loading.
Now, I canât even open the Collabora Console:
The site resolves correctly:
172.25.90.20 is my NS8 (awr9-ns8)âŠ
LE looks goodâŠ
But a whole load of errors - probably due to the LE mistake I made and later correctedâŠ
Errors are shown in the Log of CollaboraâŠ
What do you think?
Worth it to remove Collabora and reinstall it?
Or track the issue?
My 2 cents
Andy
yes but the concern is a collabora dns error, reinstall and try to ask for a new dns name, maybe LE is confused
collabora2.domain.com must be a real dns A record at your dns provider to request a letâsencrypt certificate
collabora2.domain.com must be a real dns A record at your dns provider to request a letâsencrypt certificate
This is correct, LE provides no error when creating one.
Collabora is an âAâ record on my internal DNS (It is also on my external DNS, there as a CNAME.)
But I also see this in Nextcloud:
Your browser has been unable to connect to the Collabora server: https://collabora.r9.anwi.ch
This URL is determined on the Collabora server either from the configured URL or the server_name parameter in coolwsd.xml.
It did connect, the first days after I enabled LE, but would not work.
I will attempt a reinstall of Collabora - a VM in Proxmox can easily be backupped quickly and restored in worst case. With PBS this is fast.
I will attempt this over lunch, this is my home server, so no issues.
But until lunch, I still need to do some work! 
Exceerpts from the Collabora log:
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] Server: COOLWSD HTTP Server 24.04.7.1
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] Upgrade: websocket
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] Connection: Upgrade
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] Sec-WebSocket-Accept: IksVnKNBm3o03ToWP/op6vpJqrM=
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] | net/WebSocketHandler.hpp:990
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] wsd-00001-00022 2024-12-30 09:38:10.570936 +0000 [ prisoner_poll ] TRC #17: Wrote 201 bytes of 201 buffered data| net/Socket.hpp:1489
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] Ready to accept connections on port 9980.
2024-12-30T10:38:10+01:00 [1:collabora1:collabora]
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] wsd-00001-00001 2024-12-30 09:38:10.571078 +0000 [ coolwsd ] TRC Have 1 new children.| wsd/COOLWSD.cpp:4430
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] wsd-00001-00001 2024-12-30 09:38:10.571105 +0000 [ coolwsd ] INF WSD initialization complete: setting log-level to [warning] as configured.| wsd/COOLWSD.cpp:4445
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] wsd-00001-00001 2024-12-30 09:38:10.572717 +0000 [ coolwsd ] WRN Waking up dead poll thread [main], started: false, finished: false| net/Socket.hpp:724
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] frk-00023-00023 2024-12-30 09:38:10.573947 +0000 [ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:557
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] frk-00023-00023 2024-12-30 09:38:10.581174 +0000 [ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:557
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] kit-00033-00033 2024-12-30 09:38:10.582090 +0000 [ kit_spare_002 ] WRN Security warning: running without chroot jails is insecure.| kit/Kit.cpp:3315
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] frk-00023-00023 2024-12-30 09:38:10.589285 +0000 [ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:557
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] kit-00034-00034 2024-12-30 09:38:10.590985 +0000 [ kit_spare_003 ] WRN Security warning: running without chroot jails is insecure.| kit/Kit.cpp:3315
2024-12-30T10:38:10+01:00 [1:collabora1:collabora] kit-00035-00035 2024-12-30 09:38:10.605218 +0000 [ kit_spare_004 ] WRN Security warning: running without chroot jails is insecure.| kit/Kit.cpp:3315
The reason for suggesting a reinstall is the fact that I have not seen the read-only issue elsewhere (other servers, ForumâŠ).
I will provide more info around 13:00âŠ
My 2 cents
Andy
once installed and configured you can join the URL and display OK with a valid dns certificate, you can also join the admin page
Some can use collabora without real certificate but I prefer to state ask for a LE certificate
LE is so easy, I also prefer using LE!
Feedback will be comingâŠ
Salut @stephdl
I reinstalled Collabora (now as collabora2) and I can now login into the console.
NextCloud can not connect, it shows me:
Es konnte keine Verbindung zum Collabora Online-Server hergestellt werden.
Failed to connect to the remote server: cURL error 60: SSL peer certificate or SSH remote key was not OK (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://collabora.r9.anwi.ch/hosting/discovery
Nextcloud wonât open any more, seems to need a reconfiguration.
It did request the CODE server name.
Iâm now rebootingâŠ
Salut @stephdl
Finally success!
Nextcloud opens, and so does CODE inside NextCloud - it all works now!
Thanks!
For you and the dev team, all my best wishes for 2025!
My 2 cents
Andy
1 Like
super 2 vs 1
@transocean you have to retry again 
Salut @stephdl
As part of the Xmas present I now have a Nr2 on my back⊠(collabora2)
So what, it works!
My 2 cents
Andy
1 Like
Hi @stephdl
unfortunately, I canât contribute anything more at the moment because I switched to Onlyoffice from @mrmarkuz to narrow down the error. I will continue to use it for the time being. But thanks for your efforts anyway
RegardsâŠ
Uwe
1 Like
No problem, BTW I never tested only office, I should have a go one day
I already had it on the NS7. Apart from one or two difficulties, it has always worked reliably. But @mrmarkuz is like you and a few others here, is always a great supporter.
3 Likes