Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Issue Report: Telegram restart Command Authorization Failure [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#71536•Fetched 2026-04-26 05:11:44
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
royhk920royhk920
Participants
royhk920royhk920
Timeline (top)
labeled ×2

The Telegram restart command continues to fail with the message:

You are not authorized to use this command.

This happens even after updating Telegram-related allowlists and owner-related configuration. The behavior indicates that the command is still being blocked somewhere in the authorization or execution path.

Observed configuration changes included:

Telegram sender allowlisting Owner allowlisting Telegram command owner enforcement adjustments Gateway restart after config changes

Despite these updates, the command remains rejected.

The failure appears to involve one or more of the following:

command authorization owner identity matching exec approval gating Telegram command route handling stale runtime state after configuration reload

The issue is reproducible on Telegram and is specific to the restart command.

Root Cause

The Telegram restart command continues to fail with the message:

You are not authorized to use this command.

This happens even after updating Telegram-related allowlists and owner-related configuration. The behavior indicates that the command is still being blocked somewhere in the authorization or execution path.

Observed configuration changes included:

Telegram sender allowlisting Owner allowlisting Telegram command owner enforcement adjustments Gateway restart after config changes

Despite these updates, the command remains rejected.

The failure appears to involve one or more of the following:

command authorization owner identity matching exec approval gating Telegram command route handling stale runtime state after configuration reload

The issue is reproducible on Telegram and is specific to the restart command.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The Telegram restart command continues to fail with the message:

You are not authorized to use this command.

This happens even after updating Telegram-related allowlists and owner-related configuration. The behavior indicates that the command is still being blocked somewhere in the authorization or execution path.

Observed configuration changes included:

Telegram sender allowlisting Owner allowlisting Telegram command owner enforcement adjustments Gateway restart after config changes

Despite these updates, the command remains rejected.

The failure appears to involve one or more of the following:

command authorization owner identity matching exec approval gating Telegram command route handling stale runtime state after configuration reload

The issue is reproducible on Telegram and is specific to the restart command.

Steps to reproduce

The Telegram restart command continues to fail with the message:

You are not authorized to use this command.

This happens even after updating Telegram-related allowlists and owner-related configuration. The behavior indicates that the command is still being blocked somewhere in the authorization or execution path.

Observed configuration changes included:

Telegram sender allowlisting Owner allowlisting Telegram command owner enforcement adjustments Gateway restart after config changes

Despite these updates, the command remains rejected.

The failure appears to involve one or more of the following:

command authorization owner identity matching exec approval gating Telegram command route handling stale runtime state after configuration reload

The issue is reproducible on Telegram and is specific to the restart command.

Expected behavior

The Telegram restart command continues to fail with the message:

You are not authorized to use this command.

This happens even after updating Telegram-related allowlists and owner-related configuration. The behavior indicates that the command is still being blocked somewhere in the authorization or execution path.

Observed configuration changes included:

Telegram sender allowlisting Owner allowlisting Telegram command owner enforcement adjustments Gateway restart after config changes

Despite these updates, the command remains rejected.

The failure appears to involve one or more of the following:

command authorization owner identity matching exec approval gating Telegram command route handling stale runtime state after configuration reload

The issue is reproducible on Telegram and is specific to the restart command.

Actual behavior

The Telegram restart command continues to fail with the message:

You are not authorized to use this command.

This happens even after updating Telegram-related allowlists and owner-related configuration. The behavior indicates that the command is still being blocked somewhere in the authorization or execution path.

Observed configuration changes included:

Telegram sender allowlisting Owner allowlisting Telegram command owner enforcement adjustments Gateway restart after config changes

Despite these updates, the command remains rejected.

The failure appears to involve one or more of the following:

command authorization owner identity matching exec approval gating Telegram command route handling stale runtime state after configuration reload

The issue is reproducible on Telegram and is specific to the restart command.

OpenClaw version

2026.4.23

Operating system

ubuntu 24

Install method

npm global

Model

gpt-5.5 / 5.4

Provider / routing chain

openclaw > telegram

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The Telegram restart command authorization issue may be resolved by re-examining and adjusting the command authorization, owner identity matching, or exec approval gating configurations.

Guidance

  • Review the command authorization settings to ensure the Telegram sender is properly allowlisted and configured.
  • Verify that the owner identity matching is correctly set up, as this could be causing the authorization failure.
  • Check the exec approval gating configuration to see if it's blocking the restart command.
  • Consider checking for stale runtime state after configuration reload, which might require a more thorough restart or cache clearance.

Example

No specific code example can be provided without more details on the configuration files or codebase, but reviewing the authorization and configuration settings as mentioned should be the first step.

Notes

The issue seems to be related to the authorization or execution path of the Telegram restart command. Given the lack of specific logs or error messages beyond "You are not authorized to use this command," focusing on the configurations and settings related to authorization and command execution is the most direct approach.

Recommendation

Apply workaround: Re-evaluate and adjust the authorization and configuration settings related to the Telegram restart command, as the issue seems to stem from these areas.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The Telegram restart command continues to fail with the message:

You are not authorized to use this command.

This happens even after updating Telegram-related allowlists and owner-related configuration. The behavior indicates that the command is still being blocked somewhere in the authorization or execution path.

Observed configuration changes included:

Telegram sender allowlisting Owner allowlisting Telegram command owner enforcement adjustments Gateway restart after config changes

Despite these updates, the command remains rejected.

The failure appears to involve one or more of the following:

command authorization owner identity matching exec approval gating Telegram command route handling stale runtime state after configuration reload

The issue is reproducible on Telegram and is specific to the restart command.

#vector store#embedding generation#cache error#pipeline error#runtime error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING