Hi everyone, I'm creating a custom connector, now I'm working in my local with abctl, I already published the connector but when I try to get the streams of the source I'm receiving this error:

Response body: {"status":500,"type":"<https://reference.airbyte.com/reference/errors>","title":"unexpected-problem","detail":"An unexpected problem has occurred. If this is an error that needs to be addressed, please submit a pull request or github issue.","documentationUrl":null,"data":{"message":"Something went wrong in the connector. logs:Error starting the sync. This could be due to an invalid configuration or catalog. Please contact Support for assistance. Error: md5 checksum does not match.{'expected_checksum': '45d33ca8837855285050cc5d13e483a6', 'actual_checksum': '09164aa2de45204acec74fd14eb82669', 'code_text':

I tried like 10 times but I don't know why is failing, the checksum is in the db but I don't know why he is updating that value after the publish. Could you help me? Thank you

The knowledge sources don’t contain a direct description of this specific

md5 checksum does not match

error for custom connectors, so I can’t give a definitive root cause. However, there is a very similar OSS issue where calling “Get stream properties” against a connector returns a 500 with the same generic

unexpected-problem

wrapper and an inner message like “Something went wrong in the connector. See the logs for more details.”[[Get stream API](https://github.com/airbytehq/airbyte/issues/66688)] Given what we do know: - The 500 is coming from the connector, not the platform itself. The platform just wraps it in the

unexpected-problem

error type.[[Get stream API](https://github.com/airbytehq/airbyte/issues/66688)] - The message explicitly says:

Error starting the sync. This could be due to an invalid configuration or catalog.

That strongly suggests the checksum is being used to validate either: - the connector’s code / manifest vs. what was registered when you published, or - the catalog / spec vs. what Airbyte expects for that connector version. Because the docs and issues provided don’t document this checksum mechanism, I can’t say exactly where it’s stored or how it’s computed. Given those limits, here’s what you can concretely do next in your local

abctl

setup: 1. Check the connector logs for the real stack trace The platform error is generic; the detailed cause will be in the connector container logs (source image) at the time you call “Get streams” / “Get stream properties”. The similar issue explicitly notes that the only real clue is in the connector logs.[[Get stream API](https://github.com/airbytehq/airbyte/issues/66688)] - Use

abctl

/

docker logs

on the source container and look for the first stack trace around the checksum message. 2. Ensure the published image matches what Airbyte has cached Since the error mentions

expected_checksum

vs

actual_checksum

, it’s likely Airbyte is comparing: - what it expects for this connector version (from its internal DB / cache), vs. - what it actually sees when it runs the connector. Typical situations that could cause this (inferred, not documented in the sources): - You rebuilt the image with the same version / name after publishing, so the binary content changed but Airbyte still has the old checksum cached. - The connector definition in Airbyte (via

abctl

) points to a tag that no longer matches the image you’re running. Since the knowledge sources don’t describe the exact cache behavior, I can’t give a guaranteed fix, but the closest related 500-error issue was resolved by clearing server cache / restarting.[[HTTP 500 add connector](https://github.com/airbytehq/airbyte/issues/54058)] Try: - Restart Airbyte server (and webapp) in your

abctl

environment so any in-memory cache is cleared.[[HTTP 500 add connector](https://github.com/airbytehq/airbyte/issues/54058)] - If possible, bump the connector version (e.g.

0.1.0

→

0.1.1

), rebuild and republish under that new version, then re-add the source using that version so Airbyte treats it as a fresh definition. 3. Recreate the source with a fresh catalog/spec Since the error text mentions “invalid configuration or catalog”, also try: - Delete the failing source in the UI. - Re-add it from the newly published image/version. - Let Airbyte re-run

spec

and

discover

so the catalog it stores is consistent with the current connector code. 4. If it’s still reproducible, open an issue Because this pattern (500 +

unexpected-problem

+ connector-internal error) is already tracked for other APIs, the maintainers usually ask for: - Full connector logs around the failure. - Airbyte version, connector version, and how you’re running it (here:

abctl

local).[[Get stream API](https://github.com/airbytehq/airbyte/issues/66688)] If you can share (sanitized) snippets of the connector logs around the checksum error and confirm whether you rebuilt the image after first publishing it, I can help you narrow it down further, but based on the available sources I can’t point to a specific documented bug or config flag.