@girish thanks, yes, that would be very nice, if n8n container's time zone (and probably other services) would be regulated that way.

As for the logs - I realized that we might speak about different kind of logs here - n8n stores execution logs, that might fill up the disk very quickly: https://community.n8n.io/t/hard-disk-full-where-to-delete-logs/2298

Here are the environment variables that seems like of the most importance at n8n:

GENERIC_TIMEZONE= WEBHOOK_TUNNEL_URL=https://FQDN/ #this one, to make sure webhook URL will work fine N8N_ENCRYPTION_KEY=.. #to avoid loosing credentials on docker restart #clear execution logs EXECUTIONS_DATA_PRUNE=true EXECUTIONS_DATA_MAX_AGE=672

@brutalbirdie no problem, below.

{
"name": "Cloudron user v2",
"nodes": [
{
"parameters": {},
"name": "Start",
"type": "n8n-nodes-base.start",
"typeVersion": 1,
"position": [
250,
300
]
},
{
"parameters": {
"formId": "=",
"events": [
"create",
"update"
],
"simple": false
},
"name": "Form.io Trigger",
"type": "n8n-nodes-base.formIoTrigger",
"typeVersion": 1,
"position": [
450,
450
],
"webhookId": "3362f54d-56a7-4bfc-a175-44c2cad397f3",
"alwaysOutputData": false,
"credentials": {
"formIoApi": {
"id": "5",
"name": "Form.io account"
}
}
},
{
"parameters": {
"authentication": "headerAuth",
"requestMethod": "=POST",
"url": "=curl -X POST -H "Content-Type: application/json" -d '{ "email": "{{$node["Form.io Trigger"].json["email"]}}" }' https://my.cloudron-space.org/api/v1/users\?access_token\=mytoken",
"jsonParameters": "=",
"options": {}
},
"name": "HTTP Request",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 1,
"position": [
790,
340
],
"credentials": {
"httpHeaderAuth": {
"id": "3",
"name": "Header Auth account"
}
}
}
],
"connections": {
"Form.io Trigger": {
"main": [
[
{
"node": "HTTP Request",
"type": "main",
"index": 0
}
]
]
},
"Start": {
"main": [
[
{
"node": "HTTP Request",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {},
"id": 4
}

@girish I went back to a fresh installation, because I had not checked the changes of the recent updates. This fix allows me to install handelbars. But it still doesn't work, I still get the message Cannot find module 'handlebars' with this example.

My session:

root@XYZ:/app/data# vi env root@XYZ:/app/data# cat env # Set the logging level to 'debug' export EXECUTIONS_DATA_SAVE_MANUAL_EXECUTIONS=true export EXECUTIONS_DATA_SAVE_ON_ERROR=all export EXECUTIONS_DATA_SAVE_ON_SUCCESS=all export N8N_LOG_LEVEL=info export NODE_PATH=/app/data/modules export NODE_FUNCTION_ALLOW_EXTERNAL=handlebars root@XYZ:/app/data# mkdir modules root@XYZ:/app/data# cd /app/data/modules root@XYZ:/app/data/modules# npm install handlebars --cache /tmp/foo npm WARN saveError ENOENT: no such file or directory, open '/app/data/modules/package.json' npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN enoent ENOENT: no such file or directory, open '/app/data/modules/package.json' npm WARN modules No description npm WARN modules No repository field. npm WARN modules No README data npm WARN modules No license field. + handlebars@4.7.7 added 6 packages from 39 contributors and audited 6 packages in 0.834s found 0 vulnerabilities ┌───────────────────────────────────────────────────┐ │ npm update check failed │ │ Try running with sudo or get access │ │ to the local update config store via │ │ sudo chown -R $USER:$(id -gn $USER) /root/.config │ └───────────────────────────────────────────────────┘ root@XYZ:/app/data/modules# ls -al total 16 drwxr-xr-x 3 root root 4096 Oct 9 16:25 . drwxr-xr-x 8 cloudron cloudron 4096 Oct 9 16:23 .. drwxr-xr-x 9 root root 4096 Oct 9 16:25 node_modules -rw-r--r-- 1 root root 1711 Oct 9 16:25 package-lock.json root@XYZ:/app/data/modules# ls -al node_modules/ total 36 drwxr-xr-x 9 root root 4096 Oct 9 16:25 . drwxr-xr-x 3 root root 4096 Oct 9 16:25 .. drwxr-xr-x 2 root root 4096 Oct 9 16:25 .bin drwxr-xr-x 6 root root 4096 Oct 9 16:25 handlebars drwxr-xr-x 4 root root 4096 Oct 9 16:25 minimist drwxr-xr-x 2 root root 4096 Oct 9 16:25 neo-async drwxr-xr-x 4 root root 4096 Oct 9 16:25 source-map drwxr-xr-x 5 root root 4096 Oct 9 16:25 uglify-js drwxr-xr-x 4 root root 4096 Oct 9 16:25 wordwrap root@XYZ:/app/data/modules#

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

@scooke I guess that in the Wordpress node you add an additional field for Content and link the expression for that to the output of the HTTP Request.
But I am just guessing.

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

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 🙂