@kapa.ai my custom docker connectors are not working after upgrading from 0.50.33 to 1.1.0. I get very vague "Airbyte is temporarily unavailable. Please try again. (HTTP 502)" errors

Based on the information provided in the knowledge sources, it appears that several users have encountered similar issues when upgrading Airbyte versions. While there isn't a specific mention of upgrading from 0.50.33 to 1.1.0, I can provide some insights and potential solutions based on related experiences. 1. Docker startup errors: Some users reported issues with Docker startup after upgrading Airbyte versions. This could potentially affect custom Docker connectors as well. [Github Issue #32450](https://github.com/airbytehq/airbyte/issues/32450) 2. Server unavailability: The error message you're seeing ("Airbyte is temporarily unavailable. Please try again. (HTTP 502)") is similar to what others have experienced after upgrades. This could be related to issues with the Temporal service or other components. [Github Issue #44833](https://github.com/airbytehq/airbyte/issues/44833) 3. Custom connector compatibility: Upgrading Airbyte versions may sometimes cause issues with custom connectors, especially if there have been significant changes in the platform. [Forum Post](https://discuss.airbyte.io/t/3532) Here are some potential solutions you could try: 1. Check logs: Examine the logs of your Airbyte containers, especially the worker and temporal containers, for any specific error messages that might provide more insight into the issue. 2. Rollback: If possible, try rolling back to the previous version (0.50.33) to see if the issue resolves. This can help determine if the problem is specifically related to the upgrade. 3. Clean installation: As suggested by a user in one of the issues, you could try exporting your database, destroying the environment (removing all Docker containers and deleting the install folder), then reinstalling and importing your database. [Github Issue #32450](https://github.com/airbytehq/airbyte/issues/32450) 4. Check compatibility: Ensure that your custom Docker connectors are compatible with the new Airbyte version. You may need to update them to work with version 1.1.0. 5. Verify configurations: Double-check your

.env

file and Docker compose configurations to ensure they're correctly set for the new version. If these steps don't resolve the issue, you may need to reach out to Airbyte support or consult their documentation for more specific guidance on upgrading to version 1.1.0 with custom connectors.

I am facing the same problem, a custom source that was working totally fine cannot be added anymore, I am getting

Airbyte is temporarily unavailable. Please try again. (HTTP 502)

@Hsein Bitar I think I had to run a command like

kind load docker-image custom-docker-image -n airbyte-abctl

to get it to work again