Editing an already sent root message can show the correct preview inside the editor, but after saving the message still has no preview.
@WebpageBot reports “Link previews was updated successfully”, but root preview remains broken.
I also performed controlled origin correlation. A fresh query URL was requested by:
TelegramBot (like TwitterBot)
and returned HTTP 200; the preview appeared. In the same test window, the exact root produced no matching TelegramBot/WebpageBot request at the origin.
Site-side checks passed: valid TLS, HTTP 200, server-rendered Open Graph metadata, public og:image, Telegram-like User-Agent gets the same HTML. Discord shows the correct preview for the same site.
Bot API test with LinkPreviewOptions:
A) text=/, preview URL=/ -> no preview
B) text=/?tg, preview URL=/?tg -> preview works
C) text=/, preview URL=/?tg -> preview works
Case C shows that the visible root URL itself is not the problem; failure is specific to Telegram's handling/state of the exact root preview URL.
Expected: Telegram should fetch https://kapital-rust.wtf/ and generate the same preview as /?tg.
Actual: exact root gets no preview and no new crawler request reaches the origin.
The page returns HTTP 200 and server-rendered Open Graph tags. og:image is a publicly accessible JPEG (1200x630, 56,604 bytes).
Reproduction: 1. Send either exact root URL in Telegram: only a plain link appears. 2. Submit the root URL to @WebpageBot. The bot reports success, including after "Update with content", but Telegram does not re-fetch the page. 3. Nginx access logs contain no TelegramBot request for either exact root URL. 4. Submit https://prostranstvo-vliyaniya.ru/?tg_preview=20261003. Nginx immediately logs TelegramBot fetching both the page and OG image, and Telegram displays the full preview.
Expected: the exact root URL should be fetched and display the same preview. Actual: Telegram appears to reuse a stale/negative URL-specific preview state and skips fetching the root URL.
Please clear the cached preview state for this domain/root URL and investigate why @WebpageBot reports success without triggering a re-fetch.
Update as of Oct 3, 2026: the issue is still reproducible on https://openmarketing.com.ua/. The exact root URL still does not generate a preview in Telegram. @WebpageBot reports that the preview was updated successfully, but the root URL preview is still missing. A query-string variant such as https://openmarketing.com.ua/?tg=test123 generates the preview immediately. So the issue still appears to be URL-specific caching / stale preview state for the exact root URL.
https://openmarketing.com.ua/
The exact root URL does not generate a preview:
https://openmarketing.com.ua/
→ no preview
But query-string variants work immediately:
https://openmarketing.com.ua/?tg=1
https://openmarketing.com.ua/?tg-preview-test=2
→ preview works
Server-side checks:
- HTTP/2 200
- TelegramBot can fetch the page
- valid server-rendered Open Graph tags
- public 1200x630 JPEG og:image
- robots.txt does not block TelegramBot
- @WebpageBot reports successful preview update
This appears to be the same exact-root URL preview/cache issue.
Telegram does not generate a link preview for either exact root form:
- https://prostranstvo-vliyaniya.ru/
- https://prostranstvo-vliyaniya.ru
The page returns HTTP 200 and server-rendered Open Graph tags. og:image is a publicly accessible JPEG (1200x630, 56,604 bytes).
Reproduction:
1. Send either exact root URL in Telegram: only a plain link appears.
2. Submit the root URL to @WebpageBot. The bot reports success, including after "Update with content", but Telegram does not re-fetch the page.
3. Nginx access logs contain no TelegramBot request for either exact root URL.
4. Submit https://prostranstvo-vliyaniya.ru/?tg_preview=20261003. Nginx immediately logs TelegramBot fetching both the page and OG image, and Telegram displays the full preview.
Expected: the exact root URL should be fetched and display the same preview.
Actual: Telegram appears to reuse a stale/negative URL-specific preview state and skips fetching the root URL.
Please clear the cached preview state for this domain/root URL and investigate why @WebpageBot reports success without triggering a re-fetch.
The exact root URL still does not generate a preview in Telegram.
@WebpageBot reports that the preview was updated successfully, but the root URL preview is still missing.
A query-string variant such as https://openmarketing.com.ua/?tg=test123 generates the preview immediately.
So the issue still appears to be URL-specific caching / stale preview state for the exact root URL.