@jdaviescoates thanks for the hint 🙂

@girish Gotcha but as long as I don't do that, I should be gtg. Im just thinking of a script that does 3 things.

Grabs all the IP's from emerging threats block list Grabs all the 403/404's from access logs sends them to greynoise to check if they are known "noise" and then Add both of these IP groups to that file and restart the service.

@necrevistonnezr Great! Thanks for your guys help. It’s much appreciated.

@nebulon @girish NVM! i figured it out!! 😇
Had to append the URL call with the (?access_token=) parameter & token
Figured it out with SoapUI first then got it to work in Wappler 😁
+1

@girish Thanks Girish. I'll email you directly (support@cloudron) so we can tidy things up.

@ddlidded the updated app package is now released.

@jdaviescoates said in *Really* lightweight, simple (use and administration) real time chat? Does it even exist today?:

Sadly not open source

Sorry! I skimmed the post, I must have missed that requirement 🙂

This is super helpful. I’m hoping we see something like this as a feature baked in though. Like multiple backup sources with different schedules

I haven't had a chance to finish the overall guide for the cloudron specific part but I completed a guide for installing OpenCTI with Traefik, Elasticsearch, and lots of plugins. I also have a complete docker-compose for OpenCTI, Elasticsearch cluster with X-Pack security, and multiple plugins as well as LDAP integration. you can find it here

OpenCTI install guide
https://dev.azure.com/Mastadamus/OpenCTI/_wiki/wikis/OpenCTI.wiki/3/OpenCTI-with-Traefik-Reverse-Proxy

OpenCTI GIT that contains my templates
https://dev.azure.com/Mastadamus/_git/OpenCTI

If you just want to skip to how you integrate LDAP with OpenCTI docker-compose I will paste examples below

- PROVIDERS__LDAP__STRATEGY=LdapStrategy - PROVIDERS__LDAP__CONFIG__URL=ldaps://Your.Domain.Name:636 - PROVIDERS__LDAP__CONFIG__BIND_DN={{`cn=admin,ou=system,dc=YourLDAPserverName`}} - PROVIDERS__LDAP__CONFIG__BIND_CREDENTIALS=XXXXXXXXXX - PROVIDERS__LDAP__CONFIG__SEARCH_BASE={{`ou=users,dc=YourLDAPserverName`}} - PROVIDERS__LDAP__CONFIG__SEARCH_FILTER={{`(cn={{username}})`}} - PROVIDERS__LDAP__CONFIG__MAIL_ATTRIBUTE=mail - PROVIDERS__LDAP__CONFIG__ACCOUNT_ATTRIBUTE=givenName - PROVIDERS__LDAP__CONFIG__ALLOW_SELF_SIGNED=true - PROVIDERS__LOCAL__STRATEGY=LocalStrategy

@nebulon Good to know. Thank you!

@hustler We don't have anything public for students but can you write to support@cloudron.io ? We will see what we can do, thanks.

@ApplegateR I think this is some legacy hosting provider API. Cloudron uses https://api.cloudflare.com/ , so we should be fine.

Given the inclusion of EROFS in the Linux kernel and it making into Ubuntu, a few questions come to mind.

Among the features listed are compression and caching.

Hence the question is, what is the Cloudron configuration for EROFS and are we using the potential for caching and compression since we run so many containers based on an identical base image.

@girish is it defaults or thoughtful tuning?

@Aizat said in Wasabi Timed Deleted Storage:

@timconsidine thanks, I'll check Scaleway and Hetzner out 🙂

FYI both (aside from Hetzner US location where they're just co-locating)) are 100% powered by renewable energy too, imho an important consideration in a climate emergency 🙂

@timconsidine Yes, as mentioned by @humptydumpty and maybe start with, what tools do I need to have ready, and we should get our feet wet with in some cases, before starting, which are going to be in use during the whole process.

Cloudron CLI of course, what else? A docker registry? A GIT server? A VPS with docker installed? A Docker desktop version? (as well as the previous?) How are they connected? Etc

Maybe also an example of how one is (or should be) set up?

Thanks for the offer mate!

Thanks Girish! 🙂

@girish said in Vultr DNS default TTL:

The changelog is not comprehensive, it doesn't have 1-1 relation with all changes since it also goes into the UI. Only way to know is the git log for small changes.

Totally fair. I was surprised to see that one missing since there's a ton of smaller changes still in the changelog in previous versions. I always thought the changelog was quite comprehensive before, but maybe it's geared more high-level now.

Thank you so much @fbaretls! Since Uptime Kuma has all the notification types I need (Matrix, really 😊) this solves my issue 🙌

See you in the co-olperative sector, @jdaviescoates ✌

@LoudLemur
Looks like it but I don’t remember if on purpose or as part of the Ubuntu Server installation 😑 - it’s quite some time ago that I installed Ubuntu Server on this machine

Festplatte /dev/mapper/beebox--vg-root: 461,58 GiB, 495603154944 Bytes, 967974912 Sektoren Einheiten: Sektoren von 1 * 512 = 512 Bytes Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes Festplatte /dev/mapper/beebox--vg-swap_1: 3,69 GiB, 3942645760 Bytes, 7700480 Sektoren Einheiten: Sektoren von 1 * 512 = 512 Bytes Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes