Network access to API

Help Kubo
1

Hello,

I have this problem. In a nutshell, companion and desktop on other machines in my network cannot access the daemon’s API running on my NAS. I can ping the NAS, and the IPFS daemon is working fine (people are downloading my files), but I can’t get the UIs / clients to connect to the node.

When running a native node on those devices, e.g. the desktop IPFS on the laptop and PC runs its own built in node, it works fine. So it’s just the remote access to an in-LAN node that’s failing. One machine is wired into the same router connecting to the NAS, the other is on Wifi, so it’s not a subnet / wifi-extender issue either.

2

Companion has an IPFS API URL where you should provide the LAN_IP:6001 that your IPFS node runs on.

3

Yeah, no effect there.

image
image1217Ă—320 21 KB

4

No effect means there are errors? What errors? (dev console might help).

5

Never occurred to me to check the extension’s console. It’s 403s:

image

6

I think this is a CORS issue. You need to set

"Access-Control-Allow-Origin": [
        "*"
],

on your API section (not just gateway).

(It is not CORS per se, it is additional verifications that IPFS performs when it detects requests coming from browsers and which rely on allowed origins).

1 Like
7

Thank you! That worked!