Every time I try to develope a custom connector once I set i Airbyte #replication-ask-ai

Every time I try to develope a custom connector, o...

Yuki Kakegawa

10/16/2026, 3:34 PM

Every time I try to develope a custom connector, once I set it up, I get this error: "An unknown error has occurred". Is this a known bug? It's been a while since I started getting this. I'm using self hosted airbuyte

✅ 1

kapa.ai

10/16/2026, 3:34 PM

Thinking completed "An Unknown Error Has Occurred" in Connector Builder Yes, this is a known issue that has affected several self-hosted Airbyte users. The root cause depends on your deployment method: Most Common Cause: Ingress Misconfiguration (Kubernetes/Helm) Starting around version 1.7.x, a breaking change was introduced where the Connector Builder API (

/api/v1/connector_builder/...

) needs to be routed to a separate service (

airbyte-airbyte-connector-builder-server-svc

) rather than the main webapp service. If your ingress routes all traffic to the webapp, the builder API calls return 404/503 errors, which surface as "An unknown error has occurred." [Ingress breaking change] Fix: Update your Kubernetes Ingress to add a specific rule for the builder path:

Copy code

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: airbyte-ingress
spec:
  rules:
    - host: airbyte.your-domain.com
      http:
        paths:
          # Routes builder API traffic to the correct service
          - path: /api/v1/connector_builder
            pathType: Prefix
            backend:
              service:
                name: airbyte-airbyte-connector-builder-server-svc
                port:
                  number: 80
          # Fallback for all other UI traffic
          - path: /
            pathType: Prefix
            backend:
              service:
                name: airbyte-airbyte-webapp-svc
                port:
                  number: 80

[Ingress fix] If you're using an HTTPRoute (e.g., with Istio/Gateway API), the equivalent config is:

Copy code

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: airbyte
  namespace: airbyte
spec:
  parentRefs:
    - name: gateway
      namespace: istio-system
  hostnames:
    - "airbyte.example.com"
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /api/v1/connector_builder
      backendRefs:
        - name: airbyte-airbyte-connector-builder-server-svc
          port: 80
    - matches:
        - path:
            type: PathPrefix
            value: /
      backendRefs:
        - name: airbyte-airbyte-server-svc
          port: 8001

[HTTPRoute fix] Other Things to Check • Low-resource mode (
abctl
): If you're running Airbyte in low-resource mode via

abctl

, the connector builder service may be disabled even though the UI is still accessible. [Low-resource mode note] • Temporary workaround (abctl users): Downgrading to chart version

1.6.3

has worked for some users, though it may introduce other issues:

abctl local install --chart-version 1.6.3

[Downgrade workaround] Could you share more details about your deployment (Kubernetes/Helm,

abctl

, Docker Compose) and your Airbyte version? That would help narrow down the exact fix for your situation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Open in Slack

Previous Next