You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to access an IPFS hash at IPFS://<hash> the browser attempts to connect to locahost:48084 even though nowhere in my configuration do have port 48084 configured.
I have the IPFS Companion installed, and I run a local IPFS node on the system, so it's configured for localhost:8080
Brave is configured to use the IPFS Companion (and Method to resolve is set to Local node)
However, when I attempt to access a link for the first time using ipfs://<hash> it tries to hit localhost:48084 and after a VERY long time it eventually seems to return a 301 Moved Permanently then gets redirected to 8080 which then immediately returns another 301 Moved Permanently (this time to http://<hash>.ipfs.localhost:8080/ and the asset loads/works fine.
I don't have port 48084 configured ANYWHERE either in Brave or in my IPFS companion, so I have no idea where this port is coming from and why it's not just using 8080 configured in the companion?
The hash I'm trying to load here is/was pinned to my local node.
Steps to Reproduce
Run a local IPFS node
Enable IPFS Companion, point everything at your local node
Try to access an IPFS://<hash> directly via the address bar
See above screenshots
Actual result:
See above screenshots also:
Expected result:
IPFS://<hash> link entered into the address bar should hit my correctly configured gateway - through the IPFS companion configuration...
Reproduces how often:
I can reproduce this with my current settings, trying to load ANY hash via IPFS://<hash> in the address bar.
Brave version (brave://version info)
Version 1.28.106 Chromium: 92.0.4515.159 (Official Build) (64-bit) - Linux Mint 20.2 (Uma)
Version/Channel Information:
Can you reproduce this issue with the current release? Yes
Can you reproduce this issue with the beta channel? idk
Can you reproduce this issue with the nightly channel? idk
Other Additional Information:
Does the issue resolve itself when disabling Brave Shields? No
Does the issue resolve itself when disabling Brave Rewards? No
Is the issue reproducible on the latest version of Chrome? N/A
Miscellaneous Information:
The text was updated successfully, but these errors were encountered:
Indeed, "Local node" is IPFS node provided by Brave itself, it exposes the gateway on port 48080 – confusing when you have ipfs-desktop installed and running on 8080.
In this specific case Companion does its best to pick the right port and iirc defaults to 48080 when available (prioritizing built-in node over custom external one).
As for improving UX in Brave, we should make it clear that "Local node" means "IPFS node run and managed by Brave".
I would go with "Brave node" to be extra clear where the node lives.
Description
When trying to access an IPFS hash at
IPFS://<hash>
the browser attempts to connect tolocahost:48084
even though nowhere in my configuration do have port48084
configured.I have the IPFS Companion installed, and I run a local IPFS node on the system, so it's configured for
localhost:8080
Brave is configured to use the IPFS Companion (and Method to resolve is set to Local node)
However, when I attempt to access a link for the first time using
ipfs://<hash>
it tries to hitlocalhost:48084
and after a VERY long time it eventually seems to return a301 Moved Permanently
then gets redirected to8080
which then immediately returns another301 Moved Permanently
(this time tohttp://<hash>.ipfs.localhost:8080/
and the asset loads/works fine.I don't have port
48084
configured ANYWHERE either in Brave or in my IPFS companion, so I have no idea where this port is coming from and why it's not just using8080
configured in the companion?The hash I'm trying to load here is/was pinned to my local node.
Steps to Reproduce
IPFS://<hash>
directly via the address barActual result:
See above screenshots also:
Expected result:
IPFS://<hash>
link entered into the address bar should hit my correctly configured gateway - through the IPFS companion configuration...Reproduces how often:
I can reproduce this with my current settings, trying to load ANY hash via
IPFS://<hash>
in the address bar.Brave version (brave://version info)
Version 1.28.106 Chromium: 92.0.4515.159 (Official Build) (64-bit)
- Linux Mint 20.2 (Uma)Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: