@nebulon not sure why/what happened but the N8N came back to live just now and the Element & Matrix app too...I may need to move some app out then, will test,

thanks !

@martinkbs Perfect, thank you so much!

@girish I'm just going to hang my head in shame now 🙂

This box is behind NAT and, apparently, I'd messed up my firewall rules.

Thank you for the shell/telnet suggestion though. That was helpful.

Sorry for wasting your time!

@murgero said in n8n version downgrade:

Maybe cloudron can implement a way to pick app version if installing via cli for development purposes?

There's a FR for this and a manual way:
https://forum.cloudron.io/topic/2688/disaster-recovery-restoring-a-backup/8

@kevin-k Strange...can you try to revert back to a working backup, reinstall community modules again, reboot once again and go to that page see if everything stick ?

I had issues first time I installed, had to reinstall once, but then it went smooth...

@robi I just made it work following https://forum.cloudron.io/topic/7629/error-installing-community-nodes-on-n8n/20

@nebulon perfect, thanks a lot for this!

Yes, upstream is publishing updates nearly daily at the moment, so eventually your Cloudron should catch up, but you may also manually check for updates and apply those accordingly.

I'd like to use https://www.npmjs.com/package/@digital-boss/n8n-nodes-humhub in my N8N instance, so ability to install packages would be great.

@martinkbs
That's exactly what I was looking for!
I wasn't aware of Baserow or NocoDB. It sounds it might fit my needs.

Thanks for the ideas!

@hugoo_souza10
the matter of gunicorn workers is specific to baserow which I use for logging on N8N actions.

to change the baserow env variables just go into the baserow terminal and type
export BASEROW_AMOUNT_OF_GUNICORN_WORKERS=20

that should do it.

However for N8N the best you can do is give is 8gb or 16gb of ram, and increase the postgress ram to 4gb .

Have you installed n8n via Cloudron or somehow standalone? This is a Cloudron forum, so if you are not using Cloudron, I think you have to contact the upstream developers.

here is the first release: https://forum.cloudron.io/topic/7546/open-registration-app-for-cloudron

@girish Yes, this was it. I did not manage to see the actual json. But seems like n8n always adds quotes using the name / value combination. I changed it to this:

{ "nodes": [ { "parameters": { "requestMethod": "POST", "url": "=https://my.xxx.de/api/v1/notifications/{{$node[\"Item Lists\"].json[\"id\"]}}", "jsonParameters": true, "options": {}, "bodyParametersJson": "={\n\"acknowledged\": true\n}", "headerParametersJson": "={\"authorization\": \"Bearer xxx\"}" }, "name": "HTTP Request1", "type": "n8n-nodes-base.httpRequest", "typeVersion": 2, "position": [ 1100, 300 ] } ], "connections": {} }

Now it's working. I used this:
Bildschirmfoto 2022-06-14 um 18.16.17.png
instead of this:Bildschirmfoto 2022-06-14 um 18.16.42.png

@mabaker thanks! I have put your notes in our docs - https://docs.cloudron.io/troubleshooting/#hairpin-nat .

I have to clean up that troubleshooting section a bit, but that's a task for another day...

@girish + @nebulon it is very nice to have access to you; you are very responsive and highly competent 😉
thank you!

The solution is to add the filename to the path:

In my case:

/consume/file.pdf

I've built something similar for my site, but ended up just purchasing WP Webhooks and it made my life so much easier. It's definitely worth the $100 IMO.

Alright, I have put the same note about the visibility setting as we have in the app configuration section now into the install dialog.

@bubonicfred Thanks for sharing! I hadn't noticed it yet.

@bubonicfred currently, this is the best place to check - https://git.cloudron.io/cloudron/n8n-app/-/blob/master/Dockerfile#L20

@girish bingo! i will practice once more to confirm but i suspect that the first user == the user that gets rights to previously created things

one other thing i need to double check - when i upgrade to 2.0, for whatever reason (possibly unrelated to the upgrade), my n8n stopped working (it stopped responding to webhook triggers), i will see if that's consistent and perhaps related to "it won't work till the first user is created" or something else

edit : actually it recovered all the workflows, my bad
now I just have to create second user and share workflow with members

@robi I guess this is something for upstream. Ideally, we don't have to make such decisions since we are not experts on the app.

@girish it'ok now, thanks all

@girish I saw no red indicators on the nav bar. I guess that would have helped me towards the source of the problem. But I will keep an eye if a service gets into trouble again.

@humptydumpty 😄

@rmdes right, if you want external modules, we have to fix the package. The modules are hardcoded in the Dockerfile.