linuxserver.io Posted September 24, 2020 Share Posted September 24, 2020 (edited) Application Name: Ipfs Application Site: https://ipfs.io/ Docker Hub: https://hub.docker.com/r/linuxserver/ipfs/ Github: https://github.com/linuxserver/docker-ipfs Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, rather use the linuxserver.io forum for support. Edited September 24, 2020 by linuxserver.io Quote Link to comment
Jaska Posted September 25, 2020 Share Posted September 25, 2020 Runs but does not work. "Could not connect to the IPFS API" Using static ip for this container. Quote Link to comment
saarg Posted September 25, 2020 Share Posted September 25, 2020 (edited) 3 hours ago, Jaska said: Runs but does not work. "Could not connect to the IPFS API" Using static ip for this container. You have to read the README on github to set it up correctly. You need to set the custom api address to the same IP you gave the container. So http://192.168.1.36:5001 or whatever address you used. Edited September 25, 2020 by saarg Quote Link to comment
supertomcat Posted October 2, 2020 Share Posted October 2, 2020 (edited) On 9/25/2020 at 11:20 AM, saarg said: You have to read the README on github to set it up correctly. You need to set the custom api address to the same IP you gave the container. So http://192.168.1.36:5001 or whatever address you used. Where could I see the IP I gave the container? I am getting this error as well and not seeing how to resolve in the README. Thanks! Edit: my thought its that it would be the ip of my server:5001, when I hit submit, nothing happens Edit 2: I can see something happening when I inspect the web element, it does change when I hit submit, its just still not working. Failed to load resource: Could not connect to the server. Not sure what the it should be then Edit 3: It is the ipaddressofserver:5001, but I am getting a 403 when it is set as apposed to could not connect. Edit 4: One post suggested that this will randomly happen when the daemon is started. I ran the CORS commands it was suggesting in the docker console, then restarted the docker and it worked. Could have been either issue Edited October 2, 2020 by supertomcat Quote Link to comment
loki_racer Posted October 14, 2020 Share Posted October 14, 2020 On 10/2/2020 at 2:12 PM, supertomcat said: Edit 4: One post suggested that this will randomly happen when the daemon is started. I ran the CORS commands it was suggesting in the docker console, then restarted the docker and it worked. Could have been either issue What thread are you referencing and which CORS commands did you run? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.