To parse non base32, base36 or base58btc encoded CID multibase decoder must be provided

[metal3d]

Checklist

• This is a bug report, not a question. Ask questions on discuss.ipfs.tech.
• I have searched on the issue tracker for my bug.
• I am running the latest kubo version or have an issue updating.

Installation method

dist.ipfs.tech or ipfs-update

Version

Tried with 0.32.1 and 0.33.0-rc1

Config

{
  "API": {
    "HTTPHeaders": {}
  },
  "Addresses": {
    "API": "/ip4/127.0.0.1/tcp/5001",
    "Announce": [],
    "AppendAnnounce": [],
    "Gateway": "/ip4/127.0.0.1/tcp/8080",
    "NoAnnounce": [],
    "Swarm": [
      "/ip4/0.0.0.0/tcp/4001",
      "/ip6/::/tcp/4001",
      "/ip4/0.0.0.0/udp/4001/webrtc-direct",
      "/ip4/0.0.0.0/udp/4001/quic-v1",
      "/ip4/0.0.0.0/udp/4001/quic-v1/webtransport",
      "/ip6/::/udp/4001/webrtc-direct",
      "/ip6/::/udp/4001/quic-v1",
      "/ip6/::/udp/4001/quic-v1/webtransport"
    ]
  },
  "AutoNAT": {},
  "AutoTLS": {},
  "Bootstrap": [
    "/dnsaddr/bootstrap.libp2p.io/p2p/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb",
    "/dnsaddr/bootstrap.libp2p.io/p2p/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt",
    "/ip4/104.131.131.82/tcp/4001/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ",
    "/ip4/104.131.131.82/udp/4001/quic-v1/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ",
    "/dnsaddr/bootstrap.libp2p.io/p2p/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN",
    "/dnsaddr/bootstrap.libp2p.io/p2p/QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa"
  ],
  "DNS": {
    "Resolvers": {}
  },
  "Datastore": {
    "BloomFilterSize": 0,
    "GCPeriod": "1h",
    "HashOnRead": false,
    "Spec": {
      "mounts": [
        {
          "child": {
            "path": "blocks",
            "shardFunc": "/repo/flatfs/shard/v1/next-to-last/2",
            "sync": true,
            "type": "flatfs"
          },
          "mountpoint": "/blocks",
          "prefix": "flatfs.datastore",
          "type": "measure"
        },
        {
          "child": {
            "compression": "none",
            "path": "datastore",
            "type": "levelds"
          },
          "mountpoint": "/",
          "prefix": "leveldb.datastore",
          "type": "measure"
        }
      ],
      "type": "mount"
    },
    "StorageGCWatermark": 90,
    "StorageMax": "10GB"
  },
  "Discovery": {
    "MDNS": {
      "Enabled": true
    }
  },
  "Experimental": {
    "FilestoreEnabled": false,
    "Libp2pStreamMounting": false,
    "OptimisticProvide": false,
    "OptimisticProvideJobsPoolSize": 0,
    "P2pHttpProxy": false,
    "StrategicProviding": false,
    "UrlstoreEnabled": false
  },
  "Gateway": {
    "DeserializedResponses": null,
    "DisableHTMLErrors": null,
    "ExposeRoutingAPI": null,
    "HTTPHeaders": {},
    "NoDNSLink": false,
    "NoFetch": false,
    "PublicGateways": null,
    "RootRedirect": ""
  },
  "Identity": {
    "PeerID": "12D3KooWL61aoEwSgvGnCNZHDBVjB9q88ptJXs4LVgR7NsDBE8xt"
  },
  "Import": {
    "CidVersion": null,
    "HashFunction": null,
    "UnixFSChunker": null,
    "UnixFSRawLeaves": null
  },
  "Internal": {},
  "Ipns": {
    "RecordLifetime": "",
    "RepublishPeriod": "",
    "ResolveCacheSize": 128
  },
  "Migration": {
    "DownloadSources": [],
    "Keep": ""
  },
  "Mounts": {
    "FuseAllowOther": false,
    "IPFS": "/ipfs",
    "IPNS": "/ipns"
  },
  "Peering": {
    "Peers": null
  },
  "Pinning": {
    "RemoteServices": {}
  },
  "Plugins": {
    "Plugins": null
  },
  "Provider": {
    "Strategy": ""
  },
  "Pubsub": {
    "DisableSigning": false,
    "Router": ""
  },
  "Reprovider": {},
  "Routing": {
    "Methods": null,
    "Routers": null
  },
  "Swarm": {
    "AddrFilters": null,
    "ConnMgr": {},
    "DisableBandwidthMetrics": false,
    "DisableNatPortMap": false,
    "RelayClient": {},
    "RelayService": {},
    "ResourceMgr": {},
    "Transports": {
      "Multiplexers": {},
      "Network": {},
      "Security": {}
    }
  },
  "Version": {}
}

Description

Until a few days ago, no problem to use IPFS. Then suddenly, today, this error appears when I try to "inspect" a file:

The files are all accessible on others nodes, I can use ipfs get and all stats command seems to be OK.

I tried to move ~/.ipfs and then ipfs init; ipfs daemon (with --debug there are too much of details, impossible to identify something when I try to access "inspect" view)

The error is present too.

[metal3d]

Note: this is only with MY files, not those I visit from, for example, hello world examples.

I have got a backup from 3 days ago, when it worked. The problem is still present.
The problem is still present.

[metal3d]

Oh, wait...
What's going on?

Actually, when I press the "inspect" button from the menu on the right, from the "file" view, it fails.
If I copy the CID inside the top input, and press "Seach", the problem is the same. It's exactly the same as pressing "inspect" in the right menu.

But !

If I paste the CID in the text input on top and press "inspect" (on top), it works...

In the browser console:

Failed to resolve path ipfs/QmXhTXbRhTMFN61AcZC3xbvbeKpkCxLvc41N6nuBcG75eK Error: To parse non base32, base36 or base58btc encoded CID multibase decoder must be provided
    <anonymous> cid.js:334
    parse cid.js:300
    Se explore.tsx:58
    xe explore.tsx:129
    xe explore.tsx:115
    React 2
    unstable_runWithPriority scheduler.production.min.js:19
    React 3
    U scheduler.production.min.js:17
    onmessage scheduler.production.min.js:14
    7234 scheduler.production.min.js:13
    Webpack 10
[explore.tsx:142:16](http://127.0.0.1:5001/ipfs/bafybeibgic2ex3fvzkinhy6k6aqyv3zy2o7bkbsmrzvzka24xetv7eeadm/static/node_modules/ipld-explorer-components/src/providers/explore.tsx)

It's like the button changed behavior...

Note: I tested on several browsers like Brave, and Firefox.

​

[metal3d]

It seems that the "inspect" button badly adds "/ipfs" prefix:

Capture.video.du.2024-12-22.15-12-52.mp4

[hsanjuan]

Maybe this an issue for https://github.com/ipfs/ipfs-webui/

[gammazero]

@metal3d Can you please try this in the latest Kubo-RC. There should be fix for this as it is a known issue:
ipfs/ipfs-webui#2306