Creating public group is not available any more

[avatar1024]

@fbartels it feels there is a problem with the recent version of the app. Creating public group is not available any more and people have to sign in.

I had a public group set-up, joined the call, sent the link invite but the person was asked to login. I tried the link myself in a private browser window and it was the same, I was asked to sign in (whereas usually, it worked directly).

So I deleted that group and tried to create a new one but there isn't the option any more to make the group public. Is this a bug??

[fbartels]

Hi @avatar1024

indeed the configuration for guest access seems to be missing from /api/config/v1/kopano/meet/config.json with the last update. Will have to take a closer look later today.

@girish can you move this and the last reply for @avatar1024 into a new topic?

[avatar1024]

@fbartels Thanks!

[fbartels]

Hi @avatar1024,
while I was able to initially reproduce the issue, after a rebuild (end even after just reinstalling the version from the marketplace) I am no longer able to do so.

Can you check if you restart/reinstall the app if the config is properly showing for you as well? For this you could open /api/config/v1/kopano/meet/config.json in your browser. It should look like the following:

{
  "apiPrefix": "/api/gc/v1",
  "useIdentifiedUser": true,
  "apps": {
    "enabled": []
  },
  "guests": {
    "enabled": true
  }
}

[avatar1024]

@fbartels Oops sorry, I should have at least tried to restart. It working fine just with restarting the app (no need to even reinstall). Thanks

[imc67]

@fbartels in my issue https://forum.cloudron.io/topic/3596/public-link-unavailable-after-x-days I had a similar problem like this and I still have.

After x uptime it is not possible anymore to create public meetings or to join a previously created public meeting.

I tried your suggestion to call the json and this is the result:

{
"apiPrefix": "/api/gc/v1"
}

So somehow something is deleting this information?

EDIT: I also discovered now that without the app being updated there is a new menu option in the GUI with links to other products of Kopano but they result in 404’s.
@girish I think it’s really “spooky” that this Cloudron-app is updated without noticing it’s users.

[fbartels]

@imc67 yes, I had to think of your two postings as well while musing over this topic.

What does seem to happen is that at some point the integrated webserver "forgets" the customized configuration (the meet web client is configured by /api/config/v1/kopano/meet/config.json).

The output you are getting is the built-in default, while for guest access (and the application starter you've seen) additional configuration is necessary.

[robi]

@fbartels is this config being written in a temp location that gets aged out or cleaned up?

How else would it be able to revert to a default?

Where do the defaults come from? Shouldn't be on the ro filesystem if linked properly.

[fbartels]

@robi yes, something like that seems to happen. The config file is created dynamically at startup and placed into /tmp. Seems there is some background job on Cloudron that clears out that folder at some point.

There is a newer version of Meet available anyways, it probably would be the best to move the file to /app/data instead. Will work on a pr today.

[fbartels]

There is now an update in the Cloudron Appstore that brings both a fix for this and also updates Meet to version 2.3.1.