Forge Login Failure - SSL cert issue

Forge
, , ,
1

I am getting the below error while logging in Forge with the right email ID and API key.

Error: self-signed certificate in certificate chain

Rerunning the command with --verbose may give more details.

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

Error: self-signed certificate in certificate chain

at TLSSocket.onConnectSecure (node:\_tls_wrap:1679:34)

at TLSSocket.emit (node:events:518:28)

at TLSSocket.emit (node:domain:489:12)

at TLSSocket.\_finishInit (node:\_tls_wrap:1078:8)

at ssl.onhandshakedone (node:\_tls_wrap:864:12)
2

I’ve recently encountered the same problem - is there a solution? thanks

3

Hey @Vishwa, @aht, and anyone else with this problem,

The error about “self-signed certificate” points to configuration in your corporate network. We’ve provided some guidance about that here:

If you’ve read that and are lost on how to “disable TLS inspection”, that’s pretty much a network configuration task done by your security team. Ask them to add an SSL/TLS decryption exclusion/bypass rule for the following endpoint:

  • Host: forge-outbound-proxy.services.atlassian.com
  • Protocol/Port: HTTPS (443)

You might be able to do this in local Node configuration via:

export NODE_EXTRA_CA_CERTS="/path/to/your/corporate-ca.pem"

That means you have to find the self-signed certificate in your browser settings. Or it’s another thing you need to ask IT.

Or, maybe you can obtain a Cloud Development Environment like GitHub Codespaces or Google Cloud Workspaces (there are many, many options and Atlassian has no formal recommendation in this domain) that is outside of your corporate network. These are increasingly popular in the age of AI where the environments are used to isolate coding agents.