Summary
The user is facing a persistent ‘Cannot Reach Server’ error in Airbyte’s UI despite all services appearing to run smoothly. They have tried troubleshooting steps but the issue persists.
Question
Hi everyone,
I’m currently facing a persistent “Cannot reach server” error in Airbyte’s UI (already since first time installation with abctl yesterday), despite all services appearing to run smoothly. I’ve tried various troubleshooting steps, but the issue persists.
Could anyone provide insights or suggestions on how to resolve this error?
Thank you in advance for your help!
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
["cannot-reach-server", "error", "ui", "abctl", "troubleshooting"]
Anything in browser’s developer tools?
I’m mostly interested in failing requests in Network tab, but maybe there is something on Console tab.
The same error appears on different browser as well?
Do you use VPN?
https://developer.chrome.com/docs/devtools/open
https://firefox-source-docs.mozilla.org/devtools-user/
for debugging
install kind https://kind.sigs.k8s.io/docs/user/quick-start/#installation and check logs
kind export logs --name=airbyte-abctl kind-logs
in kind-logs directory you will find all the logs
can you also install some tools and send screenshot when running k9s?
Install kubectl (https://kubernetes.io/docs/tasks/tools/#kubectl) and kubectx + kubens (https://github.com/ahmetb/kubectx) and k9s (https://k9scli.io/)
then execute commands:
KUBECONFIG=~/.airbyte/abctl/abctl.kubeconfig kubectl config view --flatten > ~/.kube/config
kubectx kind-airbyte-abctl
kubens airbyte-abctl
k9s```
Important Server Logs:
Unsetting empty environment variable 'JOB_MAIN_CONTAINER_CPU_REQUEST'
Unsetting empty environment variable 'JOB_MAIN_CONTAINER_MEMORY_REQUEST'
Unsetting empty environment variable 'SECRET_PERSISTENCE'
INFO Loading mask data from '/seed/specs_secrets_mask.yaml
INFO Established active environments: [k8s, cloud, control-plane]
INFO path /flags does not exist, will return default flag values
WARN MetricClient was not recognized or not provided. Accepted values are `datadog` or `otel`.
INFO Waiting for temporal server...
WARN Waiting for namespace default to be initialized in temporal...
WARNING: [Channel<1>: (airbyte-abctl-temporal:7233)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host airbyte-abctl-temporal, cause=java.lang.RuntimeException: java.net.UnknownHostException: airbyte-abctl-temporal: Temporary failure in name resolution```
It can be a temporary issue with temporal until container is ready, so it shouldn’t be a problem
Is it local deployment http://localhost:8000/ ?
Can you provide screenshot of Cannot reach server error message?
its running on a external IP adress