Cloudron Forum

Thank you for helping me make it work.

Strange this .mjs thing with them, I'm going to open an issue with them.

@LoudLemur I too am unclear about your question.
There's already Gitlab, Gitea and Gogs on Cloudron.
Doesn't mean Forgejo can't added, of course.

So the memory leak indeed seemed to be coming from the frequent health check.
I customized the health check path and returned a simple response object, and it seems to do the trick.

image.png

I still think I have something incorrectly handled somewhere and if the website would have a lot of traffic, the issue would probably resurface.

But it's not very likely, so I'll stick to YAGNI. (I'll keep an eye on the stats in any case.)

Thanks for the help.

@girish I've never used a profiler, but maybe I should look into that. 😉

I'll open another thread for my issue.

Once I didn't find it, I hypothesized that by dowloading the logs, I would get more info, but I couldn't download them.

Not sure if it would be useful, but I figure I'd mention it.

@ruihildt right, it's documented as such at https://github.com/TandoorRecipes/recipes#license as well. My understanding is it's OK to selfhost but not resell tandoor for commercial stuff or host it for others (in the spirit of the author's current state of mind).

So I had to change a lot of variable to "public" or "true" to make it happen.

I am certain I didn't myself change this manually, so let's blame a solar bit flip. 😉

Thanks for the pointer!

@ruihildt what do you mean by other NS?

This is a known issue - https://forum.cloudron.io/topic/8149/can-t-manage-existing-email-address-since-v7-3-4-update . It's getting fixed for 7.3.5. As @subven said, the issue is related to getting the mailbox sizes. It takes a bit of time to get that information since we get it via dovecot . So, nginx -> box code -> mail server -> dovecot and all the way back.

@nebulon Thanks, I had searched before posting, but not well enough apparently. 😉

@robi
We did, but i don't recall the reason we excluded as an alternate to ceph(that we are using in prod currently)

@ajtatum interesting, thanks! 🙂

Thanks, that's perfect.

@necrevistonnezr It is, I skimed the start of that thread, and as it was unrelated, I just assumed it was not about my issue.

@ruihildt They renamed a constant from UnicodeUsernameWhitelistValidator to
UnicodeUsernameAllowlistValidator

To fix:

Edit /app/data/site_settings.yml using file manager and replace UnicodeUsernameWhitelistValidator with UnicodeUsernameAllowlistValidator

This is something we have to fix in the next iteration together with the translation. For the moment those singular/plurals are hardcoded.

@nebulon My bad, I created a discussion in the discussion because I felt it was loosely related to password management.

@ruihildt Updates to packages are rolled out slowly. So if a user tries to check for an update manually (i.e they click for 'check for updates') and they are not part of the rollout, they get shown that message. Generally, it is safe to update anyway but we are just being careful here.

@grienauer we started out initially with a rocket.chat instance which is still alive and used mostly for internal communication though. Once we had this forum, we essentially wanted the community to move here, since the chat turned out to not be very helpful with issue and solution search-ability. Of course also no public indexing of the channels.