I have installed n8n on my server and I was trying to use a webhooks node with my website contact form. At first, I was unable to pass the data through webhook then I have gone through the documentation and found something called Start n8n with Tunnel. Later, I used the command to start the n8n with tunnel and tried to pass the Details of the form to slack and it was successful. And I am able to trigger the webhook from my contact form and the complete workflow is working as I desire. I am just concern about the warning given for using the tunnel command. It is said to use tunnel only for the testing purpose, not for the production. I have tried to figure out how to get my workflow executed without using the tunnel and I was going through some of the tutorial videos in youtube and I find in a video that the URL is " https://jan.users.n8n.cloud " and the tutorial is explained on this domain which is having SSL installed. I want to set up my subdomain with n8n same as it is set up in " https://jan.users.n8n.cloud ". And moreover, I don’t have any idea what is docker and how to setup.
Hello @jan I have done the setup and I have a small doubt where should I place the docker-compose.yml file and .env file. I have placed them in /root directory for now and when I run the command to start docker which is " sudo docker-compose up -d " I get this warnings and I am unable to access n8n in https://n8n.mydomainname.com
I am sure I’m missing something that’s pretty obvious. Could you please help me? I love n8n and have been trying out few examples in my local desktop. Now I would like to host it in a server. Thanks for your help.
@harshil1712 I have redone the whole thing (but this time as an admin user, and not as root). It worked. Not sure what I missed while installing as root. But the main thing is now it works. Thanks for your response
@harshil1712 The issue was not with the account was used for installation. I installed n8n as root user in a VM (DO droplet) created through a cloud infrastructure manager which blocked all ports by default for security. I had to open port 80 and 443 for n8n to be accessible. That was the issue. And I thought it was issue with the root user by coincidence. When I installed n8n as an admin user (non root), I did it directly in a DO droplet created directly in DO manually. So all ports were open by default. So n8n worked. So it was just a coincidence.