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 🥳

@whitecube I just did this... I wonder why you could not? Take another look.

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.

Upstream thread - https://community.n8n.io/t/process-hanging-when-starting-n8n-starting-migration-1720101653148/50380/4

@AmbroiseUnly If the issue comes up again, we should investigate in more detail. Thanks for reporting

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

@nebulon said in "fatal: not a git repository":

Have you tried to use a subfolder in /app/data/ for this? This is where data is kept persistently in Cloudron.

Been using this folder and seems like it has had no issues for a week or two now 👍🏽 thanks for clarifying 🙏🏽

@dvlexp you have to ask these questions upstream in the n8n forum - https://community.n8n.io/ . We can only provide help here with the packaging aspect of n8n itself. App related issues are best asked upstream.

Are the CSP headers set as you expect them if you take a look at the request headers? Also double check them alongside the warnings in the browser console in case there is some typo and your browser thus ignores them.