Cloudron Forum

node.js has a "happy eyeballs" quirk. This causes premature network errors when there is no ipv6 and ipv4 is slow. I have fixed this in https://git.cloudron.io/cloudron/box/-/commit/aefa481c43603d284346d58497b6ff5b462efd88

Is there any update here? We'd like to deploy it to our Cloudron instance 🙂

After this I simply retried update and it worked. And now all apps are updating as well. Thank you.

Link to docs for future reference - https://docs.cloudron.io/user-management/#endpoints

https://learn.microsoft.com/en-us/azure/cdn/cdn-how-caching-works is an excellent read on some other interpretations.

@girish I have figured out a solution that doesn’t require admin permissions to ERPNext. It’s just that they use MariaDB specific commands here and there. That’s why MySQL addon is not useful at all.

Multiple databases works kinda fine but needs patching the source because ERPNext likes to use the same value for db-user and db-name; in fact there’s no way to give it the db-user. The name of the database is itself is considered username.

While building this addon, I would recommend setting the user’s name and database the same - ie. without prepending the same string with ‘db’ or ‘user’

Multiple databases isn’t required as ERPNext doesn’t work really well as a multi-site ERP anyway.

@girish said in Add Pre-Backup and Post-Backup Hooks:

Seems to not make sense.

That's normal for ERPs, almost all ERPs require full access to their database.
This is mostly due to the Modular idea for modern ERP, which implements different DB for each module like a microservice.
And communicate between with API or Functions Hooks

@nj thanks, I have pushed the update.

Hardened node developer here : long story short, nothing to worry about.

NPM security warnings are completely broken, they have a near 100% false positive rate (technically, the "vulnerable" dependency is here, but the flaw is, in literally all instances I have seen, not exploitable). An interesting read about this if you want : https://overreacted.io/npm-audit-broken-by-design/

@nebulon Thanks for the quick fix. I can confirm it works. No ipv6 on my cloudron yet.

@nj the app package is still unstable, can you try to reinstall? Also the current package version is 0.6.0 by now.

Tested and confirmed fixed - thanks!

@nj Cloudro relies on Ubuntu LTS versions and security updates are enabled automatically (independent from Cloudron releases). So once the ubuntu securty team updates the kernels, all Cloudrons will get is as well. Since this is a kernel issue, you will likely see some "reboot required" notification in your Cloudron dashboard afterwards.

@nj not sure if this would be a good idea to map Cloudron dashboard labels of apps into the apps as such. It will be quite hard to explain where such labels within the app might come from. Further an app label is not required, so it may be unclear what to be used as the fallback default. Or maybe I haven't really understood what kind of label this might be. If you look for general env variable support, the cloudron cli tool support adding further env variables https://docs.cloudron.io/packaging/cheat-sheet/#environment-variables

@nebulon Possibly related... would it be possible to add a column maybe (or even if just a hover message on a user) that would show when the user was last used to login to Cloudron? May be helpful in narrowing down users which should be marked inactive that may have been missed earlier. Essentially good for doing an audit of users. I guess as a workaround we can look at the Event History, however it may not go far enough back.

@ccfu You could put it on https://elest.io/open-source/authentik if it's worth $10/month to you.

@girish Nice, thank you. Have just added them manually.

Be double-nice if they were added automatically when Cloudflare is first used as a DNS Proxy, but I guess I understand that's both an additional feature to maintain, and maybe debatable if everyone would want it happening silently.

@nj it’s not free, but you can make it work with a workaround. I had to adjust an existing project, but it works now. I put together my changes here, hope it helps:

https://github.com/terehov/Mattermost-LDAP

@timconsidine Oh. What are your concerns about Freescout?