CircleCI "Error resolving orb" - Fix Orb Version & Access

CircleCI found the orb reference but could not resolve it to a published version. The version does not exist, the orb is uncertified and your org blocks those, or it is private and the pipeline lacks access.

What this error means

Validation fails resolving the orb, not the element inside it. The named orb or version cannot be fetched from the registry, so the whole config is rejected.

Error resolving orb 'circleci/node@9.9.9':
orb not found, or version does not exist
Error: Config is invalid

Common causes

Version does not exist

You pinned a version (@9.9.9) that was never published, or used a volatile tag the registry no longer serves. Only published semver versions resolve.

Uncertified orbs disabled for the org

Organization security settings can restrict pipelines to certified (CircleCI-namespace) orbs. A third-party orb then fails to resolve until allowed.

Private orb without access

A private namespace orb only resolves for pipelines in that org with the right access. Cross-org or fork pipelines cannot see it.

How to fix it

Pin a version that exists

List published versions and pin a real one.

circleci orb info circleci/node      # shows latest + versions
# then pin, e.g.
orbs:
  node: circleci/node@5.2.0

Allow uncertified orbs (org setting)

1. Open Organization Settings → Security in the CircleCI UI.
2. Enable "Allow uncertified orbs" if your org policy permits third-party orbs.
3. Otherwise switch to a certified equivalent in the circleci/ namespace.

Confirm access for private orbs

Make sure the pipeline runs in the owning org and the orb namespace grants access. Fork PRs cannot read private orbs.

How to prevent it

• Pin orbs to explicit published versions, never a guessed one.
• Document your org’s uncertified-orb policy so contributors know.
• Avoid private orbs in workflows that must run on fork PRs.

Related guides