Cloudron Forum

@p44 On the topic of issues in changedetection.io, I want to illustrate to you how insanely difficult it is to even get accurate issue/bug reporting from the general public, something that should take an hour to fix often takes over a week because people Dont follow the issue template Give misleading, wrong, often completely made up information Say they followed the instructions when they didnt Miss out critical things from the issue report - like the exact (except for password/host etc) info from the notification URLs And then I come here and people calling it "A piece of shit", and yet, people cant even fill in a issue report with complete information infuriating

@girish No, I upgraded directly to 9.0.5 from the 8-series and never set up multiple backup sites.

That's working too for me by changing the name ! Thanks @james

Wanted to share a working solution, lightly adapted for Cloudron from Github issue comment referenced above: Enter Recovery Mode On the app's terminal: bash sqlite3 /app/code/data/kuma.db "DELETE FROM setting WHERE key = 'migrateAggregateTableState';" Exit Recovery Mode

@james said in Allow Invited Users to Access MiroTalk: But, maybe your client (phone) can simply not share the screen. At the moment, the getDisplayMedia API is not supported on mobile devices. Support may be introduced in future browser versions. For up-to-date information, see the MDN browser compatibility table.

How do you intend to get the GPU to the server? With most public hosting plans, this is quite expensive? I guess that is only relevant for people using their own hardware?

@nebulon thanks. It shows 0 active users, and I’m not sure why admins aren’t counted.I have no further questions.

Ah glad you managed to get down the issue in the end.

@nebulon No luck, I don't have a reliable answer for you.

Thanks for the update.

@tobiasb I've already got it running.

Thank you. I have done my work with cloudron CLI.

Yeah the idea was to just setup an oidc client credentials set with a redirect URI for the app, but not actually configuring the lamp stack to also use this. Same as with LDAP credentials. You can test the branch from https://git.cloudron.io/packages/lamp-app/-/tree/oidc-support?ref_type=heads if you know your way around building a custom app. Once installed you have to create an OpenID client in your Cloudron dashboard with /secure/redirect_uri and put the following in /app/data/apache/app.conf: # OIDCRedirectURI is a vanity URL that must point to a path protected by this module but must NOT point to any content OIDCRedirectURI https://<your.lampapp.domain>/secure/redirect_uri OIDCCryptoPassphrase somethingsecret OIDCProviderMetadataURL https://<my.example.com>/.well-known/openid-configuration OIDCClientID <clientId> OIDCClientSecret <secret> Then restart the app and then you may put those two lines in any .htaccess within your public/ folder which you want to protect from public access: AuthType openid-connect Require valid-user

Always happy to help. I also added this to the Cloudron docs.

@Neiluj said in Apps Compatible with Keycloak SSO: Hi - You can find the list of Cloudron packaged app that are SSO enabled here: https://www.cloudron.io/appstatus.html While this list speaks to a SSO managed by / for Cloudron, I am under the understanding that, for each of these apps, if you leave user management to the app when installting the app on Cloudron, you should be able to configured SSO to work with your Keycloak instance. Hopefully this is a correct assumption. I hope that this helps. Yeah, I'm not certain either, but think you're right that any app that already supports Cloudron SSO could be configured to work with Keycloak SSO too. I think perhaps @Sam_uk is using Keycloak (or similar) for the SSO for his Cloudrons and so could probably chime in with actual knowledge gained from experience.

For tracking the bug upstream: https://github.com/taigaio/taiga-front/issues/246

Hello @james Thanks for the suggestion! I checked the MySQL service — it has more than enough memory (20 GiB total, only about 40 % used). So it doesn’t look like a memory issue. There are no errors or warnings in the MySQL logs so far, so I think it should be fine. I’ll keep an eye on it for a few days just to be sure. Anyway, thank you very much for your help and your time!