<@U04S8PLJWMT> I am trying to develop a source co...
# ask-ai
a
@kapa.ai I am trying to develop a source connector for Etsy from scratch. Using self hosted version of Airbyte installed with abctl command and running under a docker container. Used declarative authentication section to define the OAuth 2.0 authentication configurations in connector builder UI. But there is no place to define the redirect url there. Also it prompts to use
<http://localhost:3000/auth_flow>
as the redirect_url in Etsy app which I did with
ngrok_url/auth_flow
When I authenticate the connector, Etsy window for login opens up but on login, instead of redirection, the page shows
A stitch has gone away!
error. Can you help on this please?
k
Airbyte’s OAuth implementation does not require you to manually define the redirect URI inside the Declarative OAuth configuration or in the Connector Builder UI; the redirect URI is generated and managed by Airbyte itself and exposed to you in the UI when you configure the connector. [[Using OAuth](https://docs.airbyte.com/platform/1.8/using-airbyte/oauth)] From the docs: - The redirect URI value used for OAuth callbacks is
{{ redirect_uri_value }}
, and **this value is set based on your deployment and handled by Airbyte**; you don’t define it in the declarative spec. [[Available variables](https://docs.airbyte.com/platform/connector-development/config-based/advanced-topics/oauth#available-template-variables)] - When you set up a new connector, Airbyte’s UI provides the redirect URI that must be registered in the third‑party app; you must copy that value exactly into the Etsy app configuration. [[Using OAuth](https://docs.airbyte.com/platform/1.8/using-airbyte/oauth)] Given that: 1. In the Connector Builder UI, you should reference
{{ redirect_uri_value }}
in your Consent URL template (for example:
...redirect_uri={{redirect_uri_value}}...
), not hardcode a URL. [[OAuth 2 in Builder](https://docs.airbyte.com/platform/next/connector-development/connector-builder-ui/authentication#oauth-2); [Available variables](https://docs.airbyte.com/platform/connector-development/config-based/advanced-topics/oauth#available-template-variables)] 2. In Etsy’s app settings, you must use the exact redirect URI shown by Airbyte’s UI when configuring OAuth (not
<http://localhost:3000/auth_flow>
or an
ngrok
variant unless Airbyte explicitly shows that as the redirect URI). [[Using OAuth](https://docs.airbyte.com/platform/1.8/using-airbyte/oauth)] The specific Etsy error text “A stitch has gone away!” is not covered in the Airbyte docs, so I can’t confirm its exact meaning, but misconfigured or mismatched redirect URIs are explicitly called out as a common OAuth failure mode in Airbyte: you must ensure the URI registered with Etsy matches the Airbyte‑provided redirect URI exactly. [[Using OAuth](https://docs.airbyte.com/platform/1.8/using-airbyte/oauth)] If you don’t see that redirect URI in the UI or still get the same error after updating Etsy with the Airbyte‑provided URI, the knowledge sources don’t provide further Etsy‑specific troubleshooting steps.
a
The redirect_url given in Airbyte is
localhost:3000/auth_flow
. Etsy won't be able to reach localhost as it requires public URL. How to fix this? Is it possible to complete OAuth 2.0 flow for Etsy API in Airbyte?