Ssl certificate for my n8n

Hey guys, I bought a ssl certificate on noip.net to use on my n8n that I have on a private server, but they are asking for CSR certificate.

Can you tell how can I create this certificate?

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:

Hey guys, sorry for the lack of information. I am entering in this world now and learning.
I installed the n8n on a ubuntu server 22.04.3 LTS following this script on github: GitHub - ddm21/Install-n8n-with-pm2: Video Guide for Reference
On this order, the script installs n18, nginx, n8n and after pm2.

I bought a ssl certificate on noip and now they say that CRT certificate is required. Do you know how can I create it?
The link of noip is How Do I Create a CSR For My SSL Certificate?
I thank you for any help you can give

Hey @Lbarreto,

Personally I would not use PM2 and would use Docker for running n8n which will automatically let you handle certificates through Caddy or Traefik using Lets Encrypt.

Sadly self hosting n8n is an advanced configuration option and one of the requirements is that you know how to manage your server of choice and other settings which would include creating certificates. The OpenSSL guide that NoIP has looks like it would cover what you need for generating a certifiacte and an CSR for signing.

Hey @Jon , thank you for your reply.
I know its a great challenge for me to manage this advanced configuration, but Iam willing to learn.
Thank you for give me some direction. I will follow OpenSSl guidelines.

1 Like

Hello,

I hope this answer is useful for you.

To secure your n8n instance with an SSL certificate:

  • Obtain a certificate from a trusted provider.
  • Install it on your server following provider instructions.
  • Update server config to use the new certificate.
  • Restart the server for changes to take effect.

Ensure your domain resolves correctly and certificate paths are accurate. If issues persist, provide more details for assistance.