Lol, . Sorry, I totally misunderstood. It's fine to discuss things here as long as it's not too off-topic and still keeps Cloudron related.

@girish said in How to disable user signup?: Bbut if you click register and try to register, one cannot login without an invite code. Ah, I see. I just tested this and you are correct. That is good enough! I do still have these two extra "blank" users (one admin and one not) that I cannot figure out how to get rid of and cannot edit (I tried to set them to Inactive, but the Save button doesn't appear to do anything), but I also cannot login as them, so I think it's okay. (These users are only in wekan, not in cloudron. My cloudron users are just the ones I expect to see.) Thanks for the help, and for the update to the docs. You are doing wonderful work trying to make self-hosting feasible for folks willing to try.

@girish That link still leads me to a 404, just FYI.

@jdaviescoates

Ok last reply for this issue as I think you can mark it solved. The environment variables do seem to be working now from what I can tell. I guess my initial tests just for some reason didn't work. But I did get an email today. So it works. Thanks for the help. Appreciate it.

@girish Sure, agreed - and somewhat from experience I've found the costs/benefits of high-availability can almost all be achieved with a solid backup/permissions/restore strategy - for which you already cover really well so links just for reference on low-cost managed K8S hosting really. Rancher 2 is the closest alternative I know of but even that is complicated enough.

@girish I think all these % numbers are a bit misleading and opinionated - but as you rightly detail it's a case of looking at the appropriateness of each item and reasonability. It's impossible to know or remember everything but still a nice too for a quick review to see if there's any easy wins, and I suppose the scoring mechanism could be handy marketing for some once a certain level is considered reasonably hardened.

@nebulon files are between 64B and 1.5MB each, so not big. I can try with a different browser, of course. What I would suggest is to put a <noscript> tag in there (with links to download file, and potentially filesname too) which would basically be shown if you don't have javascript. This would resolve the problem.

I did look into integrating with gogs when I did the GitLab integration. IIRC, the issue was that the gogs APIs for release tracking required a token (unlike GitHub and GitLab). This means that you have to create an account in another gogs/gitea instance (registration is frequently disabled) making it impossible to track. I think we might have to investigate a bit more and report the issue upstream first.

Thanks for the response, @girish. I'm going to email B2 and see what they say, I'll report back with results!

@markjames Thanks for reporting, this is a regression from our previous release. You can fix this as follows: Edit the file /home/yellowtent/box/src/provision.js Make this change https://git.cloudron.io/cloudron/box/-/commit/1259d1117364715533cb82546abec04987a44f8a . It's just a one liner. All you have to do is to add the line provider: settings.provider() in line 233 in the function getStatus. After that, sudo systemctl restart box (this restarts the code to apply the above change) If you refresh the setup screen, you will now see the AMI owner verification field like this: Let us know if that works, thanks!

@nebulon For sure, yeah I figured it may need more interest before it's implemented, and realistically I'm probably the only Cloudron user who's hosting on LunaNode (though I'd love to know if others are too), as I think LunaNode is a nice hidden gem that's not overly used yet and I switched to them recently as I had heard great things and their pricing is pretty good. Brief recommendation at the bottom for anyone interested. I'll let them know too about Cloudron in case they can do anything to help out too. On the topic of DNS at LunaNode though... it seems pretty awesome from what I can tell, as it has integrated load balancing and failover which is perfect and works with their included monitoring feature too (which is like Uptime Robot but provided by LunaNode), and so if my monitor fails and I have a second DNS entry, it'll automatically remove the failed one from the DNS records temporarily until it's back online, giving only the backup DNS entry for the "hot standby" server. Hoping to take advantage of those features in the not too distant future if it's feasible for me to run a second "hot standby" server. Waiting on Cloudron to add in some functionality to clustering which I think is coming in v6. Once that's there, I hope to be able to do that. Nudge nudge. haha. Brief recommendation based on my initial tests so far for other Cloudron users who want a good inexpensive hosting provider: I recently moved my Cloudron server from OVH to LunaNode to test out their performance, and the exact same Cloudron server in OVH used to take 10 minutes to fully come online after a reboot in OVH, and having restored that same server in LunaNode it now takes only 2-3 minutes to fully come online. That's also with some memory-intensive applications like Mastodon and NodeBB (which are always the last two to start in my environment given their resource usage). Same 8 GB nodes between OVH and LunaNode too. This performance improvement now cuts my downtime after reboots for security updates by almost 75%! That's my brief recommendation for LunaNode. haha.

@girish Got it. So as long as I stick with the Cloudron LDAP, all is well. Thanks for the explanation, and also for the update to the docs.

And AlertManager: "The Alertmanager handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integration such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts." https://prometheus.io/docs/alerting/latest/alertmanager/ https://github.com/prometheus/alertmanager

@Hillside502 Done, thanks. Having a bad keyboard day

@ultraviolet Cool, sharing is caring! I should have posted the parent user URL to see all the repos: https://github.com/WorldBrain

@ultraviolet Sure, that link was to the Electron App wrapper, there's more in the creator's repos: https://github.com/burtonator/ and someone seems to have dockerised: https://github.com/m0wer/docker-polar-bookshelf

Ok I gotcha myself because anyway I create my own pain so from what I understand to being able to restore Cloudron verify the DNS first than app/data I forgot to authorize my new IP in my Cloudflare API code 9109 is probably related to the fact it was unable to edit the DNS.

@girish The screenshot was within mailtrain. I have the email partially working now: it can receive email and I can read it on thunderbird, but I haven't been able to successfully send one yet. Some of the logs say something about the domain being too new. I'll try the wordpress built-in email for now and see how far I get

@girish I seeeeee! You've thought all this through before! OK, I learned new things from your explanation. Prob one just for the documentations then unless you think a per-App setting would be easy enough? It's only saving going into Cloudflare to delete and re-add the records but then my next research is going to be into https://dnsmadeeasy.com. TBH as I think Cloudflare is more a pied-piper following for their good marketing than for the essentials that are often better handled at the host (like Anti-DDoS, for which I do like Hetzner covering on the network level).