@model LittleShop.DTOs.BotDto @{ ViewData["Title"] = $"Re-push Configuration - {Model.Name}"; var hasExistingToken = (bool)(ViewData["HasExistingToken"] ?? false); var existingToken = ViewData["ExistingToken"] as string; }

Re-push Configuration

@Model.Name

@if (TempData["Error"] != null) { }
Push Configuration to Remote Bot

This will push the Telegram bot token to the remote TeleBot instance at @Model.RemoteAddress:@Model.RemotePort. Use this when the remote bot has been restarted and needs reconfiguration.

@if (hasExistingToken) {
Existing Token Found

A Telegram bot token is already stored for this bot.

@Html.AntiForgeryToken()

Or provide a new token:

}
@Html.AntiForgeryToken()
Get this from @@BotFather on Telegram.
Cancel
Current Remote Status
Remote Address
@Model.RemoteAddress:@Model.RemotePort
Instance ID
@(Model.RemoteInstanceId ?? "N/A")
Discovery Status
@switch (Model.DiscoveryStatus) { case "Configured": @Model.DiscoveryStatus break; case "Initialized": @Model.DiscoveryStatus break; case "Discovered": @Model.DiscoveryStatus break; case "Offline": case "Error": @Model.DiscoveryStatus break; default: @Model.DiscoveryStatus break; }
Last Discovery
@if (Model.LastDiscoveryAt.HasValue) { @Model.LastDiscoveryAt.Value.ToString("yyyy-MM-dd HH:mm:ss") } else { Never }
Instructions
  1. Ensure the remote TeleBot is running and accessible
  2. If the bot was just restarted, it may be in "Awaiting Discovery" mode
  3. Enter the Telegram bot token from @@BotFather
  4. Click "Push New Token" to configure the remote bot

When to use this:
  • After TeleBot container restart
  • When changing the Telegram bot token
  • If the remote bot lost its configuration
  • After infrastructure recovery
Quick Actions
@Html.AntiForgeryToken()
Back to Details