# Upgrade from 0.x.x to 1.x.x and all of the workflow is gone and disappear **URL:** \ **Category:** Questions\ **Tags:** core, deployment\ **Created:** [August 7, 2023, 3:23pm UTC](https://community.n8n.io/t/upgrade-from-0-x-x-to-1-x-x-and-all-of-the-workflow-is-gone-and-disappear/29062 "2023-08-07T15:23:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![simonlkch](https://avatars.discourse-cdn.com/v4/letter/s/85e7bf/32.png) [@simonlkch](https://community.n8n.io/u/simonlkch)\ **Post date:** [August 7, 2023, 3:23pm UTC](https://community.n8n.io/t/upgrade-from-0-x-x-to-1-x-x-and-all-of-the-workflow-is-gone-and-disappear/29062/1 "2023-08-07T15:23:13Z")
Upgrade from 0.x.x to 1.x.x and all of the workflow is gone and disappear how can i find the previous workflow? ## Information on your n8n setup - \*\*n8n version: 1.x.x \*\* - **Database (default: SQLite):** - \*\*n8n EXECUTIONS\_PROCESS setting default \*\* - \*\*Running n8n via (Docker) Synology \*\* ---
**Author:** ![craigz](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/craigz/32/28570_2.png) [@craigz](https://community.n8n.io/u/craigz)\ **Post date:** [August 7, 2023, 9:43pm UTC](https://community.n8n.io/t/upgrade-from-0-x-x-to-1-x-x-and-all-of-the-workflow-is-gone-and-disappear/29062/3 "2023-08-07T21:43:01Z")
Hi, the identical thing happened in my instance. In my case, i’m running in a container, and the first thing i saw when logging in after updating was the new user setup page, followed by a blank workflow. I was able to restore my workflows by importing each from json exports i’d made a while back. I’ve not had time to fully resolve the issue yet, but i was able to find the _root_ cause. Back in the 0.x.x days, the db & n8n ran as `root` within the container. Under 1.x.x the process now runs as the user `node` as described here: [n8n v1.0 migration guide](https://docs.n8n.io/1-0-migration-checklist/#breaking-changes) Due to this change, a new SQLite DB is created in ~node and even if the old db was to be checked, the `node` user can not access it due to it being owned by `root` (and being located in the root user’s home directory). The same document has what appears to be a solution, suggesting that the following command is to be run on the ‘docker host’: ```auto docker run --rm -it --user root -v ~/.n8n:/home/node/.n8n --entrypoint chown n8nio/base:16 -R node:node /home/node/.n8n ``` I’m running docker desktop on a mac, and am managing containers using portainer, so i’m not at all sure how or where to execute that docker command. i’ve basically resigned to create a fresh instance when i get a chance, which i’ll import my workflows into. For now i’m just not updating until i have the time to rebuild and currently have my workflows running just fine as long as i don’t upgrade the container image 😉 Hope that helps in some way, good luck! ---
**Author:** ![Jon](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jon/32/40174_2.png) [@Jon](https://community.n8n.io/u/Jon)\ **Post date:** [August 8, 2023, 7:30am UTC](https://community.n8n.io/t/upgrade-from-0-x-x-to-1-x-x-and-all-of-the-workflow-is-gone-and-disappear/29062/4 "2023-08-08T07:30:04Z")
Hey @craigz, The command is designed to be ran from a terminal where Docker is running, As you are using Portainer though there is more to it as Portainer doesn’t automatically change the user and keeps it as root. For Portainer go to the containers advanced settings and change the user to `node` and the working directory to `/home/node`. @simonlkch I suspect your issue will be somewhat similar, Double check your containers config if you are not launching it from a terminal. ---
**Author:** ![Luke\_Austin](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/luke_austin/32/10505_2.png) [@Luke\_Austin](https://community.n8n.io/u/Luke_Austin)\ **Post date:** [August 8, 2023, 1:07pm UTC](https://community.n8n.io/t/upgrade-from-0-x-x-to-1-x-x-and-all-of-the-workflow-is-gone-and-disappear/29062/5 "2023-08-08T13:07:24Z")
@Jon @MutedJam worth merging this one into my thread? > [@N8n data not persisting after Update to 1 (docker compose)](http://community.n8n.io/t/n8n-data-not-persisting-after-update-to-1-docker-compose/28999/16): > > So, following the user guide, here: and having created a user “n8n” - that should be: docker run --rm -it --user root -v /home/n8n/n8n-docker-caddy/.n8n:/home/node/.n8n --entrypoint chown n8nio/base:16 -R node:node /home/node/.n8n That gives me a permission denied, and running it with sudo sorts the issue. I’ll drop the git repo maintainer a line to ask for that to be added to the howto! Luke ---
**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\ **Post date:** [August 14, 2023, 9:16am UTC](https://community.n8n.io/t/upgrade-from-0-x-x-to-1-x-x-and-all-of-the-workflow-is-gone-and-disappear/29062/6 "2023-08-14T09:16:44Z")
Hi @Luke_Austin, thanks for the heads-up. I think your link will do fine in helping anyone finding this thread. Tbh I am also a bit scared of the Mergin functionality as it will move individual posts rather than the whole thread 🙈 ---
**Author:** ![craigz](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/craigz/32/28570_2.png) [@craigz](https://community.n8n.io/u/craigz)\ **Post date:** [August 14, 2023, 5:18pm UTC](https://community.n8n.io/t/upgrade-from-0-x-x-to-1-x-x-and-all-of-the-workflow-is-gone-and-disappear/29062/7 "2023-08-14T17:18:32Z")
Hi @Jon, I just updated my image to run as `node` and changed the working directory to `/home/node` as you suggested, and it worked perfectly. Just wanted to drop a message to say thank you for the assistance and confirm that the upgrade to 1.x.x was successful with a docker image managed by portainer. best, -c. ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [November 12, 2023, 5:19pm UTC](https://community.n8n.io/t/upgrade-from-0-x-x-to-1-x-x-and-all-of-the-workflow-is-gone-and-disappear/29062/8 "2023-11-12T17:19:22Z")
Closed on November 12, 2023, 5:19pm UTC This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.