search

dappnode / DAppNode

General repository of the project dappnode
GNU General Public License v3.0
585 stars 103 forks source link

ENS .eth domains: ipfs resolve -r /ipfs/: invalid path "/ipfs/": not enough path components #492

Closed vorburger closed 1 year ago

vorburger commented 2 years ago

While connected to DAppNode's VPN, when I access e.g. http://alice.eth/ in Brave (which has some sort of ENS support built-in) as well as in Firefox (which as far as I know does not?) the browser just shows:

ipfs resolve -r /ipfs/: invalid path "/ipfs/": not enough path components

I'm assuming this message comes from DAppNode, but I don't know what it means in relation to ENS .eth domains, or how to fix it.

┆Issue is synchronized with this Basecamp todo by Unito

vorburger commented 2 years ago

As far as I understand, because this affects both Firefox and Brave, this is probably a bug in dappmanager/src/ethForward/resolveDomain.ts, and not related to (my) https://github.com/dappnode/DAppNode/issues/406 IPFS tribulations, and actually has nothing directly to do with Brave's built-in IPFS and ENS support.

pablomendezroyo commented 2 years ago

@vorburger hey! thanks for the report. Will look into it a contact you back

3alpha commented 2 years ago

Hm, it seems that http://alice.eth/ doesn't have contenthash field set https://app.ens.domains/name/alice.eth/details.

3alpha commented 2 years ago

I still haven't been able to figure out what standards those websites use, since it is certainly not EIP-1577. Compliant websites work in my DAppNode, at least. See http://vitalik.eth

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

stale[bot] commented 1 year ago

This issue or pull request has been automatically been closed due to inactivity.