What causes "update_quota_loop timeout fail." in XX-net/XX-Net?

Check earlier log lines for the underlying request_balance failure reason and address it (credentials, network).

update_quota_loop timeout fail.

Error message

update_quota_loop timeout fail.

What it means

Emitted when the background update_quota_loop in x_tunnel finishes its polling attempts without seeing quota increase by more than 1GB (the loop exits after its retry budget, sleeping 60s between checks, and logs this warning). It means the quota refresh after (re)login never converged.

Source

Thrown at code/default/x_tunnel/local/proxy_session.py:1400

    start_time = time.time()
    last_quota = g.quota
    while g.running and time.time() - start_time < 10 * 60:
        if not g.config.login_account:
            xlog.info("update_quota_loop but logout.")
            return

        request_balance(
            g.config.login_account, g.config.login_password,
            is_register=False, update_server=False)

        if g.quota - last_quota > 1024 * 1024 * 1024:
            xlog.info("update_quota_loop quota updated")
            return

        time.sleep(60)

    xlog.warn("update_quota_loop timeout fail.")

View on GitHub (pinned to cfa5bc17b6)

Solutions

Check earlier log lines for the underlying request_balance failure reason and address it (credentials, network).
Manually trigger a balance refresh or restart the client to relaunch update_quota_loop.
Verify the account actually has quota being granted (dashboard); if quota is exhausted, renew (see the 'no quota' warning).
If API endpoints changed, upgrade XX-Net to the latest version.

Defensive patterns

Strategy: retry

Prevention

Treat this warning as a symptom: inspect preceding request_balance errors in the log.
Restart the client to relaunch update_quota_loop after fixing root cause.
Keep credentials and endpoints current; upgrade XX-Net when API changes ship.

When it happens

Trigger: update_quota_loop runs after login and repeatedly calls the balance API; if every iteration fails or the quota delta stays under 1024*1024*1024 bytes until the loop's attempt limit is reached, this warning is logged. Typical when the balance API keeps failing or the account quota is genuinely static/exhausted.

Common situations: Server outages or blocked API endpoints right after login, accounts whose quota never changes (already exhausted or wrong account), or clock/rate-limit issues causing repeated API failures.

Understand the failure class

Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

Related errors

AI-assisted analysis of XX-net/XX-Net@cfa5bc17b6 (2026-08-27). Data as JSON: /api/errors/d14b15b5dd9bb7c0. Report an issue: GitHub.