https://linen.dev logo
Join Slack
Powered by
Hi, does anyone know why I got the "non-json respo...
# help-connector-development
w
Hi, does anyone know why I got the "non-json response" when I tried to create a custom connector in the Airbyte UI? I created the same connector in localhost and tested the endpoint in Postman, both of them are working fine.
k
A message from kapa.ai
The "non-json response" error can occur due to various reasons, such as incorrect configuration, connectivity issues, or outdated Airbyte versions. To troubleshoot this issue, you can follow these steps: 1. Make sure your Airbyte instance and connector are up-to-date. Update them if necessary. 2. Check the server logs for more information on the error. You can do this by running 
docker logs airbyte-server
if you're using Docker. 3. Ensure that you have added the custom connector in the Airbyte UI correctly. You need to provide the display name, Docker repository name (repository + image name), tag, and documentation URL for the connector. If the connector is local, you don't need to specify a repository because the connector is saved in your local. Use the image and version you built locally (e.g., 
airbyte/custom-connector:dev
) [source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1674677116471079). 4. If you still encounter the issue, it might be helpful to check the network tab in your browser's developer mode to inspect the API request/response for more details. If you need further assistance, please provide more information, such as your Airbyte version, connector version, and any relevant logs or error messages.
j
With Airbyte UI do you mean on cloud or a local OSS instance of Airbyte?
w
I mean the local OSS instance of Airbyte.
j
What version of Airbyte are you running? Also, are you using basic auth?
w
How to check the version?
For the auth, yes.
j
You can find it in the bottom left of the UI
w
0.44.2
j
I just tested with the most recent 0.44.3 and it worked fine to me - could you try upgrading and check whether the problem persists?
w
Do you know how to upgrade it?
j
You do that by doing a 
git pull
, then stopping and starting the airbyte services
w
I did that, and it said everything up to date.
j
could you check what the 
VERSION
is in 
./run-ab-platform.sh
(3rd line)?
w
It is 0.44.2
j
Could you run ./run-ab-platform.sh and check whether it's updated now in the UI?
w
In the UI, it is 0.44.2
the same as the one in the ./run-ab-platform.sh
j
above you said 0.44.3 😄
OK, somehow the git pull didn't work
it is 
0.44.3
there
did you fork the airbyte repo or something like this?
In this case you need to update your master branch
w
Sorry about that... I edited it.
Yes, I forked the repo.
j
then you need to pull from the upstream repo or edit it manually
w
Just want to clarify: when I created the custom connector in the UI (localhost), it works. But when I tried to create the actual connector, it does not work. Does it because of the version?
j
I don't understand what you mean by "actual" connector?
w
The one on the cloud I think.
j
And by "not work" do you mean it shows "Non-json response" in the connector builder testing panel right?
w
Yes it shows "Non-json response"
j
OK, I think we need to take a step back here - I'm not sure I can follow what your problem is
What steps are you taking exactly, what are you seeing and what are you expecting to see
Preferably with screenshots
w
I first fork the repo and then clone it, then I implemented some classes using the template. And I run docker compose up to create the connector in the UI, and it was able to get the data I need. Then I run docker build. After that, I setup the custom connector package in docker, then run docker tag and docker push The third step was to create the connector in Airbyte Cloud and then I got the error.
j
The third step was to create the connector in Airbyte Cloud and then I got the error
Can you explain the steps you took to do this? Can you show a screenshot of the error?
w
Sure.
IMG_1044.PNG
I just clicked: Settings -> Sources -> + New connector. Then enter all of the fields except the connector documentation URL.
j
oh I see, we had a misunderstanding here. So this screenshot is from cloud.airbyte.com?
w
Yes.
So sorry for the misunderstanding.
j
Are you sure the image works correctly?
If you run 
docker run --rm -i <source-image-name> spec
, does it give you the expected output?
w
yes
It shows me the schema data
wait
it shows me the old version of the schema data which is not exactly the same as the one I have now.
Open in Slack
PreviousNext
Powered by