Hi Airbyte community — I’m running Airbyte v2 OSS in a fully air-gapped environment and hitting a 500 Internal Server Error on the connector documentation endpoint. In the browser console, the UI fails while loading destinations and shows connector_documentation/get errors, with repeated 500 responses �. I’m using a VPN-configured machine with Chrome on the same machine, and I’m trying to connect from there. Once the VPN is connected, there is no internet access on that machine, so Airbyte appears unable to fetch remote connector documentation/definitions �. Has anyone successfully run Airbyte v2 OSS in a true air-gapped setup and resolved this? If yes, what was the workaround — image mirroring only, config change, patching the web app/backend, or a specific version upgrade?

Airbyte v2 OSS in Air-Gapped Environments This is a known challenge with Airbyte OSS. Here's what the knowledge sources tell us: Root Cause Airbyte requires internet access to fetch connector documentation and registry definitions from remote sources (GitHub and airbyte.com). In air-gapped environments, these requests fail with 500 errors. [Air-gapped issue] What Changed in v2.1 As of Airbyte 2.1, there is an explicit improvement for this scenario: > "If GitHub is unreachable (for example, in air-gapped environments), the system falls back seamlessly to the previously bundled docs." This means upgrading to v2.1 or later should resolve the

connector_documentation/get

500 errors specifically, as the fallback to bundled docs is now built in. [v2.1 release notes] Other Known Issues & Workarounds 1. Bootloader failing to fetch remote connector registry (Helm deployments): The

CONNECTOR_REGISTRY_SEED_PROVIDER

env var defaults to

remote

. One workaround reported by users is configuring a proxy to allow access to the

<http://airbyte.com|airbyte.com>

domain, then narrowing it down by inspecting proxy logs. [Local registry issue] 2. Enterprise source stubs 500 error: If you're also seeing errors on

/api/v1/source_definitions/list_enterprise_source_stubs

, a workaround is to: ◦ Host a file with an empty JSON array (

[]

) ◦ Set the

ENTERPRISE_SOURCE_STUBS_URL

environment variable to point to that file [Enterprise stubs issue] 1. PyAirbyte offline mode: If you're using PyAirbyte, you can set the

AIRBYTE_OFFLINE_MODE

environment variable, which prevents errors when the registry is unreachable and also disables telemetry. [PyAirbyte constants] Recommended Steps 1. Upgrade to Airbyte v2.1+ — this is the most direct fix for the

connector_documentation/get

500 errors. 2. If the bootloader still fails, configure a proxy to whitelist the

<http://airbyte.com|airbyte.com>

domain. 3. Set

ENTERPRISE_SOURCE_STUBS_URL

to a locally hosted empty array if enterprise source stub fetching is also failing. The Airbyte team has been escalating the air-gapped environment issue for further investigation, so it's worth tracking [the open issue] for updates. You can also join the Airbyte Community Slack for peer support. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

What to do?