The Wayback Machine - https://web.archive.org/web/20220409155206/https://github.com/ipfs/ipfs-companion/issues/1040
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node type Embedded in chrome do not work with localhost IP and cannot use webui #1040

Open
Thaina opened this issue Jan 3, 2022 · 2 comments
Open
Labels
effort/hours good first issue help wanted kind/bug P3

Comments

@Thaina
Copy link

@Thaina Thaina commented Jan 3, 2022

Describe the bug
I try to use ipfs companion with bode type Embedded in chrome, which is experimental, but I have expected that it should still work without local ipfs node and daemon, but it seem not the case. Especially the link in welcome page which specifically try to open localhost

To Reproduce
Steps to reproduce the behavior:

  1. Install IPFS companion in chrome

  2. Change Node Type to Embedded

  3. Open the extension welcome page
    3.1 Such as at the IPFS icon in the extension
    image

  4. Click on any button below to open webui

It would be opened into something like this

  1. I could open https://webui.ipfs.io/ but then it said Could not connect to the IPFS API

Not sure this was a problem of companion itself or the webui

Expected behavior
Should the chrome companion also work as a daemon by itself? I think it should be able to detect the ipfs node of the companion and change the link of extension to be the link of the embed node, or did I was misunderstand and the embed node still require daemon anyway?

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Chrome
  • Version: 96.0.4664.110

Additional context
I am very new with IPFS and I still don't want to install ipfs things into my machine. I don't even create my node or upload anything yet. I wish I could run IPFS node and daemon directly inside chrome browser. And so I would leave my OS environment out of anything related ipfs. I would like to sorry in advance if I wrongly did any step I need to

@Thaina Thaina added the need/triage label Jan 3, 2022
@ipfs ipfs deleted a comment from welcome bot Feb 25, 2022
@lidel lidel added effort/hours kind/bug P3 and removed need/triage labels Feb 25, 2022
@lidel
Copy link
Member

@lidel lidel commented Feb 25, 2022

Thank you for reporting these broken links – these should be hidden when embedded experiment with js-ipfs is used.

If you are looking for a Chromium web browser with full IPFS node, give Brave a try: https://brave.com/brave-integrates-ipfs/

@Thaina
Copy link
Author

@Thaina Thaina commented Feb 25, 2022

@lidel Thank you for your suggestion but I just want to use chrome on daily basis, I wish full IPFS node would be working the same to every browser

Hope this could be possible soon

@lidel lidel added good first issue help wanted labels Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours good first issue help wanted kind/bug P3
2 participants