I am attempting to upload a custom destination con...
# replication-troubleshooting
s
I am attempting to upload a custom destination connector to a cluster on which I am hosting an AirByte open source instance. The upload appears to happen, and I see the
spec
Docker image be invoked and apparently finish successfully. Running
spec
locally from a Docker image works. After a bit of time, I am automatically redirected to the Account tab and my new destination connector is nowhere to be found. I’m running AirByte 0.40.25.
I’m just looking for some pointers on what I might do to troubleshoot this.
Disregard. I am running AirByte on Linode; I just recycled the Linodes in the cluster, and now all seems to be well.
Spoke too soon. I’m still getting that puzzling redirect, and my destination connector is still nowhere to be found.
Well…I uploaded the new destination definition through the API, and that seemed to work. So I’m back on track, but the UI thing confused me.
n
Hi Sean. Our team is currently understaffed and we do not have the capacity to support custom connector development. If the issue persists, I hope the community chimes in with support!
s
It’s not a problem. My question was more about why the UI apparently successfully uploaded it but I wasn’t seeing it in the UI. I am sorry to hear that you are understaffed!
n
Were you following the docs on how to add it to the UI?
s
Yes, and it’s not the first time I’ve done this. Though I will double-check the docs on this matter.
n
I see! Could you please update to the latest version of Airbyte and try once more? If that doesn't work, we'll proceed to raise an issue on GitHub!
u
Gotcha!