Cloudron Forum

@potemkin_ai said in Domain misconfiguration:

You mean synapse? Yes, sure.

No, I mean an app has to be installed on mydomain.com for the well-known to be served. If there is no app, nothing is served.

The matrix domain setup can be tricky, if you are not using the defaults suggested in https://docs.cloudron.io/apps/synapse/#post-installation . For this reason, can you explain your setup again and also what matrix id you are trying to achieve? List the domains clearly and if you have done the 3 steps listed in the doc link.

@nebulon I do and thank you – sending e-mail as we speak.

@girish thank you!
I was thinking about pro version, but from the links you've mentioned it seems like they have a single code base for all features, thank you!

@girish Nessus is a very old security scanner: https://nessus.org/

No ideas, to be honest... that's why I thought to raise it to you.

Thanks, everyone!

@nebulon thank you! I've managed to find a way around to keep automated updates keeping the risk of update failure to a minimum, but - don't you consider using btrfs or zfs's snapshots to work that around on the platform level?

@girish

The footer is actually used in the login screen (in 7.5.1) . It's not a place to put some private information.

Probably, it's worth to mention that at the customization page?

I agree with restricting access to dashboard/apps though.

Glad to hear that! Do you believe that could make it to the roadmap anytime soon?

@imc67 geo-block feels like a more feature-rich solution, that might be of help, but not exactly my cup of tea.

I would guess, that Cloudflare doesn't prevent anyone from accessing your web service directly (should they figure out the IP address, for example, via e-mail you've sent)?

@girish , thank you! Yeah, I'm aware about the theory, I was wondering how it's done on Cloudron.

so this is not possible anymore

That's exactly what I would like to check 🙂
You know - people are always the weakest part of the chain...

@girish that's not the steps - that's an outcome 🙂

I didn't expect NextCloud instance without LDAP somehow got converted to the one with LDAP 🙂

@girish Thank you!

@girish No worries. I would be hesitant with new users going straight into an "old" issue myself.

I also had an issue with a backup in place but not reflected on the backups list.

@scooke yes, the files were stored locally all of the time, despite my settings were quite opposite (S3)

Fascinating conversation. We are looking for Cloudron monitoring @potemkin_ai ourselves.

Ideally you would keep it simple and self-contained enough that it doesn't need access to third-party app stores. In terms of the notifications, it would make sense to build a very simple API which would allow the external services (Rocket.Chat, Mattermost) to pick up nomon's notifications. You could include a sandbox for push notifications along with templates for the major services, and guidance on how to use it.

KIS and focused would be my choice for such an app.

The problem with many open-source people is that we want to cover every need and every possibility and leave every door open. To be everything for everybody doesn't work in the physical world, and to be honest it doesn't work well in the virtual world.

@girish no, it's quite the opposite - a message appears in chat, and if you have notifications disabled or just miss it - nothing happens.

Hooray! Thank you, @girish ! 🙂

@girish got it, thanks!

As for Jitsi - my showstopper issue is not yet resolved =(
https://forum.cloudron.io/topic/7473/no-sound-in-jitsi/42

@jdaviescoates lovely ♥

@girish , thank you!

I don't know to be honest... I would rather put it in the client<->server protocol as well, especially since it's not something I would like to expose to everyone. Guess it's because of the mixed model Element took - they are targeting at wide communities as well as closed groups, which is kind of hard to mix.

Anyway, from what I remember (and I might be wrong) I've seen something at NextCloud as well, so placing it at the app level feels right.
The only reason why I would consider placing in a general location - it's to ease implementation, as it doesn't seem to be a very often used feature. And for it to work, I'm perfectly fine to go the console or whenever, just to make it work.

No harm - just a bit of trash - if it will remain after the app removed either.