@micmc Yes, it‘s the one Cloudron creates. It‘s available in FileZilla and the Web UI of Cloudron.

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.

You should get something like this:

$ curl 'https://my.domain.com/api/v1/groups?access_token=xxx' { "groups": [ { "id": "gid-02fc23f0-c0df-4276-a54a-e3958b53ffd8", "name": "people", "source": "", "userIds": [ "uid-0a7dc777-c010-459e-a8db-ab853ea4f742" ] } ] }

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 👍

If someone figures out a working example of this and posts it here, it will inspire others to do more with N8N.

Lots of cool examples on their forum too.

I tried google.com as well. One thing is search engines usually block "crawlers" based on the IP address. They don't like crawlers from VPS usually (same goes for most services like yelp etc). So, can you check if you have GET requests fail to normal services and not to google?

63b2598e-257d-4fef-beb9-be610489b4b2-image.png

@brutalbirdie Getting notifications on anything may be something for you.

Using something like Notify17 combined with n8n.

OK, just as a heads up, the next package will remove the sendmail addon to avoid this confusion. This for writing this post @jk ! I didn't know you can access things using {{$env[xx]}}

@girish Hi. We are not having lost connections anymore

@thetomester13

de nada 😉

@girish perfect, thanks! I think this could go far in the way of hardening this unstable app.

@atrilahiji said in Cannot reach backend server:

So this appears to be an issue on Firefox rn that has been reported on their forum.

https://community.n8n.io/t/connection-lost/1471/49

Using a chromium based browser seems to be fine in my testing.

Edit: This post seems to have a suggested solution via the NGINX config https://github.com/n8n-io/n8n/issues/36#issuecomment-539647882
@nebulon @girish

The mentioned fix is already active.
See https://git.cloudron.io/cloudron/n8n-app/-/blob/master/pkg/nginx.conf#L64
But the issue persists.

I see the same errors. I guess we will fix these errors when we make the package stable and write tests.