TLS Error with Octokit but not Native Fetch

Question

I am in the process of upgrading a job script that previously ran using NodeJS 16.x, upgrading to NodeJS 22.x.

This is a pretty simple script that contains some API calls to GitHub using Octokit. The issue is that when running this script using Node 22, I am now getting TLS errors where It was not previously. This script is executed behind an enterprise proxy.

Sample code: package.json

  "dependencies": {
    "https-proxy-agent": "7.0.6",
    "node-fetch": "3.3.2",
    "octokit": "5.0.2"
  }

index.js

const { HttpsProxyAgent } = require("https-proxy-agent");
const { Octokit } = require("octokit");

async function main(argv) {
  process.env["NODE_TLS_REJECT_UNAUTHORIZED"] = 0;
  
  const token = process.env["AUTH_TOKEN"];
  const testProxy = process.env["HTTPS_PROXY"];
  const testProxyAgent = new HttpsProxyAgent(testProxy);

  // TEST #1: Using fetch to make a request
  const testHeaders = {
    Authorization: `bearer ${token}`,
    "Content-Type": "application/json",
  };
  const test1Response = await fetch(
    "https://api.github.com/repos/<my org>/<my repo>",
    {
      method: "GET",
      headers: testHeaders,
      agent: testProxyAgent,
    },
  );
  const test1ResponseText = await test1Response.text();
  console.log(`Response #1: [${test1ResponseText}]`);

  // TEST #2: Using Octokit to make a request
  const testGithubClient = new Octokit({
    auth: token,
    request: {
      agent: testProxyAgent,
    },
  });
  const test2response = await testGithubClient.rest.repos.get({
    owner: "<my org>",
    repo: "<my repo>",
  });
  console.log(`Response #2: [${JSON.stringify(test2response.data)}]`);
}

Test #1 above works fine and produces the expected result. Test #2 produces an error:

RequestError [HttpError]: Client network socket disconnected before secure TLS connection was established
  <stack_trace>
  status: 500,

I'm clearly using a proxy for both calls but is Octokit not handling the proxy correctly?

Ben · Accepted Answer · 2025-05-29 14:19:47Z

0

This is not a direct answer to my question because I still don't know why but the workaround that I ended up using was passing overriding fetch to a custom implementation (using the native fetch()):

const githubClient = new Octokit({
  auth: token,
  request: {
    agent: proxyAgent,
    fetch: fetch,
  },
});

answered May 29 at 14:19

Ben

2,7875 gold badges23 silver badges38 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

TLS Error with Octokit but not Native Fetch

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related