docker image: btfs resolve -r /btns/blabla/: could not resolve name about go-btfs HOT 12 CLOSED

Your private build works for me. :) so its definately urlcheck function

from go-btfs.

• Refer to above change, you need change yourself and rebuild since not merge yet. you can always get the latest dashboard CID from https://github.com/bittorrent/btfs-dashboard/releases
• You can also use https://dashboard-test.btfs.io as workaround, it point to same CID.
• Curious to know how about your 1.6 node when open :5001/webui, cause it also use btns solution.

from go-btfs.

i can visit 5001/webui on my 1.6 host no problem :) also through my reverse proxy.

I don't know why, but my current container with btns solutions started working.
I can now visit the webinterface.

i'm building the commit with btfs solution as we speak to test that as well.

I have however one issue (sorry ;))

When i visit the interface through the reverse proxy, it cannot reach the api.
when i visit the interface internally, i can use the interface by putting http://btfstest:5001 as api url.

i would think http://btfstest:5001 should work through the reverse proxy, but not if the dashboard is an 'app' which needs a direct network connection to the api.

in that case i would need https://btfstest.hostname.com as api url.
http://btfstest:5001 is reverse proxied as https://btfstest.hostname.com so it should be able to reach the api that way.

the webinterface however says that the URL format is wrong.

from go-btfs.

the btns issue, i guess the node need some time to connect or recognized the seed node, anyway we will use the commit next version since it more stable.

the api issue, i will do some testing about reverse proxy and https architecture. dashboard (hostui) is used to manage local node, so the setting in configuration file is 127.0.0.1 ("API": "/ip4/127.0.0.1/tcp/5001"), maybe this is the reason. just be careful cause expose api to public will also public private key and upload file feature.

the api url format issue, i will discuss with front-end engineer.

from go-btfs.

Thank you very much :)

in 1.6, the CORS settings allows for reaching the API from any source you want.
i'm also able to visit http://btfstest:5001 from 'another host', and that wouldn't work if only 127.0.0.1 would work.

api url format has a high probability i think :)

from go-btfs.

about api url format issue, you can temporary modify the check logic line 51, or use my private build directly (you can pin to your node in case my node offline).

other connection issue, i used vm + reverse proxy, seem the only factor is api ip mentioned in previous comment, no matter http/https, directly/reverse proxy, all successful when i use 0.0.0.0 (not advise), and all failed if use 127.0.01 for non-local node.

from go-btfs.

Other threads closed.. so responding to this. I have this same issue on multiple distros. The work around to get to dashboard does not solve the problem that node is not connecting.. so choice is to have daemon running and get the resolving error going to internal link, or your workaround that goes to public dashboard taht says not connecting.. then what?

from go-btfs.

There are commits that solve these issues in a future release.
Until then you can use the other dashboard.

from go-btfs.

what other dashboard? this is a vicious loop. cant resolve, so you say use other dashboard, that otherdashboard says node not connected.. How about complete that step instead of going in circles? Like to be part of this but doesnt seem ready and the writeups and feedback loops is circular presently.. cant progress past cirtan point and all enquires into it, just go in same cirlce.

from go-btfs.

I was talking about the private build of daniel-tron. (https://gateway-test.btfs.io/btfs/QmdzDohKocMhFvKKQhanVDk9gnczcXCHLKvynks4XDseKw)

That build doesn't work anymore for me either, so i guess he rebuilt it to test something else.

Just wait until 2.01 or so is released, or build it yourself with the fixes mentioned in this topic...

from go-btfs.

welcome to try the v2.0.1, "resolve btns issue" should disappeared since we are using btfs now.

from go-btfs.

what other dashboard? this is a vicious loop. cant resolve, so you say use other dashboard, that otherdashboard says node not connected.. How about complete that step instead of going in circles? Like to be part of this but doesnt seem ready and the writeups and feedback loops is circular presently.. cant progress past cirtan point and all enquires into it, just go in same cirlce.

can't connect api may have following reason.

• btfs was not started
• not set cross domain in btfs config
• the node is not local node, not in same network, like docker, you should update the ip api listening in btfs config
• the node is not local node, and the api url is http by default, the other dashboard should also start with http://, try http instead of https
  http://dashboard-test.btfs.io
  http://gateway-test.btfs.io/btfs/QmRZYABH4LisEQPQmpzHAAxacDZbsKtnysjzEuZBaug6bG

from go-btfs.