Seems a bit mean that the open-source version doesn't allow for more than one Admin user when you can just share the Owner login credentials with other Admins to do the sensible things that Admins need to do. Be interested if anyone finds any other workaround for this deliberate limitation.

@zonzonzon are you rferring to https://docs.n8n.io/hosting/scaling/queue-mode/#start-redis ? I have to say such a setup might be an overkill for Cloudron. (as in , having multiple workers + horizontal scaling) . The package is designed for a single node deployment.

Good catch @nebulon . @zonzonzon https://docs.cloudron.io/apps/n8n/#custom-node-modules . Just edit /app/data/env.sh and set EXTRA_NODE_MODULES to empty string and then restart the app, see if that helps.

My mistake with setting in firewall in AWS, everything back to normal, it works just fine

Okay so for those with the same problem.. it's possible to fix on 1.74.3 (Current version of Cloudron) by following these steps: Set N8N_PROXY_HOPS to 1 in your ENV, then restart your n8n instance. DELETED the credential and recreate it (Modifying it don't work, you need to delete and recreate!) Update your workflow And it will works.

I managed to install by it by removing some un-used community nodes, not sure which one was causing this but by cleaning up I got it to install

Adding max_old_space_size to my .env solved the issue yay 🥳

New package should fix the issue

Hi @joseph pandoc is also part of Cloudron n8n package You're right I didn't realize this. It is a good surprise. I have other workflow requiring GDAL binaries for example (https://gdal.org/en/latest/). This one is mode specific and is not here. I guess I am good to make a custom packaging... I found some shady npm packages including binaries but it does not seem properly maintained.

Sure I can seek that out. This community has been helpful in the past on other apps. Plus I am paying for this through Cloudron. Point taken what you're saying but if the apps don't work there is no point in continuing to pay for this service.

@AmbroiseUnly Great, this helps me finally

@nebulon You are right. Our website hosting provider had to whitelist the n8n server's IP. Thanks for your help!

Did you explore this any further?

Have you seen https://docs.cloudron.io/apps/n8n/#built-in-node-modules ?

If you login as the admin user, you can change the email in personal settings i.e /settings/personal .

Are you running n8n on Cloudron? This is a Cloudron related forum and it seems your post on n8n.io is the correct way to go forward.

Hi @nebulon, we don't know yet. I created a new post for it, see here https://community.n8n.io/t/workflow-activation-fails/49834

Just for the sake of documenting, here is what I ended up with, in my .env.sh file: # ------------- NODE MODULES --------------------- # Allow node modules to be used in code node - https://docs.n8n.io/hosting/configuration/#use-built-in-and-external-modules-in-the-code-node # Allows usage of all builtin modules export NODE_FUNCTION_ALLOW_BUILTIN=* # FYI This is a SPACE separated list export EXTRA_NODE_MODULES="cloudinary@2.2.0 node-fetch@3.1.1" # Allow usage of external npm modules # Those modules are auto-installed by Cloudron upon app restart, see https://forum.cloudron.io/topic/11946/how-to-install-npm-packages-that-n8n-app-can-use/4?_=1719382777426 # FYI This is a COMMA separated list export NODE_FUNCTION_ALLOW_EXTERNAL=cloudinary,node-fetch