Cannot log into Airbyte, Jupyter error "Password or token: Token authentication is enabled"

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: EC2, Amazon Linux
  • Memory / Disk: 16GB, 100GB
  • Deployment: Are you using Docker or Kubernetes deployment? no
  • Airbyte Version: What version are you using now? recent version, no idea which
  • Source name/version: what?
  • Destination name/version: what?
  • Step: The issue is happening during sync, creating the connection or a new source? No

As of this morning I cannot connect to an Airbyte instance installed on EC2 because Jupyter is suddenly demanding a “token” and a password. Neither of which as ever been installed. Jupyter isn’t even installed on this server, so the boilerplate that Jupyter provides is not helpful. I.e.:

$ jupyter notebook password
-bash: jupyter: command not found

Jupyter error
Jupyter error845×901 65.4 KB

How do I get connected to this container again?

2

I’m back in. My current theory is that I was running a Jupyter notebook locally in Pycharm (on MacOS) and something got hijacked. Shutting down that notebook and reconnecting to the instance seems to have solved the problem.

3

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team