error setup my connection An unknown error occurred. (HTTP 413)

The HTTP 413 (Request Entity Too Large) error when setting up a connection in Airbyte typically occurs when the discovered catalog (schema) is too large to be sent back to the Airbyte API — most commonly when the source database has a very large number of tables (e.g., 10,000+). [Github Issue] What Causes It When Airbyte runs a Discover operation on your source, it collects metadata about all tables/schemas. If the resulting catalog payload is too large, the connector sidecar fails to write the result back to the API with a

413

error: >

ClientException: Client error : 413 Request Entity Too Large

> at

io.airbyte.api.client.generated.SourceApi.writeDiscoverCatalogResult

[Github Issue] Workarounds Attempted (from the issue) Users have tried the following configuration in their

values.yaml

(for Kubernetes/Helm deployments), with limited success:

global:
  env_vars:
    HTTP_IDLE_TIMEOUT: 3600s
    MICRONAUT_SERVER_MAX_REQUEST_SIZE: "104857600" # 100MB

webapp:
  ingress:
    annotations:
      nginx.ingress.kubernetes.io/proxy-send-timeout: 3600
      nginx.ingress.kubernetes.io/proxy-read-timeout: 3600
      nginx.ingress.kubernetes.io/proxy-body-size: "50m"

server:
  extraEnvs:
    - name: HTTP_IDLE_TIMEOUT
      value: 3600s
    - name: READ_TIMEOUT
      value: 3600s
    - name: WORKLOAD_API_READ_TIMEOUT_SECONDS
      value: "3600"

worker:
  env:
    - name: DISCOVER_JOB_TIMEOUT_MINUTES
      value: "60"

[Github Issue] Key Notes • The issue was reported with MSSQL source connector v4.1.26 on Airbyte 1.5.1, but a similar error has been seen with other sources (e.g., Salesforce to Snowflake). [413 nginx forum] • The root cause is the sheer number of tables (10,000–12,000+) in the source database generating a catalog payload that exceeds the server's request size limit. • Unfortunately, the GitHub issue was closed as stale without a confirmed fix, so there is no guaranteed resolution documented in the available knowledge sources. Recommendation: If you have a very large number of tables, consider whether you can limit the scope of the discovery (e.g., by filtering schemas or reducing the number of accessible tables for the Airbyte database user). If the issue persists, you may want to open a new issue on the Airbyte GitHub repository with your specific setup details. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai it is happen with sales force

For the Salesforce source specifically, the 413 error has been reported when connecting Salesforce to destinations like Snowflake or Redshift. One confirmed case showed this log in the terminal: >

client intended to send too large body: 1697412 bytes

This occurred during connection creation (POST to

/api/v1/web_backend/connections/create

). [Salesforce-Redshift forum] The same nginx-level body size limit is the root cause, just as with MSSQL. The workarounds from my previous answer (increasing

nginx.ingress.kubernetes.io/proxy-body-size

,

MICRONAUT_SERVER_MAX_REQUEST_SIZE

, etc.) would apply here as well. Additionally, for Salesforce specifically, there is a separate but related issue: the "Failed to fetch schema" error can occur if certain objects (like

Account

or

Opportunity

) cannot be processed by either the REST or BULK API. [Salesforce schema forum] This is a different root cause — it's about field types (e.g.,

base64

or

complexvalue

columns) that are unsupported by the BULK API. In that case, the Salesforce connector falls back to REST API, and if neither works, it throws an exception. [Salesforce docs] To summarize for Salesforce: • If the 413 is happening at connection creation, it's likely the catalog payload is too large — apply the server/nginx size limit increases. • If you're seeing a "Failed to fetch schema" error, it may be related to unsupported field types on specific Salesforce objects. You can try enabling the

Force Use Bulk API

option in the connector settings, which will ignore unsupported properties and sync via BULK API. Could you share more details about your deployment type (Docker, Kubernetes,

abctl

) and the exact error message you're seeing? That would help narrow down the specific fix. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.