@kapa.ai I am having an issue with my connector:

│ 2026-08-19 08:25:18,232 [io-executor-thread-4]    ERROR    i.a.s.a.ApiHelper(execute):47 - Unexpected Exception                                                                                                    │
│ io.airbyte.commons.server.errors.NotFoundException: Could not find any documentation for connector <http://acrdataplatformkg.azurecr.io/source-moloco-reporting|acrdataplatformkg.azurecr.io/source-moloco-reporting>                                                            │
│     at io.airbyte.commons.server.handlers.ConnectorDocumentationHandler.getConnectorDocumentation(ConnectorDocumentationHandler.java:71)                                                                           │
│     at io.airbyte.server.apis.ConnectorDocumentationApiController.lambda$getConnectorDocumentation$0(ConnectorDocumentationApiController.java:43)                                                                  │
│     at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.kt:32)                                                                                                                                                   │
│     at io.airbyte.server.apis.ConnectorDocumentationApiController.getConnectorDocumentation(ConnectorDocumentationApiController.java:43)                                                                           │
│     at io.airbyte.server.apis.$ConnectorDocumentationApiController$Definition$Exec.dispatch(Unknown Source)                                                                                                        │
│     at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invokeUnsafe(AbstractExecutableMethodsDefinition.java:461)                                                              │
│     at io.micronaut.context.DefaultBeanContext$BeanContextUnsafeExecutionHandle.invokeUnsafe(DefaultBeanContext.java:4354)                                                                                         │
│     at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:272)                                                                                                                             │
│     at io.micronaut.web.router.DefaultUriRouteMatch.execute(DefaultUriRouteMatch.java:38)                                                                                                                          │
│     at io.micronaut.http.server.RouteExecutor.executeRouteAndConvertBody(RouteExecutor.java:488)                                                                                                                   │
│     at io.micronaut.http.server.RouteExecutor.lambda$callRoute$5(RouteExecutor.java:465)                                                                                                                           │
│     at io.micronaut.core.execution.ExecutionFlow.lambda$async$1(ExecutionFlow.java:87)                                                                                                                             │
│     at io.micronaut.core.propagation.PropagatedContext.lambda$wrap$3(PropagatedContext.java:211)                                                                                                                   │
│     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)                                                                                                                   │
│     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)                                                                                                                   │
│     at java.base/java.lang.Thread.run(Thread.java:1583)

How to fix that?

Connector Documentation Not Found Error The error you're seeing is:

io.airbyte.commons.server.errors.NotFoundException: Could not find any documentation for connector acrdataplatformkg.azurecr.io/source-moloco-reporting

This indicates that Airbyte's

ConnectorDocumentationHandler

cannot find documentation for your custom connector hosted in a private Azure Container Registry (

acrdataplatformkg.azurecr.io

). Why This Happens Starting with Airbyte v2.1, connector documentation displayed in the UI is fetched directly from GitHub (docs.airbyte.com). For custom connectors hosted in a private registry, there is no corresponding documentation entry in the official Airbyte connector registry or GitHub docs, so the lookup fails with a

NotFoundException

. [Airbyte 2.1 Release] This is also related to the broader issue of air-gapped or private-registry environments where Airbyte cannot resolve connector documentation from external sources. [GitHub Issue] What You Can Do The knowledge sources do not contain a definitive step-by-step fix for custom connectors in private registries, but based on the available information, here are the recommended approaches: 1. Check if this is a non-blocking error: The

NotFoundException

on the documentation endpoint is typically a UI-level error (the docs panel fails to load), but it should not block syncs from running. Verify whether your actual sync jobs are still functioning. 2. Ensure your connector image has bundled documentation: As a fallback, Airbyte falls back to "previously bundled docs" when GitHub is unreachable. For custom connectors, you should ensure your connector image includes documentation. [Airbyte 2.1 Release] 3. Report/track the issue: This appears to be an open known issue for air-gapped/private-registry setups. You can follow or contribute to the tracking issue: [GitHub Issue] 4. Join the community: For additional help, join the Airbyte Community Slack or, if you're an Airbyte Cloud/Enterprise customer, open a support ticket. > Note: The knowledge sources do not contain explicit documentation on how to register custom connector documentation for private registry connectors. I'd recommend reaching out via the Slack community or support for a more definitive resolution. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai Is this a reason for failing the creation of a source in Airbyte? I am trying to create a new connector and the creation fails with the following message:

