Could not connect to the IPFS API · ipfs/ipfs-desktop#2430

2023-03-14T06:40:09.000Z

- 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](https://github.com/ipfs/ipfs-desktop/files/10964833/combined.log) [error.log](https://github.com/ipfs/ipfs-desktop/files/10964834/error.log)

(11 留言) (2 反應) (0 負責人)JavaScript (5,632 star) (912 fork)batch import

P2good first issuehelp wantedkind/bugkind/enhancement

描述

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:

Start IPFS Desktop
Wait an hour or so
Open the Status view.
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

貢獻者指南

技術棧: javascriptelectronnodejs
領域: desktopapi
議題類型: bug
難度: 3
預計時間: 1-2 days
活動狀態: stale
清晰度: clear
前置要求: IPFS basicsJavaScriptElectron app debugging
新手友善度: 50
研究方向: Examine the attached combined.log and error.log files to identify when the API becomes unreachable. Check if the IPFS daemon process crashes or if the API port changes. Look for patterns in log timestamps related to system sleep or network changes on Windows. Consider reproducing the issue by running IPFS Desktop for several hours and monitoring API availability. Also review the system tray behavior and any Windows power saving settings that might affect the daemon.