ipfs/kubo · error

error while listing remote pins: %v

Error message

error while listing remote pins: %v

What it means

Wrapped failure from lsRemote while 'ipfs pin remote rm' was listing the pins that match its filter query; the underlying error (network, auth, or service error) is included. Nothing has been removed yet.

Source

Thrown at core/commands/pin/remotepin.go:438

		rmIDs := []string{}
		if len(req.Arguments) != 0 {
			return fmt.Errorf("unexpected argument %q", req.Arguments[0])
		}

		psCh := make(chan pinclient.PinStatusGetter)
		errCh := make(chan error, 1)
		ctx, cancel := context.WithCancel(req.Context)
		defer cancel()

		go func() {
			errCh <- lsRemote(ctx, req, c, psCh)
		}()
		for ps := range psCh {
			rmIDs = append(rmIDs, ps.GetRequestId())
		}
		if err = <-errCh; err != nil {
			return fmt.Errorf("error while listing remote pins: %v", err)
		}

		if len(rmIDs) > 1 && !req.Options[pinForceOptionName].(bool) {
			return fmt.Errorf("multiple remote pins are matching this query, add --force to confirm the bulk removal")
		}

		for _, rmID := range rmIDs {
			if err = c.DeleteByID(ctx, rmID); err != nil {
				return fmt.Errorf("removing pin identified by requestid=%q failed: %v", rmID, err)
			}
		}
		return nil
	},
}

// remote service commands

var addRemotePinServiceCmd = &cmds.Command{

View on GitHub (pinned to 329838acdf)

Solutions

  1. Retry: transient network or service-side errors are the usual cause
  2. Verify the service endpoint and credentials with 'ipfs pin remote ls --service <name>'
  3. Check the service is up and reachable from this node
Defensive patterns

Strategy: retry

When it happens

Trigger: Thrown at core/commands/pin/remotepin.go:438 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of ipfs/kubo@329838acdf (2026-09-03). Data as JSON: /api/errors/82fef83da99f05c3. Report an issue: GitHub.