Micky
07/22/2025, 8:01 PM{
"url": "<http://localhost:8000/workspaces/e49fd3de-1612-4390-b15f-87e35051c414/connections>",
"airbyteVersion": "1.7.1",
"errorType": "HttpError",
"errorConstructor": "ru",
"error": {
"i18nKey": "errors.http.notFound",
"i18nParams": {
"status": 404
},
"name": "HttpError",
"requestId": "fHrmFJsEcgy8V3GsVmcm8w",
"request": {
"url": "/api/v1/workspaces/get",
"method": "POST",
"headers": {
"Content-Type": "application/json"
},
"data": {
"workspaceId": "e49fd3de-1612-4390-b15f-87e35051c414"
}
},
"status": 404,
"response": {
"message": "Internal Server Error: Could not find configuration for STANDARD_WORKSPACE: e49fd3de-1612-4390-b15f-87e35051c414.",
"exceptionClassName": "io.airbyte.commons.server.errors.IdNotFoundKnownException",
"exceptionStack": [],
"rootCauseExceptionStack": []
}
},
"stacktrace": "HttpError: errors.http.notFound\n at Rme (<http://localhost:8000/assets/core-ebigvdmw88.js:56:1031>)",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36",
"featureFlags": {}
}
kapa.ai
07/22/2025, 8:01 PMId not found: Could not find configuration for STANDARD_WORKSPACE: 00000000-0000-0000-0000-000000000000.
and - io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find configuration for STANDARD_WORKSPACE: ...
These errors have been observed after upgrades or fresh installations, and sometimes after updating connectors or other resources. In some cases, users have had to downgrade to a previous version (e.g., 1.5.1) to resolve the issue, as the newer versions failed to properly recognize or create the workspace configuration in the database. This suggests a possible migration or initialization bug in recent Airbyte releases [[source]](https://github.com/airbytehq/airbyte/issues/59196). What you can try: - Double-check that the workspace with ID e49fd3de-1612-4390-b15f-87e35051c414
actually exists in your Airbyte instance. - Try creating a new workspace and see if you can create a connection within that new workspace. - If this is a fresh install or an upgrade, consider downgrading to a previous working version (such as 1.5.1) as a temporary workaround, as some users have reported this resolves the issue [[source]](https://github.com/airbytehq/airbyte/issues/59196). - If you are using custom database backends or have restored from a backup, ensure that all required migrations have been applied and that the workspace data is intact [[source]](https://github.com/airbytehq/airbyte/issues/49304). If the problem persists, it may be a bug in the recent Airbyte release, and you may want to follow or contribute to the ongoing discussions and issues on GitHub for updates and potential fixes [[source]](https://github.com/airbytehq/airbyte/issues/59196). Summary: This is a known issue in recent Airbyte versions where the workspace configuration cannot be found, resulting in 404 errors when creating connections. Workarounds include verifying workspace existence, creating new workspaces, or downgrading to a previous version until a fix is released.Micky
07/22/2025, 8:07 PMkapa.ai
07/22/2025, 8:07 PMkapa.ai
07/22/2025, 8:07 PMabctl
, you need to specify the desired version in your values.yaml
file and then run the install command with that file. The abctl
tool does not provide a direct flag to select a specific version, but you can control the version via the Helm chart configuration. Steps: 1. Edit your values.yaml
file Set the Airbyte version you want to use in the values.yaml
file. You can find available chart versions on [Airbyte ArtifactHub](https://artifacthub.io/packages/helm/airbyte/airbyte). 2. Install Airbyte with the specific version Run: bash abctl local install --values ./values.yaml
This will deploy Airbyte using the configuration (including version) specified in your values.yaml
file. Note: - If you have already installed a newer version, you may need to reset your environment to avoid database compatibility issues. This can be done by uninstalling Airbyte and removing the persisted data: bash abctl local uninstall --persisted rm -rf ~/.airbyte/
Then reinstall with your desired version as above [[source]](https://docs.airbyte.com/platform/1.6/contributing-to-airbyte/developing-locally#resetting-the-airbyte-developer-environment). - Downgrading may not always be seamless if there have been database migrations incompatible with older versions. Some users have reported issues when downgrading after an upgrade [[source]](https://github.com/airbytehq/airbyte/issues/58587). Summary: To downgrade, specify the version in your values.yaml
and reinstall using abctl local install --values ./values.yaml
. If you encounter issues, a full reset of your environment may be required.Micky
07/22/2025, 8:11 PMvalues. yaml
using abctl @kapa.aikapa.ai
07/22/2025, 8:11 PMkapa.ai
07/22/2025, 8:11 PMabctl
to automatically generate or locate a values.yaml
file for you. According to the documentation, you are expected to create your own values.yaml
file manually. The documentation provides examples and guidance on what to include in this file, but you need to create it yourself in a directory accessible during installation or upgrade. For example: yaml global: airbyteUrl: <https://airbyte.company.example>
You can find more detailed examples and references for what to include in your values.yaml
in the Airbyte documentation and the [Airbyte GitHub repository](https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/values.yaml) [[Next Installation Guide](https://docs.airbyte.com/platform/next/deploying-airbyte#3-create-a-valuesyaml-override-file)]. If you receive an error about not being able to read the values.yaml
file, ensure you are in the correct directory or provide the correct path to the file when running abctl
[[Troubleshooting abctl](https://docs.airbyte.com/platform/next/deploying-airbyte/troubleshoot-deploy#unable-to-read-values-from-yaml-file)].Micky
07/22/2025, 8:14 PMkapa.ai
07/22/2025, 8:14 PMkapa.ai
07/22/2025, 8:14 PMbash curl -X POST "<http://localhost:8000/api/v1/workspaces/create>" \ -H "Content-Type: application/json" \ -d '{"name": "My New Workspace"}'
Replace "My New Workspace"
with your desired workspace name. - After creation, you can switch between workspaces by editing the URL in your browser to use the new workspace ID (the part after /workspaces/
in the URL) [[Forum: Multitenancy in OSS](https://discuss.airbyte.io/t/2492)]. For more details and additional parameters (like data residency), refer to the [API reference](https://reference.airbyte.com/reference/workspaces#/). --- Note: - In Airbyte OSS, all workspace management (creation, updates) is done via API, not the UI. - In Airbyte Cloud, workspace management is available in the UI. If you need to associate a region or set data residency, include the dataResidency
parameter in your API request as shown in the documentation [[Associate a region to a workspace](https://docs.airbyte.com/platform/next/enterprise-setup/multi-region#step-3)].