Update process deleting all workflows and credentials

Describe the problem/error/question

installation process

I have followed instructions in docs and now my workflows and credentials disappeared
update:

Docker-composer.yaml

version: "3.7"

services:
  traefik:
    image: "traefik"
    restart: always
    command:
      - "--api=true"
      - "--api.insecure=true"
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.web.http.redirections.entryPoint.to=websecure"
      - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
      - "--entrypoints.websecure.address=:443"
      - "--certificatesresolvers.mytlschallenge.acme.tlschallenge=true"
      - "--certificatesresolvers.mytlschallenge.acme.email=${SSL_EMAIL}"
      - "--certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json"
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - traefik_data:/letsencrypt
      - /var/run/docker.sock:/var/run/docker.sock:ro

  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    ports:
      - "127.0.0.1:5678:5678"
    labels:
      - traefik.enable=true
      - traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
      - traefik.http.routers.n8n.tls=true
      - traefik.http.routers.n8n.entrypoints=web,websecure
      - traefik.http.routers.n8n.tls.certresolver=mytlschallenge
      - traefik.http.middlewares.n8n.headers.SSLRedirect=true
      - traefik.http.middlewares.n8n.headers.STSSeconds=315360000
      - traefik.http.middlewares.n8n.headers.browserXSSFilter=true
      - traefik.http.middlewares.n8n.headers.contentTypeNosniff=true
      - traefik.http.middlewares.n8n.headers.forceSTSHeader=true
      - traefik.http.middlewares.n8n.headers.SSLHost=${DOMAIN_NAME}
      - traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true
      - traefik.http.middlewares.n8n.headers.STSPreload=true
      - traefik.http.routers.n8n.middlewares=n8n@docker
    environment:
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
      - N8N_DIAGNOSTICS_ENABLED=false
      - N8N_VERSION_NOTIFICATIONS_ENABLED=false
      - N8N_TEMPLATES_ENABLED=false
      - EXTERNAL_FRONTEND_HOOKS_URLS=
      - N8N_DIAGNOSTICS_CONFIG_FRONTEND=
      - N8N_DIAGNOSTICS_CONFIG_BACKEND=
      - N8N_ONBOARDING_FLOW_DISABLED=true
    volumes:
      - n8n_data:/home/n8nadmin/.n8n

volumes:
  traefik_data:
    external: true
  n8n_data:
    external: true

What is the error message (if any)?

no error messages just asking for creating account.

Information on your n8n setup

  • n8n version:
    1.5.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
    docker composer
  • Operating system:
    Ubuntu server latest

Hi @justme :wave: Welcome to the community :tada:

In your docker-compose, under volumes:

- n8n_data:/home/n8nadmin/.n8n

Should be

-n8n_data:/home/node/.n8n

Of course, the exact path could be different depending on how you had n8n previously deployed, replaced with whatever location you have stored your data in :see_no_evil: If you’re moving to a named volume you won’t see your previous workflows, so there would be a few extra steps you’d need to take. You’d need to

a) mount whatever location you had previously stored your n8n data in (which hopefully the above will sort you out!), and/or
b) possibly update permissions as documented in the migration guide

Hope that helps!

1 Like

I have done that but it is not showing as updated. How do I find what is the latest version? github docs and your website hiding that information for some reason. It is showing 1.5.1 after update process.

Hi @justme :wave: You can find our latest release notes here on Github: Releases · n8n-io/n8n · GitHub and here on our docs: Release notes | n8n Docs which will also tell you which is the latest version and which is the next.

Can you try to use the tag latest when you run your Docker command and see if that updates? Otherwise, can you specify 1.9.3? You can do that by either using n8n:latest or n8n:1.9.3, for example:

docker run -it --rm --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n:1.9.3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.