Http errors after minor n8n upgrade

[jacobprecht]

Hi all, after a minor upgrade from 1.58.x to 1.59.3 we have a lot of execution errors http error 401 auth failed. The request looks like this:

Refreshing the bearer does not solve the problem. Does anybody here have any hints on this? ((hopefull))

Debug info

core

• n8nVersion: 1.59.3

• platform: npm

• nodeJsVersion: 20.17.0

• database: sqlite

• executionMode: regular

• concurrency: 999

• license: community

• consumerId: 00000000-0000-0000-0000-000000000000

storage

• success: all

• error: all

• progress: false

• manual: true

• binaryMode: filesystem

pruning

• enabled: true

• maxAge: 720 hours

• maxCount: 25000 executions

Generated at: 2024-09-20T10:17:38.546Z

[n8n]

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:

[jacobprecht]

@n8n

n8n versi

I have solved this now. The solution was to change the http node FROM no saved auth with manual added headers for the Authorize/Bearer TO saved header credential. The Bearer token was unchanged, so I am a bit puzzled as this was totally unhinted in the change log.

[mariana-na]

Hi @jacobprecht ,

Thanks for posting and for sharing your solution with the community!
We’ll review this and consider adding it to the release note notices.

[Jon]

Hey @jacobprecht,

If you go to to the settings for the node it should give you a version at the bottom. Which version of the HTTP Request node is it?

[jan]

New version [email protected] got released which includes the GitHub PR 10923.