@kapa.ai we're getting 403 error after upgrading from 1.8.3 to 2.0.1

"data": {
      "workspaceId": "xxxxx"
    }
  },
  "status": 403,
  "response": {
    "message": "Forbidden",
    "_links": {
      "self": {
        "href": "/api/v1/connector_builder_projects/list",
        "templated": false
      }
    },
    "_embedded": {
      "errors": [
        {
          "message": "Forbidden"
        }
      ]
    }
  }
}

The knowledge sources don’t describe a 403 on

/api/v1/connector_builder_projects/list

specifically for 2.0.1, so I can’t say exactly why it’s happening in your case. I can only point to related, documented 403 issues and fixes. 1. Ingress / routing issues (most likely if you’re self‑managed) In 1.7+ there was a breaking change around how Connector Builder traffic is routed. If ingress isn’t updated correctly, you can see 403/404 errors when using the Connector Builder APIs. [[Ingress 1.7+](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/ingress-1-7)] For 1.7.x, users had to: - Route

/api/v1/connector_builder/

to

airbyte-airbyte-connector-builder-server-svc

- Route

/

(and other API paths) to

airbyte-airbyte-server-svc

[[403 issue](https://github.com/airbytehq/airbyte/issues/61677)] Example Ingress rule that fixed 403s for others (adjust host/annotations to your setup): [[403 issue](https://github.com/airbytehq/airbyte/issues/61677)]

yaml    - path: /api/v1/connector_builder/      pathType: Prefix      backend:        service:          name: airbyte-airbyte-connector-builder-server-svc          port:            number: 80    - path: /      pathType: Prefix      backend:        service:          name: airbyte-airbyte-server-svc          port:            number: 80

If you’re using a custom ingress / load balancer, double‑check that: -

/api/v1/connector_builder/

is routed to the connector‑builder service, and -

/api/v1/connector_builder_projects/*

is still going to the main server service (not accidentally to the builder service). A user in 1.7.1 hit 404s until they ensured the trailing

/

and correct backend mapping. [[403 issue](https://github.com/airbytehq/airbyte/issues/61677)] 2. Known 403s in 2.0 (but different context) Release notes for 2.0 mention a fix for 403s seen by workspace admins who only had access to some workspaces, but that’s about UI access to workspaces, not Connector Builder APIs. [[2.0 fixes](https://docs.airbyte.com/release_notes/v-2.0#fixes)] There’s also an open discussion about 403s when using a published custom connector vs. tests in the Builder, but no official fix yet. [[403 discussion](https://github.com/airbytehq/airbyte/discussions/68598)] Given the above, the only concrete, documented remediation steps I can offer are: - If you’re self‑managed with custom ingress / proxy (NGINX, ALB, etc.): - Re‑verify your ingress rules against the “Update ingress for version 1.7 and later” doc and the examples from the 1.7.x 403 issue. [[Ingress 1.7+](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/ingress-1-7); [403 issue](https://github.com/airbytehq/airbyte/issues/61677)] - Ensure

/api/v1/connector_builder/

goes to the connector‑builder service and that

/api/v1/connector_builder_projects/list

is still handled by the main server service. - If you’re on Airbyte Cloud or a stock abctl/Helm install with no custom ingress changes: - The knowledge sources don’t provide a documented 2.0.1‑specific cause or fix for this 403. I’d recommend opening a GitHub issue or discussion and including: - Airbyte version (2.0.1), deployment method (Cloud / abctl / Helm / custom K8s) - Exact request path (

/api/v1/connector_builder_projects/list

) - Whether Connector Builder tests work but the published source fails (similar to the discussion). [[403 discussion](https://github.com/airbytehq/airbyte/discussions/68598)] If you can share whether you’re using Helm/abctl and any custom ingress config, I can help you map it more directly to the documented examples.

@kapa.ai We already have that ingress

apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
  creationTimestamp: "2025-09-30T07:48:16Z"
  generation: 3
  name: ingress-abctl
  namespace: airbyte-abctl
  resourceVersion: "7173611"
  uid: cee9cb6a-e559-4e25-925f-c657ab38964a
spec:
  ingressClassName: nginx
  rules:
  - http:
      paths:
      - backend:
          service:
            name: airbyte-abctl-airbyte-connector-builder-server-svc
            port:
              name: http
        path: /api/v1/connector_builder
        pathType: Prefix
      - backend:
          service:
            name: airbyte-abctl-airbyte-server-svc
            port:
              name: http
        path: /
        pathType: Prefix

We're getting 403 when accessing Builder and Sources in Workspace settings

A message from kapa.ai