@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.

@girish thank you! but at the meantime, it would be nice just to roll back to the previous version and fire some alert

@robi correct, vm2 can be made to load them but n8n does not configure it that way. I guess this has to be reported upstream to n8n to support loading modules outside node_modules.

I dunno what this problem was but it seems to have gone away now

@genie I see, this seems to be something networking related and since there are a few things in between the browser and n8n maybe some network issue in the middle (sorry, I don't have any experience with kemp). For a start, does it work without kemp and cloudflare proxying? i.e straight connection from browser to the Cloudron n8n installation? That would be a good place to start debugging.

@murgero link? Here's the link to the post: https://forum.cloudron.io/post/37057

@nebulon