The Get call /api/v1/jobs/get/{job_id} is 404 in d...
# ask-ai
d
The Get call /api/v1/jobs/get/{job_id} is 404 in docker-compose environment
u
The
GET /jobs/{jobId}
endpoint is used to get the status and details of a job in Airbyte. If you're getting a 404 error, it means the server can't find the requested resource. In this case, it could mean that the job with the provided
jobId
does not exist. Please ensure that the
jobId
you're using is correct. If you're sure that the
jobId
is correct, then there might be an issue with your Airbyte setup. There have been instances where users faced issues with the Airbyte API in a docker-compose environment. For example, in a [Github issue](https://github.com/airbytehq/airbyte/issues/37848), a user was able to resolve their issue by adding the
AIRBYTE_API_HOST
variable to the environment of the
airbyte-server
container. If you're still facing issues, it would be helpful to provide more details about your setup and the exact request you're making. This will help in diagnosing and resolving the issue.
d
@kapa.ai AIRBYTE_API_HOST=airbyte-server:8001/api/public This is AIRBYTE_API_HOST by deafult
u
The
AIRBYTE_API_HOST
environment variable is not explicitly defined in the knowledge sources provided. However, it is mentioned in the context of error messages and solutions related to Airbyte's API. In one of the [GitHub issues](https://github.com/airbytehq/airbyte/issues/38101), a user encountered a
500 Server Error: Internal Server Error
when using the API. The error message indicated that the system could not resolve the placeholder
${AIRBYTE_API_HOST}
. The user resolved this issue by adding
AIRBYTE_API_HOST=${AIRBYTE_API_HOST}
to the
environment
section of the
server
service in the
docker-compose.yml
file. In another [GitHub issue](https://github.com/airbytehq/airbyte/issues/37848), a user fixed a similar issue by adding the
AIRBYTE_API_HOST
variable to the environment of the
airbyte-server
container. In a [forum post](https://discuss.airbyte.io/t/763), a user suggested setting the
INTERNAL_API_HOST
to the ingress domain when setting up Airbyte on a private GKE using kustomize. The default value for
INTERNAL_API_HOST
was given as
airbyte-server:8001
. Based on these sources, it seems that the
AIRBYTE_API_HOST
environment variable should be set to the host of the Airbyte server. However, the exact value would depend on your specific setup. If you're running Airbyte locally, it might be
localhost:8001
. If you're running it on a remote server, it would be the URL of that server. If you're running it in a Docker container, it might be the name of that container. Please note that these are just examples based on the information provided in the knowledge sources. You should check the Airbyte documentation or consult with your system administrator to determine the correct value for your specific situation.