For instance, I’ve noticed that’s using a very outdated version of n8n (1.x.x), what’s the expected approach for updating? Am I expected to systematically go through the VPS?
Another one, what about environment variables, which are important for n8n configuration?
I am technical and I can handle a complex setup via SSH (I currently self-host on Render via Docker) but I am trying to not overcomplicate things if there are simpler approach : configuration directly in OVH, some docker-compose maybe, terminal directly in ovh web UI etc.
If you want a setup that stays easy to maintain, I’d use the OVH install only as a temporary starting point and move to Docker Compose that you manage yourself. n8n’s docs recommend Docker/Compose for updates and configuration, and on a VPS you’re generally expected to handle upgrades yourself.
For config, I’d start with the core env vars only: N8N_HOST, N8N_PROTOCOL, WEBHOOK_URL, GENERIC_TIMEZONE, encryption key, and database settings if you move beyond SQLite.
keep the VPS, but manage n8n yourself with Docker Compose instead of relying on the OVH preinstalled package long-term.
Thanks! After digging the image content, it’s indeed quite basic, just a Docker Compose setup on Debian. So I am reinstalling on Ubuntu (just to have a setup closer to my dev machine) and will install n8n manually. I am expected to secure the VPS mostly manually anyway.
This way, I will also have my websites running on the same VPS (I plan to try Dokku) since it’s relatively oversized for my usage of n8n.
It’s quite barebone in the end but the best I can have at this cost point.
Hébergement VPS n8n : installer n8n sur un serveur | OVHcloud France ) .