This is extremely well explained. I hope you keep making tutorial videos! To make it this simple, yet super-clear and fast (not wasting time) is a true skill that few people have.
Thanks for the tutorial man. I have a couple of follow-up videos suggestions: 1. An in-depth video on how to attach an external database 2. A video on how to keep docker and n8n up to date after installing on Google Cloud VM Thanks again. Subscribed.
Great tutorial. Only issue is that you should not include the protocol () in the docker run command for the value of 'N8N_HOST'. I ran into an issue where N8N was appending the protocol to the value when generating a webhook URL on my VM.
@lobos009 You can follow the steps here: github.com/futurminds/n8n-self-hosting/blob/main/README.md#:~:text=your%2Ddomain.com.-,How%20to%20update%20n8n%3A,-You%20can%20follow
great video! However my webhook data doesnt show in UI, how can this be resolved! Ps- the data is available in the execution, I also cannot stop the execution
great content man! however, I'm facing an issue regarding the webhook data not showing in UI, any idea how to resolve this? Ps- the data is available in the execution, just doesnt show in UI, also cannot stop execution
@hashtechnovation3914 did you mean aws ec2? AWS Lambda is a serverless compute service designed to run code without managing servers, but it's not ideal for self-hosting applications like n8n due to its constraints around long-running tasks, storage, and network access. n8n requires a persistent environment, such as a VM or container, which AWS Lambda is not designed for.
@IvySaskia you can follow the instructions here to update the version: docs.n8n.io/hosting/installation/docker/#updating Important: Take a backup of ~/.n8n:/home/node/.n8n Ensure that your n8n instance is using a persistent volume or a mapped directory for its data storage. This is crucial because the workflows, user accounts, and configurations are stored in the database file (typically database.sqlite), which should be located in a directory that remains intact even when the container is removed. In your docker-compose.yml, you should have something like this: ``` volumes: - ~/.n8n:/home/node/.n8n ``` This mapping ensures that the .n8n directory on your host machine is used for data storage, preserving your workflows and configurations across container updates. When you stop and remove the n8n container, you are only deleting the container instance itself, not the data stored in the persistent volume. As long as the volume is correctly configured, your workflows and accounts should remain unaffected. But to avoid any chance of data loss you should take a backup of ~/.n8n:/home/node/.n8n before removing the container.
@@FuturMinds ok... when I use on my desktop docker, the data does not lose, but on this deploy how do I make the backup? I restart with the new image (making pull the new iamge) , I got two issues. 1 Data is lose .. 2 the new version on the container is not updated.
@IvySaskia On this link: docs.n8n.io/hosting/installation/docker/#updating, you will find that you first need to stop your container and then remove it. Then update the image and spin up a new container. To create a backup, you can copy ~/.n8n:/home/node/.n8n to your local or another directory on the same VM even before deleting the container. And then, after updating and spinning up a new container, if you see the data getting lost, you can replace ~/.n8n:/home/node/.n8n with the one you saved earlier. This should work fine.
This is extremely well explained. I hope you keep making tutorial videos! To make it this simple, yet super-clear and fast (not wasting time) is a true skill that few people have.
Thanks @pressrepeat2000 This means a lot :)
Thanks for the tutorial man. I have a couple of follow-up videos suggestions:
1. An in-depth video on how to attach an external database
2. A video on how to keep docker and n8n up to date after installing on Google Cloud VM
Thanks again. Subscribed.
@diegocs8 Thanks for the video suggestions. Those are good topics. I'll try to cover them soon.
Hello, your guide is outstanding. Thank you for sharing it. Best regards, Oren
Glad it was helpful!
Great tutorial. Only issue is that you should not include the protocol () in the docker run command for the value of 'N8N_HOST'. I ran into an issue where N8N was appending the protocol to the value when generating a webhook URL on my VM.
Great tutorial. Any tutorial on how to safely update n8n to latest version?
@lobos009 You can follow the steps here: github.com/futurminds/n8n-self-hosting/blob/main/README.md#:~:text=your%2Ddomain.com.-,How%20to%20update%20n8n%3A,-You%20can%20follow
great video!
However my webhook data doesnt show in UI, how can this be resolved!
Ps- the data is available in the execution, I also cannot stop the execution
great content man!
however, I'm facing an issue regarding the webhook data not showing in UI, any idea how to resolve this?
Ps- the data is available in the execution, just doesnt show in UI, also cannot stop execution
Please make video how to self host on aws lambda please
@hashtechnovation3914 did you mean aws ec2?
AWS Lambda is a serverless compute service designed to run code without managing servers, but it's not ideal for self-hosting applications like n8n due to its constraints around long-running tasks, storage, and network access. n8n requires a persistent environment, such as a VM or container, which AWS Lambda is not designed for.
When a new version of n8n is up, how do u update on the deployed one?
@IvySaskia you can follow the instructions here to update the version: docs.n8n.io/hosting/installation/docker/#updating
Important: Take a backup of ~/.n8n:/home/node/.n8n
Ensure that your n8n instance is using a persistent volume or a mapped directory for its data storage. This is crucial because the workflows, user accounts, and configurations are stored in the database file (typically database.sqlite), which should be located in a directory that remains intact even when the container is removed.
In your docker-compose.yml, you should have something like this:
```
volumes:
- ~/.n8n:/home/node/.n8n
```
This mapping ensures that the .n8n directory on your host machine is used for data storage, preserving your workflows and configurations across container updates.
When you stop and remove the n8n container, you are only deleting the container instance itself, not the data stored in the persistent volume. As long as the volume is correctly configured, your workflows and accounts should remain unaffected.
But to avoid any chance of data loss you should take a backup of ~/.n8n:/home/node/.n8n before removing the container.
@@FuturMinds ok... when I use on my desktop docker, the data does not lose, but on this deploy how do I make the backup? I restart with the new image (making pull the new iamge) , I got two issues. 1 Data is lose .. 2 the new version on the container is not updated.
@IvySaskia On this link: docs.n8n.io/hosting/installation/docker/#updating, you will find that you first need to stop your container and then remove it. Then update the image and spin up a new container.
To create a backup, you can copy ~/.n8n:/home/node/.n8n to your local or another directory on the same VM even before deleting the container. And then, after updating and spinning up a new container, if you see the data getting lost, you can replace ~/.n8n:/home/node/.n8n with the one you saved earlier.
This should work fine.