middle_proxy_nat_ip при нескольких туннелях #372
Unanswered
Guerrero3324
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Добрый день.
Подскажите как правильно указать middle_proxy_nat_ip если несколько туннелей и первый временно в отключке.
Как я понимаю при запуске пытается определить внешний ip через туннель, но только через первый туннель. И если он не отвечает, то подключается через второй, но ругается.
warning(proxy): curl https://api.ipify.org via awg0 exited with 28: curl: (28) Connection timed out after 10002 milliseconds
warning(proxy): curl https://ifconfig.me via awg0 exited with 28: curl: (28) Connection timed out after 10002 milliseconds
warning(proxy): curl https://ipv4.icanhazip.com via awg0 exited with 28: curl: (28) Connection timed out after 10002 milliseconds
warning(proxy): MiddleProxy/ad-tag is enabled but the egress public IP could not be detected; the ad-tag (and non-Premium media via ME) may not work. Set [server].middle_proxy_nat_ip to the IP Telegram sees for this server's egress (the SOCKS/tunnel exit IP when egress isn't direct).
warning(proxy): [2] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
warning(proxy): [3] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
warning(proxy): [4] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
warning(proxy): [1] middle-proxy handshake failed, reconnecting direct to [ipv4]:443
Только прописывать middle_proxy_nat_ip в ручную?
Beta Was this translation helpful? Give feedback.
All reactions