Could not connect to the IPFS API

[octylFractal]

• OS Windows 11
• Version of IPFS Desktop: 0.26.1

Describe the bug
A short amount of time (~hours?) after starting IPFS Desktop, the API endpoint will disappear, resulting in "Could not connect to the IPFS API" when the Status view is opened, and local applications being unable to talk with it.

To Reproduce
Steps to reproduce the behavior:

1. Start IPFS Desktop
2. Wait an hour or so
3. Open the Status view.
4. See the error.

Expected behavior
The API remains up when IPFS Desktop is running.

Additional context
I know that the issue is not an improper URL configuration because shortly after (re)starting the IPFS daemon (not necessairly IPFS Desktop) the API works fine.

combined.log
error.log

[welcome]

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.

[whizzzkid]

Thanks for submitting this issue @octylFractal, and for attaching the log files. error.log file is empty, did that have anything meaningful there? Can you try re-attaching the file?

Under the hood, desktop is running kubo, so API being unresponsive sounds like a potential issue with kubo itself. Can you try running kubo directly and see if that has the same issue?

FWIW, I have ipfs-desktop running since last few days and have not run into this yet, maybe it's specific to win11.

[octylFractal]

The error.log is actually empty, unhelpfully. I'll try running kubo directly and report back.

[octylFractal]

kubo gives me ipfs/kubo#9693 in the output eventually, so it seems it is a kubo issue. Should I file a separate issue regarding how the error didn't show up?

[whizzzkid]

@octylFractal thanks for investigating this, eventually kubo will handle this error and ipfs-desktop should show that error. I think an enhancement for ipfs-desktop would be handle these panics and not report empty error logs, because clearly something is wrong. Would you like to take a stab at it?

CC: @SgtPooki

[github-actions]

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

[octylFractal]

Would you like to take a stab at it?

Sadly I don't have capacity for that right now.

[SgtPooki]

@octylFractal Are you still running into this issue?

[octylFractal]

No, the update to kubo that included the fix for the linked issue fixed it.

[is-this-echo]

I am also facing the same issue running ipfs-desktop 0.28.0 with kubo 0.20.0 on Windows 10.
The Status view works fine after I ran ipfs daemon after downloading Windows 10 Kubo binaries.

In my case the error logs are not empty though, sharing them here.
error.log
combined.log

[SgtPooki]

Thanks for the addition @is-this-echo, I will take a look when I can.