@kapa.ai why can’t I load connector_documentation when I deploy airbyte locally? It seems I can’t access

<http://localhost:8080/api/v1/connector_documentation/get>

Based on the information provided in the knowledge sources, it appears that you're encountering an issue with accessing the Airbyte API when deploying locally. There are a few potential reasons for this: 1. Incorrect API endpoint: The correct endpoint for the public API in a local deployment is

<http://localhost:8000/api/public/v1/>

instead of

<http://localhost:8080/api/v1/>

. This is mentioned in the [GitHub discussion about the Python SDK](https://github.com/airbytehq/airbyte/discussions/45182). 2. Port forwarding: If you're using Kubernetes for local deployment, you might need to set up port forwarding. The [documentation on deploying Airbyte](https://docs.airbyte.com/deploying-airbyte/#6-set-up-port-forward-for-ui-access) mentions that you should run a command similar to:

kubectl --namespace airbyte port-forward $POD_NAME 8080:$CONTAINER_PORT

This would allow you to access the UI at

<http://127.0.0.1:8080>

. 3. Docker Compose: If you're using Docker Compose for local deployment, the API should be accessible at

<http://localhost:8000/api/v1/>

. To resolve your issue, try the following: 1. Ensure you're using the correct URL:

<http://localhost:8000/api/public/v1/connector_documentation/get>

2. If you're using Kubernetes, make sure you've set up the proper port forwarding. 3. Check if your Airbyte instance is running correctly by accessing the UI at

<http://localhost:8000>

(for Docker Compose) or

<http://127.0.0.1:8080>

(for Kubernetes with port forwarding). If you're still encountering issues, you might want to check the logs of your Airbyte containers for any error messages that could provide more insight into the problem.

A message from kapa.ai

Based on the information provided in the knowledge sources, it appears that you're encountering an issue with accessing the Airbyte API when deploying locally. There are a few potential reasons for this: 1. Incorrect API endpoint: The correct endpoint for the public API in a local deployment is

<http://localhost:8000/api/public/v1/>

instead of

<http://localhost:8080/api/v1/>

. This is mentioned in the [GitHub discussion about the Python SDK](https://github.com/airbytehq/airbyte/discussions/45182). 2. Port forwarding: If you're using Kubernetes for local deployment, you might need to set up port forwarding. The [documentation on deploying Airbyte](https://docs.airbyte.com/deploying-airbyte/#6-set-up-port-forward-for-ui-access) mentions that you should run a command similar to:

kubectl --namespace airbyte port-forward $POD_NAME 8080:$CONTAINER_PORT

This would allow you to access the UI at

<http://127.0.0.1:8080>

. 3. Docker Compose: If you're using Docker Compose for local deployment, the API should be accessible at

<http://localhost:8000/api/v1/>

. To resolve your issue, try the following: 1. Ensure you're using the correct URL:

<http://localhost:8000/api/public/v1/connector_documentation/get>

2. If you're using Kubernetes, make sure you've set up the proper port forwarding. 3. Check if your Airbyte instance is running correctly by accessing the UI at

<http://localhost:8000>

(for Docker Compose) or

<http://127.0.0.1:8080>

(for Kubernetes with port forwarding). If you're still encountering issues, you might want to check the logs of your Airbyte containers for any error messages that could provide more insight into the problem.

I can access the connector but the issue only concerns the documentation.