Closed martjay closed 11 months ago
What's Clash?
If you mean problem with connection on desktop version - i have the same problem
Cannot reproduce on 4.6 and 4.6.1.
By the way there seems to be no network-issue related messages in you log.
Maybe you should check your Clash for Windows settings, check the avalibility of your proxy servers in your Clash software, or replace Clash with other tools.
Can someone say what Clash is?
@ilya-fedin Clash is a popular[^pop] proxy software in China, support various proxy protocols which are aimed to bypass China's GFW (network block / censorship). And Clash for Windows is a Electron GUI frontend for Clash, which is also widely used in China among Windows users.
[^pop]: By "popular" I mean it's widely used, due to several reasons, but don't mean to say it's good, though.
Due to the censorship situation in mainland China, the severs can get banned from time to time, like in certain ISP's network or in certain city/province, which can cause connection failures.
Also, the original post isn't providing enough information, that is, for example, whether this Clash for Windows is running under TUN mode (which is not stable and robust enough) or not. And this can cause network failures, too.
Due to the censorship situation in mainland China, the severs can get banned from time to time, like in certain ISP's network or in certain city/province, which can cause connection failures.
Also, the original post isn't providing enough information, that is, for example, whether this Clash for Windows is running under TUN mode (which is not stable and robust enough) or not. And this can cause network failures, too.
My settings should be all right. I used to connect to telegram with clash before, but I don't know why the client can't get on now. The web version can be connected.
There is also a problem with Shadowsocks. Now I can't connect to the telegram desktop.
@martjay I'm not sure this is related to changes in code.
Can you check one of the previous versions from https://github.com/telegramddsktop/tdesktop/releases, starting with 4.5.3 or 4.4.1 or even older?
Download the portable version from the Assets dropdown, unpack in a clean folder, launch and try to connect - no need to fully complete the authorization, because it may lead to flood limits on authorizations, just see if it connects and shows the Qr code. Don't forget first thing to do is to open Settings and disable autoupdate, or it may quickly update to 4.6.2.
If it reproducibly does connect and then 4.6.2 doesn't we can compare the logs.
@martjay I'm not sure this is related to changes in code.
Can you check one of the previous versions from https://github.com/telegramddsktop/tdesktop/releases, starting with 4.5.3 or 4.4.1 or even older?
Download the portable version from the Assets dropdown, unpack in a clean folder, launch and try to connect - no need to fully complete the authorization, because it may lead to flood limits on authorizations, just see if it connects and shows the Qr code. Don't forget first thing to do is to open Settings and disable autoupdate, or it may quickly update to 4.6.2.
If it reproducibly does connect and then 4.6.2 doesn't we can compare the logs.
It is strange that I can connect to the web version of Telegram, but not connect to the client.
Nothing strange here, you don't connect to Telegram servers directly when using the web versions, your browser connects to the Telegram Web HTTP server instead.
Nothing strange here, you don't connect to Telegram servers directly when using the web versions, your browser connects to the Telegram Web HTTP server instead.
In the past, I used the same VPN node to connect to the telgram client. There was no problem at all, but now I don't know what I did to make the connection impossible.
Please answer the question
Can you check one of the previous versions from https://github.com/telegramdesktop/tdesktop/releases, starting with 4.5.3 or 4.4.1 or even older?
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
indeed, i also encountered such a problems. i'm not sure the problem is clash or telegram, but it not work in windows and ubuntu linux.
Please answer the question
Can you check one of the previous versions from https://github.com/telegramdesktop/tdesktop/releases, starting with 4.5.3 or 4.4.1 or even older? https://github.com/telegramdesktop/tdesktop/issues/25831#issuecomment-1453564155 telegram version 4.5.3 the version 4.6.5 is not work too
telegram version 4.5.3
so you say 4.4.1 works?
Please answer the question
Can you check one of the previous versions from https://github.com/telegramdesktop/tdesktop/releases, starting with 4.5.3 or 4.4.1 or even older?
[4.4.1]work! [4.5.3]work! Sorry, I'm late to reply to you. Recently, I have been using Kotatogram, which seems to use the interface of the web version or the interface of the old version of the client. At least there is no problem with the network connection. But after all, Kotatogram is not an official application, and it has not been updated for a long time, so I hope you can fix this problem. When it comes to the specific version, I can't remember it. It may have been the first three versions of my post.
When it comes to the specific version, I can't remember it.
Have you actually checked 4.4.1 / 4.5.3 now or have you remembered?
which seems to use the interface of the web version or the interface of the old version of the client
tdesktop never used the interface of the web version, so that's not possible
When it comes to the specific version, I can't remember it.
Have you actually checked 4.4.1 / 4.5.3 now or have you remembered?
which seems to use the interface of the web version or the interface of the old version of the client
tdesktop never used the interface of the web version, so that's not possible
I did a full version test today and 4.5.7 beta worked, from 4.58 beta onwards it doesn't work, so now I can say with certainty that all versions after 4.58 have this problem
telegram version 4.5.3
so you say 4.4.1 works?
not work
telegram version 4.5.3
so you say 4.4.1 works?
not work
From 4.58 beta onwards it doesn't work, previous versions were working. for me
I‘m using Clash Verge with the Clash.Meta core and have the same problem.
Looks like there's something wrong with HTTP proxies, socks5 has been working well on my computer. Last day I happened to try the HTTP proxy of sing-box, I failed too.
Hey there!
This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.
Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
Steps to reproduce
Use Clash for windows cannot be connected in last version.
Expected behaviour
I uploaded it
Actual behaviour
Use Clash for windows cannot be connected in last version
Operating system
windows 11 pro x64
Version of Telegram Desktop
4.6
Installation source
Static binary from official website
Logs