Error when creating source/destination or connection in Airbyte WebApp

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is facing a TypeError issue in Airbyte WebApp when trying to create a source/destination or connection. The error message indicates a ‘Failed to fetch’ error.


Question

Hey guys can someone support me sort out with Airbyte issue. Using WebApp I all time receive next issue:
{
“url”: “https://airbyte.tad-env.space/workspaces/status”,
“airbyteVersion”: “1.1.0”,
“errorType”: “TypeError”,
“errorConstructor”: “TypeError”,
“error”: {},
“stacktrace”: “TypeError: Failed to fetch\n at xI (https://airbyte.tad-env.space/assets/core-icl96mliue.js:120:10076)”,
“userAgent”: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ",
“featureFlags”: {}
}

its hapened when i try to create source/destination or connection


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["airbyte", "webapp", "error", "typeerror", "source-destination", "connection"]
2

As I can see this is common issue without solution yet: https://airbytehq.slack.com/archives/C021JANJ6TY/p1727074347888689

3

<@U035912NS77> hey could u take a look? maybe u can advice something

4

Hm, I haven’t seen this particular issue yet, but maybe you could include some details about how you’re deploying Airbyte to start.

I’m assuming abctl, but I’d also be interested how you’re routing traffic to it (e.g. if there are any proxies involved and what those look like). I’d also be interested to know how/where you’re hosting it and any other special considerations (e.g. special authentication or access controls).

5

looks as it was a cache)
previously i deployed helm locally and maybe he left some cache which raised issue

6

right know im also hosting in k8s in aws

7

Gotcha, so is it working correctly now?

8

yes, everything looks good , thanks a lot and sorry for ping