autofees: Error calling `/lnrpc.Lightning/ListChannels`

[bitromortac]

Originally posted by @dekdynamics:

I also have this problem on The Wall, as I've reported in Slack to @jbrill and @levmi

AutoFees was working fine for me, and unfortunately I cant tell exactly when it started failing. Maybe it was on litd 16, or maybe it happened after the silent update to lightning.terminal.engineering (when the Last Run stuff was added to the AutoFees UI.)

I have tried:

1. Disabling / Re-enabling AutoFees
2. Restarting litd
3. Generating a new pairing phrase
4. Many combinations of the above

Eventually, I always get back to "NotYetAssessed" and then this error:

curl -sk "https://autopilot.lightning.finance:12010/v1/autopilotserver/sessions/$(litcli autopilot list | jq -r '.sessions[] | select(.session_state == "STATE_CREATED" and (.label | contains("AutoFees"))) | .local_public_key' | xxd -r -p | base64 | tr '+/' '-_')" | jq
{
  "session_info": {
    "state": "ACTIVE",
    "created_at": "1767969653",
    "last_successful_conn_timestamp": "1767969706",
    "last_conn_attempt_timestamp": "1767969705",
    "unsuccessful_attempt_count": 0,
    "features": {
      "AutoFees": {
        "name": "AutoFees",
        "last_run_timestamp": "1767969706",
        "state": "ACTIVE",
        "status": {
          "status": "NextRunScheduled",
          "details": "Next approximate run time: 2026-01-12 14:41:00 +0000 UTC"
        },
        "updated_at": "1767969706",
        "feature_runs": {
          "feature_run_details": [
            {
              "run_at": "1767969706",
              "error_type": "CLIENT_ERROR",
              "details": "Error calling `/lnrpc.Lightning/ListChannels`"
            }
          ],
          "pagination": {
            "last_offset": "0",
            "next_offset": "1",
            "total_count": "1"
          }
        }
      }
    }
  }
}

[bitromortac]

@dekdynamics can you check these points:

• is your lit TLS certificate is still valid?
• do you have rpcmiddleware.enable=true in your lnd config
• do you have any exclusions set for your channels?

The autopilot will soon show more details why a call could not be made, we're working on that.