An unknown error occurred. (HTTP 504)

The pod responsible for running the check operation is still running.

HTTP 504 Error When Creating a Custom Connector The

NotFoundException

for connector documentation is not the cause of your HTTP 504 error. These are two separate issues. The HTTP 504 (Gateway Timeout) error when adding a custom connector typically occurs because the "Get Spec" job (or connection check) is taking too long to complete, causing the gateway to time out before the operation finishes. [Custom Connectors Docs] Common Causes The fact that the pod is still running when the 504 occurs points to the pod being unable to complete its work and report back in time. Based on the knowledge sources, here are the most likely causes: 1. Docker image architecture mismatch: If you built your image on an ARM machine (e.g., Apple M1/M2) but your Airbyte instance runs on

linux/amd64

, the connector pod will fail or hang. The fix is to build a multi-platform image:docker buildx build --platform linux/amd64 --push -t your-registry/image-name:tag .[Forum Post] 2. Private registry authentication issue: Since your image is on Azure Container Registry (

acrdataplatformkg.azurecr.io

), the pod may be unable to pull the image. Verify that your Airbyte instance is properly authenticated to your ACR. [Forum Post] 3. Docker image tag: Avoid using the

latest

tag — use an explicit version number instead. [Forum Post] 4. Docker image naming: Ensure your image name contains no underscores (

_

) or stacked folder paths in the repository name. [Forum Post] 5. Network/ingress timeout: If you're accessing Airbyte through an ingress or reverse proxy, the gateway timeout may be triggered by the proxy before Airbyte finishes. Try bypassing the ingress and accessing Airbyte directly. [Forum Post] Recommended Next Steps • Check the server and worker pod logs for more detailed error messages beyond the generic 504. • Try manually pulling the image on your Airbyte instance to confirm registry access:docker pull acrdataplatformkg.azurecr.io/source-moloco-reporting:tag • Verify the architecture of your Docker image matches your Airbyte host environment. image 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

how to force the check operation to not fail with a short timeout or to run? This check operation is actually running the request to the api that takes some time to process

Extending the Check Operation Timeout The knowledge sources provide several configuration options to address this, depending on your deployment type. 1. Increase the Nginx Ingress Timeout (Kubernetes) The nginx ingress has a default timeout of 60 seconds. Add these annotations to your Ingress resource:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: airbyte-ingress
  namespace: airbyte
  annotations:
    nginx.ingress.kubernetes.io/proxy-read-timeout: '600'
    nginx.ingress.kubernetes.io/proxy-send-timeout: '600'
    nginx.ingress.kubernetes.io/proxy-connect-timeout: '600'

[GitHub Issue] 2. Increase the Connector Sidecar Timeout The connector sidecar has an internal timeout (

SIDECAR_FILE_TIMEOUT_MINUTES

, default 9 minutes) that can cause the check pod to be killed even if it's still running. You can override it by building a custom sidecar image:

FROM airbyte/connector-sidecar:<your-version>

ENV SIDECAR_FILE_TIMEOUT_MINUTES=30
ENV SIDECAR_FILE_TIMEOUT_WITHIN_SYNC_MINUTES=60

[GitHub Issue] 3. Increase the Airbyte Server Timeout (Helm)

server:
  httpIdleTimeout: 20m
  extraEnv:
    - name: READ_TIMEOUT
      value: 30m

[GitHub Issue] 4. Docker Deployment — Proxy Timeout If you're running Airbyte behind a proxy on Docker, set:

BASIC_AUTH_PROXY_TIMEOUT=600

[Forum Post] Important Caveat The knowledge sources do not explicitly mention a way to make the check operation fully asynchronous (i.e., polling-based instead of blocking). This has been requested as a feature but does not appear to be implemented yet. [GitHub Issue] The most reliable combination is to increase both the ingress timeout and the sidecar timeout, as the sidecar timeout can kill the pod independently of the gateway timeout. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.