Self hosted Hostinger- Terminal real issue after docker rm

[JJJorg]

[HELP] After follow ChatGPT instructions for do the n8n update on my hostinger terminal i think i mess up everything ( OMG). I paste what chatgpt told me he did:
Hi everyone,
I need help recovering my n8n instance after attempting to update it manually on my Hostinger VPS.
What happened
I was running n8n with Docker + Traefik.
During an update attempt, I executed:
docker stop root-n8n-1
docker rm root-n8n-1
After this, the new container failed to start and I now receive the error:
/home/node/.n8n: No such file or directory
It looks like the host directory /root/.n8n may be missing or empty.
Main concern
I’m worried that by removing the container I lost my workflows and credentials if the bind mount was not configured correctly.
Current status
Running:
ls -la /root/.n8n
returns an empty folder or “No such file or directory”.
When I try to recreate the container with:
docker run -d --name…
-v /root/.n8n:/home/node/.n8n
-e N8N_BASIC_AUTH_ACTIVE=false
-e WEBHOOK_URL=“https://…”
-l traefik.enable=true
-l traefik.http.routers.n8n.rule=Host:n8n…cloud
-l traefik.http.services.n8n.loadbalancer.server.port=…
docker.n8n…:latest
I still get the “No such file or directory” error.
What I need help with

All i need is to recover my n8n

[JJJorg]

OK i just resolve the issue. Hoping could be helpful I did the backup directly on Hostinger.

[Rich37804]

There are directions in the Hostinger control panel on updating N8N.
Access your VPS through a browser terminal:

1. Pull the latest version of the n8n image:

   docker compose pull
   

2. Stop and remove the currently running containers:

   docker compose down
   

3. Start n8n with the updated image:

   docker compose up -d
   

That’s it! Your n8n instance should now be running the latest version. You can verify the version by accessing the n8n dashboard