@kapa.ai Airbyte cliud is throwing this error on the create source page: // HttpError { "i18nKey": "errors.http.internalServerError", "i18nParams": { "status": 500 }, "name": "HttpError", "requestId": "qouFvy8nfW6jSQsbGDjcp8", "request": { "url": "/api/v1/source_definitions/list_enterprise_source_stubs", "method": "post" }, "status": 500, "response": { "message": "Internal Server Error: java.io.IOException: HTTP error fetching enterprise sources", "exceptionClassName": "java.lang.RuntimeException", "exceptionStack": [], "rootCauseExceptionStack": [] } }

Based on the information provided in the knowledge sources, this error appears to be related to an issue with fetching enterprise source definitions in Airbyte. The error you're encountering is similar to the one described in [this GitHub issue](https://github.com/airbytehq/airbyte/issues/51511). The error occurs when trying to list enterprise source stubs, which is part of the process of creating a new source in Airbyte. The HTTP 500 Internal Server Error suggests that there's a problem on the server side. While the exact cause isn't clear from the available information, here are a few potential reasons and solutions based on the knowledge sources: 1. Network connectivity: There might be issues connecting to the enterprise source registry. Ensure that your Airbyte instance has proper network connectivity. 2. Environment variables: The error could be related to unresolved environment variables. Make sure that all necessary environment variables are properly set, especially

AIRBYTE_API_HOST

if you're running Airbyte on-premises. 3. Permissions: The 403 error mentioned in the GitHub issue suggests there might be permission issues. Verify that your Airbyte instance has the correct permissions to access the enterprise source registry. 4. Version compatibility: Ensure you're using a compatible version of Airbyte. Some users reported that downgrading to an earlier version resolved the issue. 5. Temporary server issue: It's possible that this is a temporary issue with Airbyte's servers. You could try again later or reach out to Airbyte support if the problem persists. If the issue continues, you may want to check the Airbyte server logs for more detailed error messages. Additionally, you could try restarting the Airbyte server pod if you're running on Kubernetes, as this resolved a similar issue for some users. If none of these solutions work, it would be best to report this issue to the Airbyte team through their GitHub repository or support channels, providing them with the full error message and your Airbyte version and deployment method.