N8N issue due to webhook migration

Questions
1

Describe the problem/error/question

I can’t login into my N8N UI stack, i tried to connect the console and resert my password but i have an error message linked to a webhook migration.
I have several workflow using webhook and this errors happened already in the past i had to rebuild from zero. I’m happy to start over from zero but i need at least to backup some workflow this time to not loose everything.

What is the error message (if any)?

Migration “AddWebhookId1611144599516” failed, error: column “webhookId” of relation “webhook_entity” already exists

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: LATEST
  • Database (default: SQLite): SQLITE
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): DOCKER
  • Operating system: LINUX
2

what you get if you export by command line?

can you try to disable workflow by cli before export?

3

For now when the container restart in loop due to this error :

Initializing n8n process
n8n ready on 0.0.0.0, port 5678
Migrations in progress, please do NOT stop the process.
Starting migration AddWebhookId1611144599516
Migration "AddWebhookId1611144599516" failed, error: column "webhookId" of relation "webhook_entity" already exists
There was an error running database migrations
column "webhookId" of relation "webhook_entity" already exists
Permissions 0644 for n8n settings file /home/node/.n8n/config are too wide. This is ignored for now, but in the future n8n will attempt to change the permissions automatically. To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.
User settings loaded from: /home/node/.n8n/config
Last session crashed

I can’t get access to container anymore