Repository navigation
Remote operations on Telegram are not possible #964
Description
Activity
fixed after i chat with command code spark 1.3
⠶ Yes, I just tested it and confirmed this is the reason:
- I checked cli.mjs, and the Telegram client uses bare fetch, without a ProxyAgent, and by default does not read proxy variables
- Node 26's fetch ignores by default HTTP_PROXY: I set up a fake proxy 127.0.0.1:9, it still returns 200; only after adding NODE_USE_ENV_PROXY=1 does it report
ECONNREFUSED (Finally Left the Agent) - curl automatically reads the proxy, so curl does not mean Node is connected; TUN is a virtual network card layer that transparently forwards, and applications are undetectable, so only TUN can save it
- Node 26's fetch ignores by default HTTP_PROXY: I set up a fake proxy 127.0.0.1:9, it still returns 200; only after adding NODE_USE_ENV_PROXY=1 does it report
If you don't want to open TUN, just start it like this:
$env:NODE_USE_ENV_PROXY=1; $env:HTTP_PROXY="http://127.0.0.1:10808"; $env:HTTPS_PROXY="http://127.0.0.1:10808"
- I checked cli.mjs, and the Telegram client uses bare fetch, without a ProxyAgent, and by default does not read proxy variables
Rotate the creds you posted above please.
@bas3line Please check.
Summary
1 : command code return:
⠶ Hi! What can I help you with?
◼ Remote: Telegram unreachable: fetch failed. retrying
◼ Remote: send failed: fetch failed
◼ Remote: send failed: fetch failed
◼ Remote: send failed: fetch failed
2: auth.json
3: no return in telegram bot after /start
Expected Behavior
return in telegram bot after /start and send any message
Actual Behavior
no return in telegram bot after /start and send any message
Steps to reproduce the issue
Follow the /rc prompt to follow the steps
Command Code Version
1.73.2
Operating System
Windows
Terminal/IDE
Unknown
Shell
cmd.exe
Session file (optional)
No response
Fix prompt (optional)
No response
Additional context
No response