Hosting files on local node, but 404 error

[StaticDave]

Windows 11 running IPFS Desktop v2.15.0

Describe the bug
I have been adding files/folders to my local node for some testing. Everything was working fine, but when I restarted the desktop it wouldn't load anything. Now when I try to even look at files, I get a "404" error and my import button is greyed out so I can't even add new files. I've waited for extended periods to see if it took time loading, to no avail. My system says I am hosting 30GB of files and blocks but it cannot seem to access/display them. I can view the node via explore, but I get a 404 error locally. How can i force reconnect desktop to my local node so I can continue with my project?

The error log is empty, so I'm not sure what is causing this.

Any ideas?

[lidel]

@StaticDave this sounds like a bug specific to ipfs-webui presentation layer.

Are you able to see if there is an error inside of GUI ?

I think you can open Console via Ctrl+Shift+i key combo, then open Console tab:

then, clean up the console, and Open Files again and see if any new error appears.

[StaticDave]

@lidel Thanks for the reply. After I clear the console and open files I am not getting any errors.

I believe after digging around that I somehow have a different peer ID than I did. I'm not sure how that could have happened, as I am using the same user profile on windows with the same IPFS that I made my files with.

Is there a way to change my peer ID?

[Radderz81]

I have just installed the latest update of IPFS-Desktop; not sure if it's related to this same issue, but my IPFS companion can no longer connect to the IPFS gateway. It was working prior to the update.

IPFS API URL is correctly set as http://127.0.0.1:5001 within companion
IPFS-Desktop config API is set to "/ip4/127.0.0.1/tcp/5001"

However, if I visit http://127.0.0.1:5001/ within a browser, it now 404's, and the companion is offline / greyed out.

I've restarted the daemon again after the update from IPFS desktop with no luck. Could this be related to this same problem / a recent change in the update affecting this?

[lidel]

@StaticDave you can change PeerID by doing ipfs key rotate in command-line, or by removing .ipfs (IPFS_PATH) from your system. When IPFS_PATH is missing, IPFS Desktop will create a new identity the first time it starts. Also, you may have more than one node running on your machine (e.g. if you are running both Brave and IPFS Desktop). I am closing as I understand your problems are solved (most likely due to purging broken repo and starting anew).

@Radderz81 please fill separate issue in https://github.com/ipfs/ipfs-companion/ repo.

[StaticDave]

Thanks @lidel . Removing .ipfs worked and I'm back up and running

[lidel]

Cool! Hopefully ipfs-desktop will be able to provide GUI to autofix such broken repos – we track that in #2050