Docker Setup SSL/HTTPS on self-hosted instance

[scropion86]

i have gone through this post

Setup SSL/HTTPS on self-hosted instance

Describe the problem/error/question I have setup a n8n self-hosted instance on a raspberrypi. The UI is accessible via http://mydomain.com. I need it to be accessible via httpS://mydomain.com in order to add Oauth credentials. I know I have to set the N8N_SSL_KEY and N8N_SSL_CERT in order to do it but not sure what to set. Current values in container: N8N_SSL_KEY: -----BEGIN CERTIFICATE----- xxxxxxxxxx -----END CERTIFICATE----- N8N_SSL_CERT: -----BEGIN PRIVATE KEY----- xxxxxxxxxx -----ENDPRI…

and found that documentation is missing to mention that these Env variable must point to the cert files in volume

my issue is i am hosting my n8n in an ec2 in aws which i don’t have root access to be able to access and modify the volume files manually by accessing its directory in /var/lib/docker/volumes/n8n_data/_data

can these two variables accept the cert info as string to a path to the file ?

Debug info

core

• n8nVersion: 1.59.4
• platform: docker (self-hosted)
• nodeJsVersion: 20.17.0
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: community
• consumerId: unknown

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

security

• secureCookie: false

Generated at: 2024-09-22T10:08:10.604Z

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Jon]

Hey @scropion86,

They only accept file paths, an easier way could be to use a reverse proxy like nginx / caddy or Traefik which will handle ssl for you.

There may be an AWS option to handle the same thing as well.