V0.4.11: ipfs publish creates error / WebUI not loading

Help
1

I have a script to auto-republish a couple of keys, but I’m now getting the following error when running it:

ERROR dht: loggableKey could not cast key: invalid cid version number: 47 lookup.go:35

(IPNS resolve doesn’t work.)

EDIT: When I run the publish command manually, it does say “published”, but I’m still getting the daemon error, and resolve still doesn’t work.

EDIT2: publish now working; see below

2

WebUI isn’t loading either. (Daemon is not printing any error in this case.)

3

After waiting some time, the ipns resolve now works with all keys, despite the daemon error.

WebUI still isn’t loading. Different URL/path in the new version?

4

names should automatically republish in recent ipfs

5

They definitely seem to, because I’m getting the above error from the daemon without running any republish command manually.

6

What do you mean by “webui still isn’t loading.”? Does nothing load? Is some part not working? (I’ll admit that some parts of the webui are a bit broken at the moment and could use some love).

7

Doesn’t load anything. http://localhost:5001/webui does reroute to http://localhost:5001/ipfs/QmPhnvn747LqwPYMJmQVorMaGbMSgA7mRRoyyZYz3DoZRQ/ … but it’s just a blank page.

8

Hm. Sounds like a some javascript error is preventing it from loading. Could you open a debugger console and tell me if you see any error messages?

9

There was an error already in the very first line.

09:49:00.957 DEBUG        nat: DiscoverGateway error:no NAT found nat.go:38
09:49:00.957 DEBUG       mdns: starting mdns query mdns.go:125
09:49:05.964 DEBUG       mdns: mdns query complete mdns.go:138
09:49:09.839 DEBUG bitswap_ne: bitswap net handleNewStream from <peer.ID SoLer2> ipfs_impl.go:210
09:49:09.839 DEBUG     engine: wants QmXZUBBaBDXgmMWmiRvKjT3BPMkZH2x5JFwbT4LpHJfqvY - 2147483647 engine.go:238
09:49:09.839 DEBUG     engine: peer <peer.ID SoLer2> wants QmXZUBBaBDXgmMWmiRvKjT3BPMkZH2x5JFwbT4LpHJfqvY ledger.go:80
09:49:10.679 DEBUG bitswap_ne: bitswap net handleNewStream from <peer.ID SoLer2> ipfs_impl.go:210
09:49:10.679 DEBUG     engine: <peer.ID SoLer2> cancel QmTYvrvFACjFpsjGtXiPU9c5RAuqxb9Sc3ft1mv4oAPmJg engine.go:234
09:49:10.958 DEBUG       mdns: starting mdns query mdns.go:125
09:49:13.954 DEBUG       path: Resolve: '/ipfs/QmPhnvn747LqwPYMJmQVorMaGbMSgA7mRRoyyZYz3DoZRQ/' resolver.go:54
09:49:13.954 DEBUG       path: resolve dag get resolver.go:139
09:49:13.954 DEBUG blockservi: BlockService GetBlock: 'QmPhnvn747LqwPYMJmQVorMaGbMSgA7mRRoyyZYz3DoZRQ' blockservice.go:160
09:49:13.985 DEBUG blockservi: BlockService GetBlock: 'QmPhnvn747LqwPYMJmQVorMaGbMSgA7mRRoyyZYz3DoZRQ' blockservice.go:160
09:49:16.042 DEBUG       mdns: mdns query complete mdns.go:138
09:49:20.955 DEBUG       mdns: starting mdns query mdns.go:125
09:49:20.957 DEBUG       core: <peer.ID SYCBeu> core bootstrap skipped -- connected to 4 (> 4) nodes bootstrap.go:125
09:49:21.038 DEBUG       mdns: Handling MDNS entry: 10.10.30.194:4001 <PeerID> mdns.go:147
09:49:21.048 DEBUG       mdns: got our own mdns entry, skipping mdns.go:155
09:49:25.957 DEBUG       mdns: mdns query complete mdns.go:138
09:49:30.955 DEBUG       mdns: starting mdns query mdns.go:125
09:49:30.956 DEBUG       mdns: Handling MDNS entry: 10.10.30.194:4001 <PeerID> mdns.go:147
09:49:30.956 DEBUG       mdns: got our own mdns entry, skipping mdns.go:155
09:49:35.956 DEBUG       mdns: mdns query complete mdns.go:138
10

Ah. Sorry, I was looking for javascript errors (from the browser console).