Before you start

Sign-in codes, message sync and media downloads are separate checks; client proxy settings may differ.

Step by step

  1. Use https://telegram.org/faq to confirm supported platforms and official clients.
  2. Record the OS and app version and preserve existing settings before changing DNS, VPN or proxies.
  3. Compare Wi-Fi and cellular settings; desktop clients may also have terminal or app-specific proxies.
  4. Compare in-app and system proxy settings for duplication. Never forward a sign-in code to another person.
  5. Test a minimal sample and review background operation, notifications and file permissions as needed.
  6. Re-enable extensions, routing rules and synchronization one at a time after basic functionality works.

Official references

Use these provider resources for current rules. Some announcement links are help pages, not live availability tests.

Common questions

Can switching networks fix every Telegram error?

No. Account privileges, subscriptions, file permissions and service outages require separate checks.

What should I send to support?

Share the time, client version, redacted error code and minimal reproduction. Never share a password, token, cookie or one-time code.