N8n update broke n8n api

Questions
1

Describe the problem/error/question

I am on the community edition of n8n. When I updated n8n and it broke my n8n api credential. I have restarted, deleted the credential, deleted and created a new api key, reinstalled n8n, but nothing has worked. I can confirm that other credentials still function. Thanks in advance for the help.

What is the error message (if any)?

in n8n, the error is a refused connection and the suggestion that the service is offline (not the case). In the API playground, the key also does not work. Here, I obtain the following 401 error and then the 400 error in powershell

n8n_api_error_playground_web
n8n_api_error_playground_web1712×652 21.2 KB

In Powershell, the error shows as the following
n8n_api_error_playground
n8n_api_error_playground1020×222 8.73 KB

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:1.49.0
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):npm
  • **Operating system:Windows 11
2

Hi @Jonathan_Sherman

I just tested with 1.49.0 and it seems to be working fine.

CleanShot 2024-07-17 at 12.05.44@2x
CleanShot 2024-07-17 at 12.05.44@2x764×380 68.8 KB

CleanShot 2024-07-17 at 12.06.09@2x
CleanShot 2024-07-17 at 12.06.09@2x1532×1290 197 KB

1 Like
3

Yes, I don’t believe it is something that affects everyone. However, I still have not solved it. It would be great if someone at n8n could help.

1 Like
4

This is strange. Someone from n8n team will help you asap.

5

@Jonathan_Sherman Can you try using 127.0.0.1 instead of localhost?

6

127.0.0.1 results in an authorization failure
n8n_api_error_127.0.0.1

7

Hey @Jonathan_Sherman,

Can you share the full url you are using? The first issue was it couldn’t connect likely becuase it was usng ipv6 instead of ipv4 for localhost, The error now looks like the API key is incorrect.

8

Hi, thanks for that. Using http://127.0.0.1:5678 instead of localhost allows the credential to connect in my workflows. However, the API playground is still broken.

9

Perfect, I am not sure why the API playground would be broken though what error does that show?

10

That shows the 401 Error: Unauthorized

11

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