Regarding the very recent post about the PGP repository update and the commands to run - does this apply to an installation of Collabora when using with a Nextcloud server and Nextcloud Office?
Hii @Nigel Great to see you back on forum 
Yes, the recent PGP signing key update does apply if you’re using Collabora Online (COOL or CODE) installed via .deb or .rpm packages — even if it’s being used together with Nextcloud Office.
-
If you’re running Collabora Online as a separate service (e.g., on the same server or another server) installed using .deb or .rpm packages, then yes, you need to update the PGP key to continue receiving updates properly from the Collabora repository.
-
If you’re using a Docker image of Collabora CODE (like
collabora/code), then no action is needed — Docker images are self-contained and don’t rely on your system’s package manager or its keys. -
If you’re using a Nextcloud app only (like Nextcloud Office) without a separate Collabora backend, this typically uses a Collabora server elsewhere, such as the built-in Nextcloud Office CODE backend, or your own Docker-based setup. Again, no update is needed unless you manually installed Collabora Online via
.debor.rpm.
TL;DR
Update the key if you installed COOL/CODE using .deb or .rpm packages.
No update needed if you’re using Docker or Snap packages.
No update needed on the Nextcloud server unless it also directly runs a .deb/.rpm installed Collabora instance.
Hoho! V good! 
And many thanks for clarification, I am going to run the .deb command (installed as package). Getting cautious in my dotage about ‘assuming’ anything once everything is working 
If you get an idle moment perhaps have a look at another (it seems v long running) issue. Can’t remember if I raised here or over on Nextcloud forum, sorry! My users are very frustrated that they can only work on one doc at a time which seems to basically be because they don’t open in a new browser tab?
Sorry to ‘crossthread’ (
).
All the best and again, many thanks.
1 Like