callback: login: migrate to dc: context deadline exceeded

[HirbodBehnam]

Hello
When I try to run one of my bots using telegram.BotFromEnvironment on my server I get this error message: callback: login: migrate to dc: context deadline exceeded. It usually happens after a long wait.
Here is what I tried before opening this discussion:

1. Pinging all ipv4 servers in this file. They are all fine.
2. ipv6 is not enabled on my server. This means that if I try to ping one of the servers with ipv6, I get ping: connect: Network is unreachable. So I tried to completely remove all ipv6 hosts from datacenter lists and give the new list to options of the BotFromEnvironment function. But still no luck.
3. I tried to run the app from my PC using a VPN (wireguard) which is connected to my server. And strangely, this works.

My desktop OS is Windows 10 and my server is Ubuntu 20.04. Binaries are compiled with go 1.18 and I've even tried cross compiling from my desktop to my server.

Have anyone got any idea's what should I try next?
Thanks in advance

[HirbodBehnam]

I did some more digging using gost and setting up a socks5 proxy in my bot.
Here is the server connecting to a local socks5 proxy logs:

Server logs which doesn't work on

2022/05/26 10:33:16 route.go:650: socks5://127.0.0.1:10808 on 127.0.0.1:10808
2022/05/26 10:39:01 socks.go:888: [socks5] 127.0.0.1:57664 -> socks5://127.0.0.1:10808 -> 149.154.167.51:443
2022/05/26 10:39:01 socks.go:888: [socks5] 127.0.0.1:57666 -> socks5://127.0.0.1:10808 -> 149.154.167.50:443
2022/05/26 10:39:01 socks.go:940: [route] 127.0.0.1:57666 -> socks5://127.0.0.1:10808 -> 149.154.167.50:443
2022/05/26 10:39:01 socks.go:940: [route] 127.0.0.1:57664 -> socks5://127.0.0.1:10808 -> 149.154.167.51:443
2022/05/26 10:39:01 socks.go:888: [socks5] 127.0.0.1:57662 -> socks5://127.0.0.1:10808 -> [2001:67c:4e8:f002::a]:443
2022/05/26 10:39:01 socks.go:940: [route] 127.0.0.1:57662 -> socks5://127.0.0.1:10808 -> [2001:67c:4e8:f002::a]:443
2022/05/26 10:39:01 socks.go:950: [socks5] 127.0.0.1:57662 -> 127.0.0.1:10808 : dial tcp [2001:67c:4e8:f002::a]:443: connect: network is unreachable
2022/05/26 10:39:01 socks.go:975: [socks5] 127.0.0.1:57666 <-> 149.154.167.50:443
2022/05/26 10:39:01 socks.go:975: [socks5] 127.0.0.1:57664 <-> 149.154.167.51:443
2022/05/26 10:39:01 socks.go:977: [socks5] 127.0.0.1:57666 >-< 149.154.167.50:443
2022/05/26 10:39:37 socks.go:977: [socks5] 127.0.0.1:57664 >-< 149.154.167.51:443
2022/05/26 10:39:37 socks.go:888: [socks5] 127.0.0.1:57678 -> socks5://127.0.0.1:10808 -> 149.154.167.50:443
2022/05/26 10:39:37 socks.go:940: [route] 127.0.0.1:57678 -> socks5://127.0.0.1:10808 -> 149.154.167.50:443
2022/05/26 10:39:37 socks.go:888: [socks5] 127.0.0.1:57676 -> socks5://127.0.0.1:10808 -> 149.154.167.51:443
2022/05/26 10:39:37 socks.go:940: [route] 127.0.0.1:57676 -> socks5://127.0.0.1:10808 -> 149.154.167.51:443
2022/05/26 10:39:37 socks.go:888: [socks5] 127.0.0.1:57674 -> socks5://127.0.0.1:10808 -> [2001:67c:4e8:f002::a]:443
2022/05/26 10:39:37 socks.go:940: [route] 127.0.0.1:57674 -> socks5://127.0.0.1:10808 -> [2001:67c:4e8:f002::a]:443
2022/05/26 10:39:37 socks.go:950: [socks5] 127.0.0.1:57674 -> 127.0.0.1:10808 : dial tcp [2001:67c:4e8:f002::a]:443: connect: network is unreachable
2022/05/26 10:39:37 socks.go:975: [socks5] 127.0.0.1:57678 <-> 149.154.167.50:443
2022/05/26 10:39:37 socks.go:975: [socks5] 127.0.0.1:57676 <-> 149.154.167.51:443
2022/05/26 10:39:37 socks.go:977: [socks5] 127.0.0.1:57676 >-< 149.154.167.51:443
2022/05/26 10:39:53 socks.go:977: [socks5] 127.0.0.1:57678 >-< 149.154.167.50:443

And here is the connection logs from my pc:

Works fine from my pc which is connected to my server

2022/05/26 10:41:11 route.go:650: ws://:10808 on [::]:10808
2022/05/26 10:45:57 ws.go:413: [ws] x.x.x.x:2765 -> [::]:10808
2022/05/26 10:45:57 ws.go:413: [ws] x.x.x.x:2766 -> [::]:10808
2022/05/26 10:45:57 http.go:161: [http] x.x.x.x:2765 -> ws://:10808 -> 149.154.167.91:443
2022/05/26 10:45:57 http.go:251: [route] x.x.x.x:2765 -> ws://:10808 -> 149.154.167.91:443
2022/05/26 10:45:57 http.go:304: [http] x.x.x.x:2765 <-> 149.154.167.91:443
2022/05/26 10:45:57 http.go:161: [http] x.x.x.x:2766 -> ws://:10808 -> [2001:67c:4e8:f004::a]:443
2022/05/26 10:45:57 http.go:251: [route] x.x.x.x:2766 -> ws://:10808 -> [2001:67c:4e8:f004::a]:443
2022/05/26 10:45:57 http.go:272: [http] x.x.x.x:2766 -> x.x.x.x:10808 : dial tcp [2001:67c:4e8:f004::a]:443: connect: network is unreachable

It's clear that my pc is trying to connect to DC number 4 but the server is trying to connect to DC number 2 for some reasons... I'll try to force the server use DC number 4 and post the results after.

[HirbodBehnam]

So I might have fixed it using two tricks.

1. I forced the DC to be number 4 in options.
2. I disabled ipv6 using this link

For now, it looks like this works for me...