Please edit your Original Post (“OP”) above, to include:
- Brave Browser version numbers
- Operating System version numbers
Let us say, that your router’s IP address (effectively the LAN’s gateway IP address) on your Local Area Network (LAN) is:
192.168.0.1
On your computing device, MANUALLY set the computing device’s network connection DNS server number to:
192.168.0.1
Do that for:
- Ethernet connection
- Wireless connection
and, if/where you find the opportunity of adjusting the DNS setting within a software application such as Brave Browser.
Also, the following may be involved:
You might DISABLE IPFS resolution:
Implementation Details
System administrators can disable the functionality completely using an admin policy. There’s also a global setting that can be used in
brave://flags
.The go-ipfs binary is downloaded and kept up to date by Brave if a local node is enabled. It uses the same update mechanism as extensions.
Brave’s IPFS support has been designed to minimize its effect on system resources. If Brave has been configured to use a local IPFS node, that node will be lazily loaded only when the first IPFS URI is accessed. If Brave has been configured to use the public gateway, the IPFS node is never loaded.
Users can troubleshoot IPFS by navigating to an internal page:
brave://ipfs
. This also shows users the gateway, API, and swarm ports. Users can also talk to the Brave managed instance using go-ipfs command line and by specifying an argument for the--api=
parameter.