Issue with launching web browser after Airbyte installation

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

Summary

During the installation of Airbyte 1.0 using abctl local install --low-resource-mode, there was an issue with launching the web browser at the end. Various browser commands were not found, leading to a failure in launching the web browser. As a result, the user is unable to connect to the web server.


Question

Hello all, been using airbyte for ~1 year, tried an install of 1.0, with the new abctl local install --low-resource-mode command. all went well until toward the end and got the following:
Ingress created
▄ Attempting to launch web-browser for http://localhost:8000/usr/bin/xdg-open: line 1045: www-browser: command not found
/usr/bin/xdg-open: line 1045: links2: command not found
/usr/bin/xdg-open: line 1045: elinks: command not found
/usr/bin/xdg-open: line 1045: links: command not found
/usr/bin/xdg-open: line 1045: lynx: command not found
/usr/bin/xdg-open: line 1045: w3m: command not found
xdg-open: no method available for opening ‘http://localhost:8000’
WARNING Failed to launch web-browser.
Please launch your web-browser to access http://localhost:8000
SUCCESS Airbyte installation complete.

clearly can’t connect to the web server. I suspect something went a bit askew and cascaded from there. Any suggestions? Thanks!


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", "installation", "abctl", "web-browser", "command-not-found", "localhost"]
2

What OS environment are you running in?

3

Fedora 40 Workstation

4

I’m not familiar with that one. I guess that’s a desktop environment though? What browser do you use?

5

What does xdg-settings get default-web-browser say?

6

org.mozilla.firefox.desktop

7

just to check, you were able to open the http://localhost:8000 manually right?

8

yes, despite the warning message, I can connect. Working through the insecure cookies now.

9

Great. To be clear, what’s failing is the piece that opens your browser automatically for you, which on linux happens via a tool in the OS called xdg-open. I’m not sure why that’s failing. We don’t have a ton of control over that, since we use a https://github.com/cli/browser|library which calls out to xdg-open .

Do you still have firefox installed? Maybe you need to update your default browser with a command like xdg-settings set default-web-browser google-chrome.desktop. I got that from this https://forums.fedoraforum.org/showthread.php?331500-Fedora-39-Issue-with-Default-Web-Browser

I’m curious, what happens when you run xdg-open <https://google.com> though. Does that open your browser?