search

vysheng / tg

telegram-cli
GNU General Public License v2.0
6.45k stars 1.52k forks source link

can not start telegram cli-help please #730

Open smn200844 opened 9 years ago

smn200844 commented 9 years ago

Hi when I enter this command (telegram -k /etc/telegram/tg.pub) to run telegram cli, this message will be appear *\ Connect with 173.240.5.1:443 timeout

*\ Can not create connection to DC. Is network down?

what should I do? the result ping is "100% lost" , even in ping.eu. and all of my VPS's , should I use 173.240.5.1 certainly? it is not possible to change it? Please help me , Thanks

LukeLR commented 9 years ago

If you have a 100% ping loss, this clearly looks like your internet connection. Are you sure you are online?

On 09 Aug 2015, at 6:32 pm, smn200844 notifications@github.com wrote:

Hi when I enter this command (telegram -k /etc/telegram/tg.pub) to run telegram cli, this message will be appear *\ Connect with 173.240.5.1:443 timeout

*\ Can not create connection to DC. Is network down?

what should I do? the result ping is "100% lost" , even in ping.eu. and all of my VPS's , should I use 173.240.5.1 certainly? it is not possible to change it? Please help me , Thanks

— Reply to this email directly or view it on GitHub.

smn200844 commented 9 years ago

I am online that I can send this message.you can try it your self, ping it on www.ping.eu you will see 100% loss. and even if you check 443 port , it is closed on this server,you really have access to this server? where are you from

On 09/08/2015, Lukas Rose notifications@github.com wrote:

If you have a 100% ping loss, this clearly looks like your internet connection. Are you sure you are online?

On 09 Aug 2015, at 6:32 pm, smn200844 notifications@github.com wrote:

Hi when I enter this command (telegram -k /etc/telegram/tg.pub) to run telegram cli, this message will be appear *\ Connect with 173.240.5.1:443 timeout

*\ Can not create connection to DC. Is network down?

what should I do? the result ping is "100% lost" , even in ping.eu. and all of my VPS's , should I use 173.240.5.1 certainly? it is not possible to change it? Please help me , Thanks

— Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub: https://github.com/vysheng/tg/issues/730#issuecomment-129226051

LukeLR commented 9 years ago

Yes, I also cannot reach this ip, but AFAIK it does not even below to telegram's current data centers. Are you sure you are on the latest version of TG-cli?

On 09 Aug 2015, at 10:09 pm, smn200844 notifications@github.com wrote:

I am online that I can send this message.you can try it your self, ping it on www.ping.eu you will see 100% loss. and even if you check 443 port , it is closed on this server,you really have access to this server? where are you from

On 09/08/2015, Lukas Rose notifications@github.com wrote:

If you have a 100% ping loss, this clearly looks like your internet connection. Are you sure you are online?

On 09 Aug 2015, at 6:32 pm, smn200844 notifications@github.com wrote:

Hi when I enter this command (telegram -k /etc/telegram/tg.pub) to run telegram cli, this message will be appear *\ Connect with 173.240.5.1:443 timeout

*\ Can not create connection to DC. Is network down?

what should I do? the result ping is "100% lost" , even in ping.eu. and all of my VPS's , should I use 173.240.5.1 certainly? it is not possible to change it? Please help me , Thanks

— Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub: https://github.com/vysheng/tg/issues/730#issuecomment-129226051 — Reply to this email directly or view it on GitHub.

rocarvaj commented 8 years ago

This is definitely an issue with the TG-cli version. I was installing it using a .deb file in some random webpage and I had the same problem. I then installed it straight from the git repo and it worked.