Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Platform-wide OAuth failure: "Protocol https not supported" breaking all workflows [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28784•Fetched 2026-04-22 08:03:14
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Author
HamzaShahbazTMHamzaShahbazTM
Participants
HamzaShahbazTMHamzaShahbazTMkrisn0xkrisn0xn8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×2mentioned ×2subscribed ×2closed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

  • Error occurs before workflow execution (during authentication phase)
  • error: all
  • The error occurs during OAuth callback, not within workflow logic
RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

Upgrading n8n to the latest version may resolve the OAuth issues due to potential incompatibilities in the current version.

Guidance

  • Verify the OAuth callback configuration to ensure it is correctly set up for HTTPS requests.
  • Check the n8n documentation for any known issues related to OAuth in version 1.123.27.
  • Consider upgrading n8n to the latest version, as the instance is currently 16 versions behind, which may be causing the compatibility issues.
  • Test a single workflow with OAuth connection after upgrading to confirm if the issue is resolved.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be specific to the version of n8n being used, and upgrading to the latest version may resolve the issue. However, it is also possible that there is a configuration issue with the OAuth callback handling.

Recommendation

Apply workaround: Upgrade to the latest version of n8n, as the current version is outdated and may be causing the OAuth incompatibility issues. This is because the instance is 16 versions behind, and upgrading may resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

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

#model compatibility#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Platform-wide OAuth failure: "Protocol https not supported" breaking all workflows [2 comments, 3 participants]