Ipfs-webui: Upgraded to repo version 10 and lost webui

[TitaniumCoder477]

I upgraded to repo version 10 but lost the ability to reach the webui page.

Steps to reproduce the behavior:

1. Upgrade from 9 to 10 using: fs-repo-migrations -to 10
2. Upgrade go-ipfs to 0.7.0
3. Start the ipfs daemon
4. Attempt to browse: http://192.168.1.43:5001/webui
5. Get redirected to http://192.168.1.43:5001/ipfs/bafybeianwe4vy7sprht5sm3hshvxjeqhwcmvbzq73u55sdhqngmohkjgs4/ with an error: ipfs cat /ipfs/bafybeianwe4vy7sprht5sm3hshvxjeqhwcmvbzq73u55sdhqngmohkjgs4/: merkledag: not found

I expect to see the IPFS Web UI.

Figure 1: My service details w/ version info; systemctl status ipfs:

● ipfs.service - IPFS Daemon
Loaded: loaded (/lib/systemd/system/ipfs.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-01-05 20:43:33 EST; 1s ago
Main PID: 1222 (ipfs)
Tasks: 8 (limit: 2358)
Memory: 45.2M
CGroup: /system.slice/ipfs.service
└─1222 /usr/local/bin/ipfs --config=/media/data/.ipfs daemon

Jan 05 20:43:33 WIL-IPFS-SRV systemd[1]: Started IPFS Daemon.
Jan 05 20:43:33 WIL-IPFS-SRV ipfs[1222]: Initializing daemon...
Jan 05 20:43:33 WIL-IPFS-SRV ipfs[1222]: go-ipfs version: 0.7.0
Jan 05 20:43:33 WIL-IPFS-SRV ipfs[1222]: Repo version: 10
Jan 05 20:43:33 WIL-IPFS-SRV ipfs[1222]: System version: amd64/linux
Jan 05 20:43:33 WIL-IPFS-SRV ipfs[1222]: Golang version: go1.14.4

Figure 2: ipfs responds fine; ipfs files ls gives me:

ipfs-companion-imports
nextcloud
screenshots

Figure 3: However, can't get the webui to pull up

Using Chrome and Firefox on multiple computers and in incognito produces same result. I also cleared all cookies and cache and even F12 > right-click reload > Empty Cache and Hard Reload.

FYI, I permit API access on my LAN only. This was all working prior to the upgrade as recently as this past weekend when I was using the web UI.

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[jessicaschilling]

Thanks for this detailed info - we will look more closely in the next scheduled triage session. You may also want to check in with the forums at discuss.ipfs.io to see if folks in the wider community might have guidance as well.

[TitaniumCoder477]

Thank you @jessicaschilling. After work this evening, I was contemplating how to spend the evening and the random thought popped into my head that I should check the webui again. I completely expected it to be exactly, precisely, the same as last night since I had literally not touched it since creating the issue here. But to my complete surprise, the webui appeared like a genie from a lamp and smiled coyly as if to imply I should question my sanity before documenting such an outrageous claim.

Dramatic personifications aside, I have no earthly idea why it is working now. The server has been up 22 hours and 8 minutes since I gave it my last try, documented the issue here, and lived to fight another day. I'm totally feeling happy, mystified, and suspicious at the moment. :)

[jessicaschilling]

😊
Will chalk up to gremlins, but it's still on our triage list. Leaving this issue open for now.

[lidel]

@TitaniumCoder477 go-ipfs v0.7.0 uses a new version of webui, that was not present in your repo.

The error:

merkledag: not found

(i know, its not very good error) suggests that your node was offline, so it could not find the new webui in local repo nor it was able to fetch it.

Between that error and now you most likely started your node (ipfs daemon) and when you opened webui it was fetched and cached (so in the future its fetched from local repo).

I'm closing as your issue is solved, but we should take a mental note that merkledag: not found wastes a lot of our colelctive time and text should be improved – let's continue in https://github.com/ipfs/go-ipfs/issues/2009