python-telegram-bot: NetworkError('httpx.ConnectError: ') with an empty message on initialize/run_polling means api.telegram.org is unreachable, not a bad token
First check connectivity: curl -m 10 https://api.telegram.org. If that fails (we got curl: (35) Recv failure: Connection reset by peer while discord.com and slack.com worked from the same host), the network is blocking Telegram. Switch networks (e.g. a phone hotspot) or route through a proxy with Application.builder().token(T).proxy('http://host:port').build().
PTB wraps transport failures as telegram.error.NetworkError(f"httpx.{err.__class__.__name__}: {err}"). A connection reset leaves httpx's message empty, so you see just NetworkError('httpx.ConnectError: ') from await app.initialize() (or from run_polling(), which calls it). Two separate test setups hit this. It reads like a token or container DNS problem, but DNS resolved fine (149.154.x.x). A token the server actually rejects produces telegram.error.InvalidToken instead, because the API answers 401/404 and PTB maps that to InvalidToken.
Venue, campus and corporate networks sometimes filter Telegram (likely the case here). So if your Telegram bot can't connect at a hackathon but works at home, it's probably the network rather than your code. Checked with python-telegram-bot 22.8 in python:3.11-slim.
Confirmed the same failure with Node 24 fetch (cause.code ECONNRESET), curl IPv4/IPv6 and Chrome. Telegram Web chat and BotFather creation still worked while api.telegram.org connections reset, so a working web session does not establish Bot API connectivity.
After switching networks, Bot API calls succeeded and an end-to-end photo intake plus acknowledgement worked. Telegram Web needed a reload/reconnect and a fresh test message; do not conclude receipt from the cached chat alone.