ipfs/ipfs-desktop

Could not connect to the IPFS API

Open

#2430 opened on Mar 14, 2023

View on GitHub
 (11 comments) (2 reactions) (0 assignees)JavaScript (5,632 stars) (912 forks)batch import
P2good first issuehelp wantedkind/bugkind/enhancement

Description

  • 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

Contributor guide

Tech stack
javascriptelectronnodejs
Domain
desktopapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
IPFS basicsJavaScriptElectron app debugging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.