# Meet.coop update October 2025

**URL:** https://forum.meet.coop/t/meet-coop-update-october-2025/1739
**Category:** Tech circle
**Created:** [16 October 2025 13:08 UTC](https://forum.meet.coop/t/meet-coop-update-october-2025/1739 "2025-10-16T13:08:04Z")
**Posts on this page:** 1
**Showing post:** 47

<div class="post-metadata">

### Author: ![kawaiipunk](https://forum.meet.coop/user_avatar/forum.meet.coop/kawaiipunk/32/1094_2.png) [@kawaiipunk](https://forum.meet.coop/u/kawaiipunk)
#### Post date: [21 December 2025 14:05 UTC](https://forum.meet.coop/t/meet-coop-update-october-2025/1739/47 "2025-12-21T14:05:26Z")

</div>

Hi folks, update from me.

I got a bit stuck because I haven’t been given access to the [sso.meet.coop](http://sso.meet.coop) “master” realm so I can’t access any of the Keycloak admin settings. This is true even from the command line, see: [Keycloak: How to add a new User - Mastertheboss](https://www.mastertheboss.com/keycloak/keycloak-how-to-add-a-new-user/)

I have securely handed over the SSO credentials to ColloCall that were being used on the [de.meet.coop](http://de.meet.coop) server and switched over the domain to point at the ColloCall server. Now we just need ColloCall to spin up the new server. Hopefully they will do this on Monday/Tuesday. If not, as soon as they are back at work in Jan. I wasn’t able to get a specific deadline from them.

I have locked down the old [de.meet.coop](http://de.meet.coop) and [bbb.de.meet.coop](http://bbb.de.meet.coop) servers with the firewall to only ssh access.

In the meantime, members can use the [ca.meet.coop](http://ca.meet.coop) Big Blue Button or ideally [https://jitsi.meet.coop/](https://jitsi.meet.coop/).

The current plan is to:

- Continue to try and get access to the [sso.meet.coop](http://sso.meet.coop) Keycloak admin
- Make sure we have archived all relevant files on [de.meet.coop](http://de.meet.coop) and [bbb.de.meet.coop](http://bbb.de.meet.coop) servers
- Spin them down
- Work out what to do about recordings backups
- Archive and spin down [ca.meet.coop](http://ca.meet.coop) (I have never been given ssh access to this server) and [bbb.ca.meet.coop](http://bbb.ca.meet.coop)
- Spin down the [jitsi.meet.coop](http://jitsi.meet.coop) service or add [meet.coop](http://meet.coop) SSO to it.
- Migrate and upgrade current [sso.meet.coop](http://sso.meet.coop) to new Web Archs server

This will leave a fully maintained infra that we hopefully be sustainable long into the future. We can start discussing the future of the co-op.

Season’s greetings!

---

_[View the full topic](https://forum.meet.coop/t/meet-coop-update-october-2025/1739)._