Hello,
I am running n8n locally to test it, but I have been struggling with setting https protocol instead of http.
I added to the config:
export N8N_PROTOCOL=https
export N8N_SSL_KEY=/path/to/keyfile
export N8N_SSL_CER=/path/to/certfile
When I start n8n, I get:
Editor is now accessible via:
http://localhost:5678/
Unfortunately, this configuration does not change anything. Can someone explain how to do it?
Information on your n8n setup
**n8n version:n8n/0.228.2
**Database (default: SQLite):SQLite
**n8n EXECUTIONS_PROCESS setting (default: own, main):own
**Running n8n via (Docker, npm, n8n cloud, desktop app):npm
**Operating system:MacOs
Hi Imane E. M. Welcome to the n8n community
n8n offers a free service to spin up a local instance which can be accessible from the internet.
It’s called tunnel.
All you have to do is to start the n8n with tunnel flag.
Something like this.
n8n start --tunnel
With this you’ll get HTTPS. But this is for local usage only and should not be used in production.
Anyone with this URL can access and modify the data on your running n8n instance.
Here is the related docs which might help.
3 Likes
Jon
June 7, 2023, 7:53am
3
Hey @n8n_user_questions ,
The settings look right to me, how did you actually start n8n?
2 Likes
Hello Naveen,
Thank you very much. It worked
Best regards,
Imane
1 Like
Hello Jon,
From command line:
sudo n8n start
I installed n8n with homebrew following the steps of a tutorial.
1 Like
inbsp
June 11, 2023, 10:25pm
6
Hello @n8n_user_questions
Please do not use --tunnel
in production.
Instead, if You have a domain, consider using a proxy in front of your n8n instance. Like nginx proxy manager . It is easy to set up, it has a web interface, and it will automate all obtaining/renewing etc certificate nonsense, that you have to do.
So far I had no issues with nginx proxy manager + n8n.
2 Likes
system
Closed
June 18, 2023, 10:26pm
7
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.