In order to help you, please provide app logs and as much other information as possible. Which credentials are you referring to and also where is the logo replaced? In the Cloudron dashboard or somewhere else?
You can often install things to the /app/data location manually if you can set the right env variables.
try:
export HOME=/app/data
then run the pip install
@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.
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.
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.
