Installing a custom connector on a local Airbyte deployment fails with 403 Forbidden

TL;DR

An Airbyte maintainer identified this as a known bug in the local deployment path and pointed to a fix that shipped in abctl 0.28. The fix shipped in abctl 0.28, so the fix is to upgrade: install abctl 0.28 (or later) and redeploy your local instance.

Steps

1. On a local Airbyte deployment managed by abctl, clicking "Install" on a custom connector from the Settings page threw a 403 Forbidden error. The airbyte-server logs showed the request getting rejected even though the user had a valid token and the deployment was fully local. An Airbyte maintainer identified this as a known bug in the local deployment path and pointed to a fix that shipped in abctl 0.28. The user upgraded abctl, reinstalled the local deployment, and the custom connector installed without the 403. The user explicitly confirmed the upgrade fixed it.
2. This was a bug in how abctl served the connector-builder UI paths on local deployments, not a problem with your token. The fix shipped in abctl 0.28, so the fix is to upgrade: install abctl 0.28 (or later) and redeploy your local instance. After upgrading, go back to Settings and install the custom connector again. It should complete without the 403. The original reporter did this and confirmed it worked.

When to use

You are seeing this: The airbyte-server logs showed the request getting rejected even though the user had a valid token and the deployment was fully local. Use this skill when you run into "Installing a custom connector on a local Airbyte deployment fails with 403 Forbidden".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

On a local Airbyte deployment managed by abctl, clicking "Install" on a custom connector from the Settings page threw a 403 Forbidden error.

In the thread Installing a custom connector on a local Airbyte deployment fails with 403 Forbidden, the question was: On a local Airbyte deployment managed by abctl, clicking "Install" on a custom connector from the Settings page threw a 403 Forbidden error. The airbyte-server logs showed the request getting rejected even though the user had a valid token and the deployment was fully local. An Airbyte maintainer identified this as a known bug in the local deployment path and pointed to a fix that shipped in abctl 0.28. The user upgraded abctl, reinstalled the local deployment, and the custom connector installed without the 403. The user explicitly confirmed the upgrade fixed it. The verified resolution: This was a bug in how abctl served the connector-builder UI paths on local deployments, not a problem with your token. The fix shipped in abctl 0.28, so the fix is to upgrade: install abctl 0.28 (or later) and redeploy your local instance. After upgrading, go back to Settings and install the custom connector again. It should complete without the 403. The original reporter did this and confirmed it worked. Original discussion: https://vectle.com/threads/thr_Q1DHFz1f000b6bePLsUNlA