-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
While running the Docker Image, the webui stays empty. #1807
Comments
On my MacBook the latest version 0.3.8-dev shows the same empty webpage. 0.3.7 works as expected... |
On my docker images I can reproduce this error when changing to a newer version then 0.3.5. I put it in the README: |
This sounds to me like a CORS issue. where are you accessing the webui from? from outside the docker node? (e.g. the docker host?) i think you'll need to modify CORS according to |
we could use |
I have this issue as well. In this example, my docker daemon where I run the IPFS container is a separate home server at 192.168.1.2. The workaround has two steps: First, on the docker daemon, set the API and Gateway to 0.0.0.0 like this: sudo docker exec ipfs_host ipfs config Addresses.Gateway /ip4/0.0.0.0/tcp/8080 Wait for the log to show: API server listening on /ip4/0.0.0.0/tcp/5001 This will allow you to see the webui on your workstation at http://192.168.1.2:5001/webui, but it will still be blank. Second, you need to forward your local ports to the 127.0.0.1 interface on your docker daemon with SSH: ssh -L 4001:127.0.0.1:4001 -L 5001:127.0.0.1:5001 -L 8080:127.0.0.1:8080 192.168.1.2 Once you do that, you will be able to access the webui at http://127.0.0.1:5001/webui and it will be populated with info, but it will only work as long as that SSH tunnel is open... It seems like there may be some in the webui or API somewhere that doesn't respect the setting of 0.0.0.0? FYI: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES |
Still got the same issue running the current version. :( |
Have anyone solved this problem yet ? |
We are working on brand new version in Stay tuned :) |
@lidel I know it's strange but, my ipfs docker just worked and I really don't know why. |
@lidel Emmmm, I'm not sure if it's due to some network change, yesterday I set up a local webui and it's not working, neither can I visit |
And I tried to cut of my network, still working... |
@StepOITD really hard to tell without doing a deep dive into intricacies of your local setup, however usual suspects are:
|
I believe this can be closed as the issue should solved in the latest webui: |
Thanks! |
When I start the docker image and access the webui, all content stays blank.
I build the container like this:
$ dockerbuild --rm -t ipfs .
I started it like this:
The logs read like this:
The error message is rewritten each time a reload (CTRL-R) the page.
Creating a bash within the container and fireing up the following brings this:
The text was updated successfully, but these errors were encountered: