Platform-wide OAuth failure: "Protocol https not supported" breaking all workflows

[HamzaShahbazTM]

Describe the problem/error/question

We are currently experiencing a platform-wide issue with n8n.

All workflows that rely on OAuth (Google Sheets, etc.) are failing. This is affecting previously working workflows as well as new credential connections.

The issue does not appear to be related to any specific workflow and seems to be at the n8n instance or OAuth handling level.

What is the error message (if any)?

Protocol "https:" not supported. Expected "undefined"

Please share your workflow/screenshots/recording

• Issue affects all workflows using OAuth (e.g. Google Sheets)
• Existing workflows that were previously working are now failing
• New OAuth credential connections fail during callback
• Error occurs before workflow execution (during authentication phase)

(Workflows not included as this is not specific to any single workflow)

Share the output returned by the last node

Protocol "https:" not supported. Expected "undefined"

Debug info

core

• n8nVersion: 1.123.27
• platform: docker (cloud)
• nodeJsVersion: 24.13.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: 50
• license: enterprise (sandbox)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 720 hours
• maxCount: 25000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
• isTouchDevice: false

Additional context

• Existing credentials are also failing (not just new ones)
• The error occurs during OAuth callback, not within workflow logic
• The instance is currently ~16 versions behind
• No recent workflow-level changes were made
• Issue is blocking all automation workflows

Expected behavior

OAuth connections and workflows should function normally, allowing HTTPS requests and integrations like Google Sheets to execute successfully.

Suspected causes

1. Outdated n8n version causing OAuth incompatibility
2. OAuth callback handling bug in this version
3. Possible mismatch in OAuth redirect handling

Request

Could you please:

1. Confirm if this is a known issue with this version
2. Upgrade n8n to the latest version
3. Verify OAuth callback configuration if needed

[n8n-assistant]

Hey @HamzaShahbazTM,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-7799".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-7799

[krisn0x]

Hey @HamzaShahbazTM ,

Thank you for reaching out! It looks like this issue might be more of a support request rather than a bug report. For general support, troubleshooting, or questions, we recommend raising your request on our community support forum.

The forum is a great place to connect with both our team and other community members who can help out. You might even find answers to similar questions there!

For issues related to n8n Cloud like billing, instances going offline or connection issues, please email help@n8n.io as we are not able to access your cloud account logs or workflows from here.

We’ll go ahead and close this issue to keep the tracker focused on bug reports. Feel free to join the conversation on the forum, and let us know if you have any further concerns or questions.

Thanks again for being part of the n8n community!