Upgrade from 1.29.1 to 1.3.1 fails

Questions
1

Upgrade to 1.3.1 failed

Docker upgrade to 1.3.1 fails.

What is the error message (if any)?

n8n-n8n-1  | QueryFailedError: SQLITE_ERROR: no such column: AuthIdentity__AuthIdentity_user.globalRoleId
n8n-n8n-1  |     at handler (/usr/local/lib/node_modules/n8n/node_modules/typeorm/driver/sqlite/SqliteQueryRunner.js:81:26)
n8n-n8n-1  |     at replacement (/usr/local/lib/node_modules/n8n/node_modules/sqlite3/lib/trace.js:25:27)
n8n-n8n-1  |     at Statement.errBack (/usr/local/lib/node_modules/n8n/node_modules/sqlite3/lib/sqlite3.js:15:21)
n8n-n8n-1  | Error: Exiting due to an error.
n8n-n8n-1  | QueryFailedError: SQLITE_ERROR: no such column: AuthIdentity__AuthIdentity_user.globalRoleId

Information on your n8n setup

1.3.1

  • Database (default: SQLite):
    SQLite

  • n8n EXECUTIONS_PROCESS setting (default: own, main):

I do not know

  • Running n8n via (Docker, npm, n8n cloud, desktop app):

Docker

  • Operating system:

Windows 10

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

hello @PlkMarudny

Are you talking about v1.3.1 or v1.31.1?

1 Like
4

Yeah, 1.31.1. my bad.

1 Like
5

Hey @PlkMarudny,

Can you try going to 1.32.1 and let me know if you have the same issue, If you do can you go back to 1.29.1 and see if the issue is still there.

6

It seems I’m having the same issue now upgrading from 1.25.1 to 1.32.2.

When I want to use the old container it does not start anymore

QueryFailedError: SQLITE_ERROR: no such column: WorkflowEntity__WorkflowEntity_shared.roleId
at handler (/usr/local/lib/node_modules/n8n/node_modules/typeorm/driver/sqlite/SqliteQueryRunner.js:81:26)

When I run the new one it does start but workflows are not shown in the Webgui also the gui is only reachable through the IP and not the Domain name anymore.

When I look to the logs it seems that the workflows are up and running but can’t access them through the GUI

7

I think that’s because of the HTTP instead of HTTPS

Check this one

in n8n 1.34 there is now a warning about that.

8

Yes just figured it out while trying with 1.34.

But how can I redirect n8n to the domain again?