N8N 2.1.2 broke my http request

Questions
, ,
1

I recently updated my n8n instance to version [2.1.2], and I’m facing two major issues that weren’t present before. I’m wondering if anyone else is experiencing this or knows a fix.

  1. HTTP Request Failures (Shopify) Some of my HTTP Request nodes, specifically simple requests to Shopify, have stopped working. These exact nodes were working perfectly before the update.
    Error Message: [The resource you are requesting could not be found]
    What I tried: I checked the credentials and URL. I even generated a completely new Shopify access token to rule out any issues on the Shopify side, but the requests still fail.
  2. Stability / Offline Issues Since the update, my n8n has gone offline about 5 times. It seems to crash or restart unexpectedly.
    Setup: [e.g., Self-hosted on Docker / n8n Cloud / Desktop App]
    Has anyone encountered similar problems with the v2.x update? Any advice on logs to check or known breaking changes regarding HTTP requests would be greatly appreciated.

Describe the problem/error/question

What is the error message (if any)?

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.)

Skærmbillede 2025-12-23 kl. 10.55.48
Skærmbillede 2025-12-23 kl. 10.55.481496×936 71.5 KB

Share the output returned by the last node

Information on your n8n setup

2

V2 changed a lot of things with how HTTP requests work, especially with authentication and headers. The Shopify error your getting sounds like maybe the authentication method changed or theres some new required parameters. I would check the changelog for 2.1.2 to see if theres any breaking changes for HTTP nodes, and also try comparing your node settings to a fresh HTTP request node to see if any new fields were added that need to be filled. For the stability issues, that sounds like it could be a memory problem or somthing with how the executions are being processed in v2. Maybe check your Docker logs to see what’s causing the crashes

1 Like