All my n8n API keys just expired - potential bug?

Questions
1

Hey there,

I had an active n8n API key per environment which worked just fine and was used at least once a day. But just now (starting Feb 19.) the API keys all expired at once.

I remember having seen a feature about the API requests in the recent release notes. There is now some new feature, where multiple (only ee I think) keys can be created and be set to expire a certain date.

My assumption: Maybe it just shows, that it would never expire but does within one week after migration?

Also, my production environment is still running on Version 1.75.1 and there the error does not exist.

The error states:

Authorization failed - please check your credentials
jwt malformed

Screenshot 2025-02-19 at 12.17.46 AM
Screenshot 2025-02-19 at 12.17.46 AM829×468 35.6 KB

Screenshot 2025-02-19 at 12.19.53 AM
Screenshot 2025-02-19 at 12.19.53 AM775×268 7.31 KB

Information on your n8n setup

  • n8n version: 1.78.1 and 1.80.0
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu 20.04 LTS
2

Assuming you meant 1.78.1 (not 1.78.01… I saw that was corrected now), is that the version affected, or is it the (currently still pre-release) version 1.80.0, or both?

3

Yes, updated it.
Both versions are affected.

4

Can concur, n8n API key fails to authorize with error ‘Authorization failed - please check your credentials’ in version 1.78.1, on Ubuntu Server 24.04 VM, n8n running on Docker, SQLite database, with n8n API token set at non-expiring.

I had to delete the API token and make a new one to get everything functioning again. Luckily I had few flows where I used this API key in.

5

Also happened on my instance

  • n8n version: 1.78.1
  • Licence: community with free extension
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main/queue
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu 24.04 LTS
6

I’ve had the same issue and just created a new token

7

Same for me since I update to 1.78.0

8

This sounds like a bug, I’ll escalate it.

1 Like
9

We will investigate this further. Though when I tried upgrading on n8n Cloud I did not encounter any issue with the API key. Might be affecting self-hosted solutions only.

3 Likes
11

Looking into this right now.

1 Like
12

Addressed the issue. Will create a patch ([email protected]) with the fix. In the mean time recreating the API key should work.

4 Likes
13

It works again. That went fast! Love it!

14

I still have the issue in 1.79.3

n8n version: 1.79.3
Database (default: SQLite): SQLite
n8n EXECUTIONS_PROCESS setting (default: own, main): main
Running n8n via (Docker, npm, n8n cloud, desktop app): Podman (Docker)
Operating system: Rocky Linux 9.5

15

Can you please elaborate? What error are you seeing? Does the api key with the problem start with n8n_api?

16

I upgraded to v 1.80.3 a few hours ago. On checking now the problem is not existing anymore.

1 Like
17

I had the same issue, just updated to SaaS version [email protected]
Working with no errors , didn’t need to recreate the API key.

2 Likes
18

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