chenhg5/cc-connect · error

telegram: connect failed: %w

Error message

telegram: connect failed: %w

What it means

runConnection wraps any failure establishing the Telegram long-poll connection (getUpdates/bot setup) into a retryLoopError tagged as initial-connect or reconnect failure depending on whether the platform has ever connected. The wrapped err carries the underlying cause.

Source

Thrown at platform/telegram/telegram.go:368

		case <-ctx.Done():
			timer.Stop()
			return
		case <-timer.C():
		}
	}
}

func (p *Platform) runConnection(ctx context.Context) error {
	factory := p.getNewBot()
	b, me, startPoll, err := factory(p.token, p.processUpdate, p.httpClient)
	if err != nil {
		cause := retryCauseInitialConnectFailure
		if p.hasEverConnected() {
			cause = retryCauseReconnectFailure
		}
		return &retryLoopError{
			cause: cause,
			err:   fmt.Errorf("telegram: connect failed: %w", err),
		}
	}
	if ctx.Err() != nil || p.isStopping() {
		return nil
	}

	gen, ok := p.publishBot(b, me)
	if !ok {
		return nil
	}

	slog.Info("telegram: connected", "bot", me.Username)
	p.emitReady(gen)

	// Start polling — blocks until ctx is cancelled or connection drops.
	startPoll(ctx)

	p.clearBot(gen, b)

View on GitHub (pinned to 4000b2338a)

Solutions

1. Ensure no other process/bot instance is polling the same token (409 Conflict)
2. Check host network connectivity and proxy settings
3. Rely on/configure the retry backoff loop; inspect the wrapped cause for the root error
4. Re-verify the token if 401s persist

if err := plat.Start(handler); err != nil {
    var rle *RetryLoopError
    if errors.As(err, &rle) {
        slog.Error("telegram connect loop ended", "cause", rle.Cause, "err", rle.Err)
    }
    return err
}

When it happens

Trigger: The polling loop's connection attempt fails — bot creation error, getMe failure, or first getUpdates error — before or after a previously successful connection (which switches the retry cause from initial to reconnect).

Common situations: Network flap while the daemon runs; Telegram returning 409 Conflict because another poller instance holds a long-poll; token revoked mid-run; DNS failure.

Understand the failure class

Background: 'Something went wrong' / 'Request failed (500)' / 'HTTP error! status: 404' — what failed HTTP requests actually mean and how to find the real cause — this error's family across 28 libraries.

Related errors

• range chunk retries exhausted
• connect permission bridge: %w
• reasonix: POST %s: %w
• range request: %w
• range chunk retries exhausted: %w

AI-assisted analysis of chenhg5/cc-connect@4000b2338a (2026-09-06). Data as JSON: /api/errors/c11de09337573e26. Report an issue: GitHub.