still having this issue after trying to install airbyte using the latest abctl version after trying to access it // HttpError { "i18nKey": "errors.http.notFound", "i18nParams": { "status": 404 }, "name": "HttpError", "requestId": "4jqEJZXqfhVtwdBDxQv3p2", "request": { "url": "/api/v1/workspaces/get", "method": "POST", "headers": { "Content-Type": "application/json" }, "data": { "workspaceId": "48e3540c-07e9-403d-a5b3-a4190b6362d7" } }, "status": 404, "response": { "message": "Internal Server Error: Could not find configuration for STANDARD_WORKSPACE: 48e3540c-07e9-403d-a5b3-a4190b6362d7.", "exceptionClassName": "io.airbyte.commons.server.errors.IdNotFoundKnownException",

Based on the error you're experiencing, it appears you're encountering a workspace configuration issue after installing Airbyte with abctl. The error message indicates that Airbyte cannot find the workspace configuration for the specified workspace ID. This issue is similar to problems documented in the knowledge sources. According to [Airbyte 1.6.0 and also to 1.6.1 fail to update Docker connectors](https://github.com/airbytehq/airbyte/issues/59196), users have experienced similar

IdNotFoundKnownException

errors where the system cannot find workspace configurations. However, your specific issue may also be related to a known ingress misconfiguration problem. According to [abctl v0.30.1 installs Airbyte v1.8.1 with incorrect ingress target](https://github.com/airbytehq/airbyte/issues/65539), recent versions of abctl have been generating ingresses that point to the wrong service (

airbyte-abctl-airbyte-webapp-svc

instead of

airbyte-abctl-airbyte-server-svc

), which causes HTTP 503/404 errors when trying to access the Airbyte UI/API. To troubleshoot your issue, I recommend: 1. Check your ingress configuration:

bash    kubectl describe ingress ingress-abctl -n airbyte-abctl

If it points to

airbyte-abctl-airbyte-webapp-svc

, you'll need to manually edit it to use

airbyte-abctl-airbyte-server-svc

instead. 2. Verify your workspace exists: The error suggests the workspace ID

48e3540c-07e9-403d-a5b3-a4190b6362d7

cannot be found in the database. This could indicate a database initialization issue. 3. Check if this is a fresh installation: If this is a new installation, the workspace may not have been properly created during setup. Unfortunately, the knowledge sources don't provide a complete solution for your specific workspace configuration error. You may need to check the Airbyte server logs for more details about why the workspace configuration is missing, or consider reaching out to the Airbyte community for additional support.