Renu Fulmali
11/26/2025, 9:40 AMkapa.ai
11/26/2025, 9:41 AMRenu Fulmali
11/26/2025, 9:52 AMkapa.ai
11/26/2025, 9:52 AMkapa.ai
11/26/2025, 9:52 AMRenu Fulmali
11/26/2025, 9:59 AMkapa.ai
11/26/2025, 10:00 AMkapa.ai
11/26/2025, 10:00 AM/api/v1/connector_builder_projects/resolve is not working even after exposing the connector endpoint, there are a few important points to consider based on the knowledge sources: 1. Correct Ingress Routing is Critical: Many users have reported that issues with the Connector Builder endpoints (including /resolve) are often due to incorrect Kubernetes Ingress configuration. The Ingress must specifically route /api/v1/connector_builder/ (note the trailing slash) to the airbyte-airbyte-connector-builder-server-svc service. If this is not set up, requests may be routed to the wrong service (such as the webapp), resulting in 404 or 5xx errors [[Ingress Example](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)]. Example Ingress snippet: 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: 8001 Make sure the rule for /api/v1/connector_builder/ comes before the catch-all / rule. 2. Endpoint Path Differences: The endpoint you mentioned (/api/v1/connector_builder_projects/resolve) is different from the one most commonly referenced in the documentation and issues (/api/v1/connector_builder/manifest/resolve). If your frontend is calling /api/v1/connector_builder_projects/resolve, ensure that your Airbyte version actually supports this endpoint, as some versions may have changed the API path [[Github Issue #65568](https://github.com/airbytehq/airbyte/issues/65568)]. 3. Version Compatibility: There have been reports of frontend/backend mismatches in certain Airbyte versions, where the frontend calls an endpoint that does not exist in the backend, resulting in 404 errors. This was especially noted in Airbyte 1.7.1, but similar issues may persist in later versions if the frontend and backend are not in sync [[Github Issue #63770](https://github.com/airbytehq/airbyte/issues/63770)]. 4. Service Health: Ensure that the airbyte-connector-builder-server pod is running and healthy. If the service is not up, the endpoint will not be reachable even with correct ingress rules. Summary: - Double-check your Ingress rules to ensure /api/v1/connector_builder/ is routed to the correct service. - Verify that your Airbyte version supports the /api/v1/connector_builder_projects/resolve endpoint. - Make sure all relevant pods are running and healthy. - If the issue persists, it may be due to a frontend/backend version mismatch or a bug in your Airbyte version. If you have already done all of the above and the endpoint still does not work, the knowledge sources do not provide a more specific solution for this exact endpoint, and you may need to consult the Airbyte GitHub issues for updates or consider downgrading to a version where the Connector Builder is known to work as expected.Renu Fulmali
11/26/2025, 10:03 AMkapa.ai
11/26/2025, 10:03 AMkapa.ai
11/26/2025, 10:04 AM/api/v1/connector_builder/manifest/resolve endpoint typically means that the HTTP method used (e.g., GET, POST) is not allowed for that endpoint. According to the knowledge sources, this endpoint is expected to be accessed via a POST request by the Connector Builder UI when testing or validating a connector [[Github Issue #63770](https://github.com/airbytehq/airbyte/issues/63770)]. Key things to check: 1. Ingress Configuration: Ensure your Kubernetes Ingress is correctly routing all /api/v1/connector_builder/ traffic to the airbyte-airbyte-connector-builder-server-svc service. If this is misconfigured, requests may be routed to the wrong service, which could return a 405 error [[Ingress Example](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)]. 2. HTTP Method: Make sure the request to /api/v1/connector_builder/manifest/resolve is a POST request, as this is the expected method for this endpoint. 3. Path Suffix: The path in your Ingress should be /api/v1/connector_builder/ (with a trailing slash) to ensure all subpaths, including /manifest/resolve, are routed correctly [[Github Issue #61677](https://github.com/airbytehq/airbyte/issues/61677)]. 4. Service Health: Confirm that the airbyte-connector-builder-server pod is running and healthy. If all of the above are correct and you are still seeing a 405 error, the knowledge sources do not provide further troubleshooting steps for this specific error. The most common root cause in similar reports has been incorrect Ingress routing or using the wrong HTTP method. If you need an example Ingress configuration, here is a reference: 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: 8001 [[Ingress Example](https://docs.airbyte.com/platform/1.8/deploying-airbyte/integrations/ingress-1-7#deploying-with-helm)] If you continue to experience issues, please provide more details about your Ingress configuration and the exact request being made.