Hi there. I installed and ran the ipfs on a VPS. And I change the config so that I can use it from remote. (Such as my own device).
My config is like that:
"Addresses": {
"Swarm": [
"/ip4/0.0.0.0/tcp/4001",
"/ip6/::/tcp/4001"
],
"API": "/ip4/0.0.0.0/tcp/5001",
"Gateway": "/ip4/0.0.0.0/tcp/8080"
}
I change the 127.0.0.1 to 0.0.0.0
So that I can use command to visit the IPFS on a VPS.
But when I try to visit the webui throughserverip:5001/webui, it shows nothing...
Can you tell me how to solve it? Or maybe it's not possible to use webui from remote?
THANKS~
myqq0000
All 5 comments
Please don't open up the API port 5001 to the public -- it's a huge security risk. Use an SSH tunnel instead, e.g. ssh -L 5001:localhost:5001 user@serverip. This will give you a local port 5001 forwarded to the actual API port, but without exposing it to the public.
ghost
on 26 Aug 2017
Closing this issue. If you still have more questions, please open a thread on https://discuss.ipfs.io/. Thanks!
daviddias
on 26 Oct 2017
For the reference see
https://github.com/ipfs-shipyard/ipfs-webui/issues/594#issuecomment-417922174
myfingerhurt
on 2 Sep 2018
I have the same problem. Thing is if we change from 127.0.0.1 to something like 192.168.1.10, we're opening it just to local network, and it's not much of a security risk. I see now issue is opened about this, was this solved at all - can we access webui from some other than local machine?
trancephorm
on 20 May 2021
Stebalien
on 24 May 2021
Related issues
Miserlou
·
6Comments
haarts
·
4Comments
PayasR
·
10Comments
nbingham1
·
19Comments
jbenet
·
76Comments
Most helpful comment
Please don't open up the API port 5001 to the public -- it's a huge security risk. Use an SSH tunnel instead, e.g.
ssh -L 5001:localhost:5001 user@serverip. This will give you a local port 5001 forwarded to the actual API port, but without exposing it to the public.