Unable to connect (behind proxy)

[thexile]

Since version 0.4.16, Telegram is unable to login (behind proxy):

Error log excerpt:
...
[2014.06.02 17:31:39] Message Info: bad message notification received (error_code 17) for msg_id = 6020262313430099340, seq_no = 8
[2014.06.02 17:31:40] Message Info: bad message notification received (error_code 17) for msg_id = 6020262315790898108, seq_no = 8
[2014.06.02 17:31:40] Message Info: bad message notification received (error_code 17) for msg_id = 6020262318205823784, seq_no = 8
[2014.06.02 17:31:41] Message Info: bad message notification received (error_code 17) for msg_id = 6020262320518280908, seq_no = 8
...

[libora]

Version 0.5.1 is able to conect behind proxy. But for me is better if Telegram use settings of proxy from system, because we changed login information every 90 days and now I will must change Telegram settings manually

[telegramdesktop]

I can see sometimes this cyclic error_code=17 errors, so I hope I will be able to fix it in the future.

[auchri]

Telegram says it is connected behind a proxy but shows no contacts or conversations

[libora]

I have no problem behind proxy. Telegram works perfectly.
Dne 6. 6. 2014 7:56 "auchri" notifications@github.com napsal(a):

Telegram says it is connected behind a proxy but shows no contacts or
conversations
[image: unbenannt]
https://cloud.githubusercontent.com/assets/5092164/3197037/06cdd116-ed3f-11e3-8359-85f7e168667e.PNG
[image: set]
https://cloud.githubusercontent.com/assets/5092164/3197045/33dcd486-ed3f-11e3-8f32-0ee7780a7349.PNG

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

[thexile]

I concur with anchri. If Telegram managed to connect, there is neither conversations nor contacts being displayed. The log will still generate cyclic error code 17.

[telegramdesktop]

Perhaps 0.5.2 works better with this error_code 17. Tell me, if the cyclic error will still be there.

[thexile]

thank you. Telegram desktop is now working perfectly.

[auchri]

It works, but sometimes it needs long to detect the proxy connection and sometimes I must restart telegram, until it detects the connection.

Where can I see the log?

[telegramdesktop]

There is a command line option "-debug", that will force debug logs to be written in DebugLogs/ folder near Telegram.exe. Each execution will produce three logs, .._log.txt (which was quoted above), .._mtp.txt (plain requests log), .._tcp.txt (plain network communication log, was not used ever :)

Don't forget to turn them off, or they will grow very fast + they have many private information inside (almost all of it, actually).

[azizur]

It works for me on Mac OS X 10.9.5

I export proxy settings as environment variables then launch telegram using command line when I am behind proxy.

[jlindsay]

https://techcrunch.com/2014/04/24/apple-google-intel-and-adobe-settle-antitrust-lawsuit-over-no-hire-agreement/

lets not forget there has been many allegations of wage suppression in silicon valley.

http://www.hightechemployeelawsuit.com/

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.