Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

webui on nas LAN

See original GitHub issue

i installed ipfs on a nas for LAN using docker

when i try to access webui i get this

Is your IPFS daemon running?
Failed to connect to the API.

ipfs companion works tho

exactly what i need to do and get this working

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

lidelcommented, Jul 17, 2019

@icf20 thank you for raising the issue of poor UX when opening Web UI from LAN IP.

We plan to simplify the way Companion opens Web UI: https://github.com/ipfs-shipyard/ipfs-companion/issues/736 (this will make it work in LAN scenario without the need of setting CORS)

Not sure how useful it is, but some additional context:

is the default config i dint change anything

Default config assumes you are running and accessing Web UI via localhost interface. Unless you set up HTTPS, the LAN IP is not considered a Secure Context and may require additional configuration. AFAIK go-ipfs has additional code that returns HTTP 403 unless you are sending request from localhost.

i found the issue

This is not related to Web UI issues. It means that if you have HTTPS website with images loaded from IPFS paths, IPFS Companion will redirect requests for those images to your node at LAN IP. If node in LAN does not have HTTPS, browsers will produce mixed content errors. It is a limitation of the web platform (Secure contexts).

1reaction

icf20commented, Jun 7, 2019

F me!!! i found the issue

companion block this from working because not https removing the companion let me use the wengui perfectly