search

vysheng / tg

telegram-cli
GNU General Public License v2.0
6.47k stars 1.53k forks source link

Ping timeout #760

Open bidak opened 9 years ago

bidak commented 9 years ago

I want to create multiple daemon files by the following code:

../bin/telegram-cli -k tg-server.pub -c telegram.config --json -dWS /var/www/tg1.sck &
...
...

But telegram-cli shows ping timeout and not connected. There is any way to solve the problem?

LukeLR commented 9 years ago

Does it work with only one client?

On 04 Sep 2015, at 4:36 am, bidak notifications@github.com wrote:

I want to create multiple daemon files with following code:

../bin/telegram-cli -k tg-server.pub -c telegram.config --json -dWS /var/www/tg1.sck & ... ... But telegram-cli shows ping timeout and not connected. There is any way to solve the problem?

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

bidak commented 9 years ago

Yes, It works with one client. When the connection is lost, I use the following code:

sudo pkill telegram

So tg connects.

bidak commented 9 years ago

How to solve the problem?

*** public key 'tg-server.pub' loaded successfully
 *** Couldn't open public key file: /etc/telegram-cli/server.pub
 *** Can not load key /etc/telegram-cli/server.pub
 *** public key 'tg-server.pub' loaded successfully
 *** DC1 'DC' update: 149.154.175.50:443
 *** DC2 'DC' update: 149.154.167.51:443
 *** DC3 'DC' update: 149.154.175.100:443
 *** DC4 'DC' update: 149.154.167.91:443
 *** DC5 'DC' update: 91.108.56.107:443
 *** Alarm query 617856569668
 *** Alarm query 643637950820
 *** Alarm query 669421159968
 *** Alarm query 695196029844
 *** Alarm query 720987596108
 *** Alarm query 746762155544
 *** Alarm query 772541248828
 *** Alarm query 798324428992
 *** Alarm query 824107717812
 *** fail connection: reason: ping timeout
 *** Lost connection to server... 149.154.167.51:80
 *** fail connection: reason: ping timeout
 *** Lost connection to server... 149.154.175.50:80
 *** fail connection: reason: ping timeout
 *** Lost connection to server... 91.108.56.107:80
 *** fail connection: reason: ping timeout
 *** Lost connection to server... 149.154.167.91:80
 *** fail connection: reason: ping timeout
 *** Lost connection to server... 149.154.175.100:80
 *** Alarm query 849895266244
...
LukeLR commented 9 years ago

So when you're launching a single instance of tg, everything works and you can send a message to someone?

On 04 Sep 2015, at 6:09 pm, bidak notifications@github.com wrote:

How to solve this problem?

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

bidak commented 9 years ago

Yes , i'm connecting and sending message now but when i create multiple deamon and socket tg , shows fail connection.

LukeLR commented 9 years ago

Are you sure that all the instances are using different configuration directories?

On 04 Sep 2015, at 7:35 pm, bidak notifications@github.com wrote:

Yes , i'm connecting and sending message now but when i create multiple deamon tg , shows fail connection.

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

bidak commented 9 years ago

Thanks a lot.this problem has been solved. Is there any way to find out if the account is blocked? (without terminal)