@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

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? [image: 1630085548014-63b2598e-257d-4fef-beb9-be610489b4b2-image-resized.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.

My bad, I'm not sure why I thought 2FA was not into consideration here ! I can login just fine now, this issue, isn't one