public link "unavailable" after x days
Hi @fbartels, today I discovered again "something strange" with a public meeting link.
Last Thursday a public meeting with 5 went fine! Today that group of people wanted to use the same public link to meet. However they were requested to login to Meet (but they can't because they don't have an account).
Because there was instantly stress by the organizer I quickly restarted the app and guess: that same link was available again for guests!!
I think I was able to save the log but don't feel comfortable to share public, can I email it to you?
[edit1] I checked the log in the online log viewer but see it is all about the restart, there is no single logging of before the restart, last log is of oct 23th!?!
[edit2] downloaded the full log and found this just before the restart of the app:
2020-11-03T12:05:55.000Z 2020/11/03 12:05:55 [INFO][cache:0xc00027ac30] Done checking OCSP staples 2020-11-03T12:27:32.000Z 2020/11/03 12:27:32 [ERROR] failed to copy buffer: readfrom tcp 172.18.0.13:8000->172.18.0.1:42974: use of closed network connection 2020-11-03T12:27:32.000Z time="2020-11-03T12:27:32Z" level=warning msg="websocket read pump exit" error="websocket: close 1006 (abnormal closure): unexpected EOF" manager=rtm rtm_connection=79 user_id="cn=uid-d231c67f-f582-4632-a161-7678e40f0264,ou=users,dc=cloudron" 2020-11-03T12:30:01.000Z 2020/11/03 12:30:01 [ERROR] failed to copy buffer: write tcp 172.18.0.13:8000->172.18.0.1:46156: write: broken pipe 2020-11-03T12:30:01.000Z 2020/11/03 12:30:01 [ERROR] failed to copy buffer: context canceled 2020-11-03T12:30:02.000Z 2020/11/03 12:30:02 [ERROR] failed to copy buffer: context canceled 2020-11-03T12:31:51.000Z 2020-11-03 12:31:51,010 WARN received SIGTERM indicating exit request
but don't feel comfortable to share public, can I email it to you?
Private support is unfortunately reserved for customers with a Kopano subscription. https://meet-app.io/index.php#pricing & https://kopano.com/pricing/support-professional-services/
Normally rooms are automatically destroyed after the last participant left and auto created once the first logged in user enters it. I have not seen a case where a room is not available when revisiting the same room at a later date (I have multiple repeating meetings per week).
Since the default logging does not show enough information you probably need to enable debug logging in kwmserver. This is influenced through the setting https://stash.kopano.io/projects/KWM/repos/kwmserver/browse/scripts/kwmserverd.cfg#21. This config file is located at
/app/data/kwmserverd.cfgin Cloudron. You need to restart at least kwmserver after changing the setting (but you could just as well restart the whole app).
Normally rooms are automatically destroyed after the last participant left and auto created once the first logged in user enters it.
In my experience this is not the case. It's now about 22 hours ago the public meeting ended, if I click that URL now I get the "Next"-"Enter yourname"-"Join" page with the result: "Guests can only join active group meetings".
Before the next time that URL is used for a meeting (next Tuesday) I'll switch on debug logging or if I can reproduce it before (by testing the URL daily).
es, a logged in user needs to be present before a guest can join.
ofcourse, but the thing is that that you wrote "rooms are automatically destroyed after the last participant left", it seems that's not the case as this guest was able to "almost" start to join. Where in the "faulty"-situation (see my first post in this thread) a guest was directed to the login page.
I'm lost ...
it seems that's not the case as this guest was able to "almost" start to join
No, you're reading too much into it. The check if the meeting can be entered is simply done at the last stage of the join flow. By then the user already "logged" in as a guest. Logged in in quotes since guests are authenticated through a jwk without their interaction.
Thinking further about it. In addition to the logging of kwmserver it could be interesting to know what Konnect logs at that point in time.
avatar1024 last edited by
@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 i made you a mod of this category.