telegramdesktop / tdesktop

Telegram Desktop messaging app
https://desktop.telegram.org/
Other
26.14k stars 5.18k forks source link

Use Clash for windows cannot be connected in last version #25831

Closed martjay closed 11 months ago

martjay commented 1 year ago

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

[2023.02.04 18:43:00] Launched version: 4006000, install beta: [TRUE], alpha: 0, debug mode: [FALSE]
[2023.02.04 18:43:00] Executable dir: E:/Program Files/Telegram Desktop/, name: Telegram.exe
[2023.02.04 18:43:00] Initial working dir: E:/Program Files/Telegram Desktop/
[2023.02.04 18:43:00] Working dir: E:/Program Files/Telegram Desktop/
[2023.02.04 18:43:00] Command line: E:\Program Files\Telegram Desktop\Telegram.exe
[2023.02.04 18:43:00] Executable path before check: E:/Program Files/Telegram Desktop/Telegram.exe
[2023.02.04 18:43:00] Logs started
[2023.02.04 18:43:00] Connecting local socket to Global\1c54aa7a7a5cc9d4f108443c939a5718-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2023.02.04 18:43:00] This is the only instance of Telegram, starting server and app...
[2023.02.04 18:43:00] Moved logging from 'E:/Program Files/Telegram Desktop/log_start0.txt' to 'E:/Program Files/Telegram Desktop/log.txt'!
[2023.02.04 18:43:00] Global devicePixelRatio: 1
[2023.02.04 18:43:00] Primary screen DPI: 120, Base: 96.
[2023.02.04 18:43:00] Computed screen scale: 125
[2023.02.04 18:43:00] DevicePixelRatio: 1
[2023.02.04 18:43:00] ScreenScale: 125
[2023.02.04 18:43:00] Font: from ':/gui/fonts/DAOpenSansRegular.ttf' loaded 'DAOpenSansRegular'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAOpenSansRegularItalic.ttf' loaded 'DAOpenSansRegularItalic'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2023.02.04 18:43:01] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2023.02.04 18:43:01] Using DirectX compiler 'E:\Program Files\Telegram Desktop\modules\x64\d3d\d3dcompiler_47.dll'.
[2023.02.04 18:43:01] App Info: reading settings...
[2023.02.04 18:43:01] App Info: reading encrypted settings...
[2023.02.04 18:43:01] Lang Info: Loaded cached, keys: 3936
[2023.02.04 18:43:01] Lang Error: Unexpected tag (key 'lng_action_add_user:users')
[2023.02.04 18:43:01] Lang Error: Expected '}' after tag name (key 'lng_confirm_phone_about:phone')
[2023.02.04 18:43:01] Lang Info: Loaded cached, keys: 3988
[2023.02.04 18:43:01] Lang Error: Expected '}' after tag name (key 'lng_confirm_phone_about:phone')
[2023.02.04 18:43:01] OpenAL Logging Level: (not set)
[2023.02.04 18:43:01] Audio Playback Devices: OpenAL Soft on 扬声器 (M-Audio M-Track Solo and Duo);OpenAL Soft on 扬声器 (THX Spatial);OpenAL Soft on Realtek Digital Output (Realtek High Definition Audio);OpenAL Soft on VoiceMeeter Aux Input (VB-Audio VoiceMeeter AUX VAIO);OpenAL Soft on VoiceMeeter Input (VB-Audio VoiceMeeter VAIO);OpenAL Soft on VoiceMeeter VAIO3 Input (VB-Audio VoiceMeeter VAIO3);OpenAL Soft on DELL U2518D (NVIDIA High Definition Audio)
[2023.02.04 18:43:01] Audio Playback Default Device: OpenAL Soft on 扬声器 (M-Audio M-Track Solo and Duo)
[2023.02.04 18:43:01] Audio Capture Devices: OpenAL Soft on Line 1/2 (M-Audio M-Track Solo and Duo);OpenAL Soft on 麦克风 (DroidCam Virtual Audio);OpenAL Soft on VoiceMeeter Output (VB-Audio VoiceMeeter VAIO);OpenAL Soft on 麦克风 (WO Mic Device);OpenAL Soft on VoiceMeeter Aux Output (VB-Audio VoiceMeeter AUX VAIO);OpenAL Soft on VoiceMeeter VAIO3 Output (VB-Audio VoiceMeeter VAIO3)
[2023.02.04 18:43:01] Audio Capture Default Device: OpenAL Soft on Line 1/2 (M-Audio M-Track Solo and Duo)
[2023.02.04 18:43:01] App Info: reading accounts info...
[2023.02.04 18:43:01] App Info: reading encrypted info...
[2023.02.04 18:43:01] App Info: reading map...
[2023.02.04 18:43:01] App Info: reading encrypted map...
[2023.02.04 18:43:01] App Info: reading encrypted user settings...
[2023.02.04 18:43:01] App Info: encrypted user settings read.
[2023.02.04 18:43:01] App Info: reading encrypted mtp data...
[2023.02.04 18:43:01] MTP Info: read keys, current: 5, to destroy: 0
[2023.02.04 18:43:01] Map read time: 7
[2023.02.04 18:43:01] App Info: reading encrypted mtp config...
[2023.02.04 18:43:02] Export Info: Destroy top bar by controller removal.
[2023.02.04 18:43:02] OpenGL: Using custom 'gpu_driver_bug_list.json'.
[2023.02.04 18:43:02] OpenGL Profile: OpenGLES.
[2023.02.04 18:43:02] OpenGL Renderer: ANGLE (NVIDIA, NVIDIA GeForce RTX 2070 SUPER Direct3D11 vs_5_0 ps_5_0, D3D11-31.0.15.2824)
[2023.02.04 18:43:02] OpenGL Vendor: Google Inc. (NVIDIA)
[2023.02.04 18:43:02] OpenGL Version: OpenGL ES 3.0.0 (ANGLE 2.1.7 git hash: 0bb011f9e403)
[2023.02.04 18:43:02] OpenGL Extensions: GL_EXT_texture_compression_bptc, GL_EXT_texture_compression_rgtc, GL_OES_mapbuffer, GL_OVR_multiview, GL_OVR_multiview2, GL_NV_pack_subimage, GL_WEBGL_video_texture, GL_EXT_blend_func_extended, GL_ANGLE_multi_draw, GL_EXT_multisampled_render_to_texture, GL_ANGLE_texture_compression_dxt3, GL_EXT_color_buffer_half_float, GL_OES_depth32, GL_ANGLE_texture_usage, GL_ANGLE_base_vertex_base_instance, GL_ANGLE_depth_texture, GL_OES_compressed_EAC_R11_signed_texture, GL_OES_texture_float, GL_EXT_shader_texture_lod, GL_OES_texture_half_float, GL_OES_compressed_ETC2_RGBA8_texture, GL_EXT_discard_framebuffer, GL_EXT_texture_compression_dxt1, GL_EXT_draw_elements_base_vertex, GL_EXT_sRGB, GL_OES_get_program_binary, GL_OES_packed_depth_stencil, GL_ANGLE_explicit_context_gles1, GL_OES_draw_buffers_indexed, GL_OES_texture_half_float_linear, GL_NV_fence, GL_OES_texture_stencil8, GL_ANGLE_copy_texture_3d, GL_NV_EGL_stream_consumer_external, GL_ANGLE_program_cache_control, GL_EXT_occlusion_query_boolean, GL_ANGLE_pack_reverse_row_order, GL_CHROMIUM_sync_query, GL_ANGLE_provoking_vertex, GL_OES_texture_border_clamp, GL_EXT_draw_buffers_indexed, GL_OES_compressed_EAC_RG11_signed_texture, GL_ANGLE_texture_multisample, GL_ANGLE_explicit_context, GL_ANGLE_multiview_multisample, GL_OES_draw_elements_base_vertex, GL_OES_standard_derivatives, GL_EXT_EGL_image_external_wrap_modes, GL_OES_compressed_ETC2_sRGB8_alpha8_texture, GL_ANGLE_framebuffer_blit, GL_CHROMIUM_bind_uniform_location, GL_ANGLE_texture_compression_dxt5, GL_EXT_debug_label, GL_OES_texture_float_linear, GL_KHR_parallel_shader_compile, GL_ANGLE_get_serialized_context_string, GL_OES_surfaceless_context, GL_ANGLE_lossy_etc_decode, GL_EXT_blend_minmax, GL_OES_compressed_EAC_R11_unsigned_texture, GL_OES_vertex_array_object, GL_EXT_texture_filter_anisotropic, GL_EXT_draw_buffers, GL_EXT_map_buffer_range, GL_KHR_debug, GL_OES_fbo_render_mipmap, GL_ANGLE_robust_client_memory, GL_EXT_texture_norm16, GL_EXT_unpack_subimage, GL_CHROMIUM_copy_texture, GL_EXT_robustness, GL_OES_depth24, GL_OES_rgb8_rgba8, GL_EXT_disjoint_timer_query, GL_EXT_color_buffer_float, GL_EXT_texture_rg, GL_ANGLE_translated_shader_source, GL_CHROMIUM_bind_generates_resource, GL_NV_pixel_buffer_object, GL_OES_compressed_EAC_RG11_unsigned_texture, GL_EXT_texture_storage, GL_OES_EGL_image_external_essl3, GL_EXT_texture_compression_s3tc_srgb, GL_ANGLE_client_arrays, GL_OES_EGL_image, GL_EXT_debug_marker, GL_EXT_float_blend, GL_EXT_instanced_arrays, GL_OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture, GL_OES_element_index_uint, GL_OES_EGL_image_external, GL_ANGLE_framebuffer_multisample, GL_EXT_frag_depth, GL_CHROMIUM_copy_compressed_texture, GL_ANGLE_get_tex_level_parameter, , GL_ANGLE_memory_size, GL_OES_compressed_ETC2_sRGB8_texture, GL_OES_texture_npot, GL_ANGLE_request_extension, GL_CHROMIUM_lose_context, GL_EXT_read_format_bgra, GL_OES_compressed_ETC2_RGB8_texture, GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture, GL_ANGLE_instanced_arrays, GL_EXT_texture_format_BGRA8888
[2023.02.04 18:43:02] EGL Extensions: EGL_EXT_create_context_robustness, EGL_ANGLE_d3d_share_handle_client_buffer, EGL_ANGLE_d3d_texture_client_buffer, EGL_ANGLE_surface_d3d_texture_2d_share_handle, EGL_ANGLE_query_surface_pointer, EGL_ANGLE_window_fixed_size, EGL_ANGLE_keyed_mutex, EGL_ANGLE_surface_orientation, EGL_ANGLE_direct_composition, EGL_ANGLE_windows_ui_composition, EGL_NV_post_sub_buffer, EGL_KHR_create_context, EGL_KHR_image, EGL_KHR_image_base, EGL_KHR_gl_texture_2D_image, EGL_KHR_gl_texture_cubemap_image, EGL_KHR_gl_renderbuffer_image, EGL_KHR_get_all_proc_addresses, EGL_KHR_stream, EGL_KHR_stream_consumer_gltexture, EGL_NV_stream_consumer_gltexture_yuv, EGL_ANGLE_flexible_surface_compatibility, EGL_ANGLE_stream_producer_d3d_texture, EGL_ANGLE_create_context_webgl_compatibility, EGL_CHROMIUM_create_context_bind_generates_resource, EGL_CHROMIUM_sync_control, EGL_EXT_pixel_format_float, EGL_KHR_surfaceless_context, EGL_ANGLE_display_texture_share_group, EGL_ANGLE_display_semaphore_share_group, EGL_ANGLE_create_context_client_arrays, EGL_ANGLE_program_cache_control, EGL_ANGLE_robust_resource_initialization, EGL_ANGLE_create_context_extensions_enabled, EGL_ANDROID_blob_cache, EGL_ANDROID_recordable, EGL_ANGLE_image_d3d11_texture, EGL_ANGLE_create_context_backwards_compatible, EGL_KHR_create_context_no_error, EGL_KHR_reusable_sync, 
[2023.02.04 18:43:02] OpenGL: QOpenGLContext created, version: 3.3.
[2023.02.04 18:43:02] OpenGL: [TRUE] (OverlayWidget)
martjay commented 1 year ago

666666

ilya-fedin commented 1 year ago

What's Clash?

Pinchicryak2 commented 1 year ago

If you mean problem with connection on desktop version - i have the same problem

zedifen commented 1 year ago

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.

Snipaste_2023-02-07_13-00-39

ilya-fedin commented 1 year ago

Can someone say what Clash is?

zedifen commented 1 year ago

@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.

zedifen commented 1 year ago

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.

martjay commented 1 year ago

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.

666666 777777

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.

888888

john-preston commented 1 year ago

@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 commented 1 year ago

@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.

ilya-fedin commented 1 year ago

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.

martjay commented 1 year ago

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.

ilya-fedin commented 1 year ago

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?

github-actions[bot] commented 1 year ago

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.

shiboyang commented 1 year ago

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. Screenshot from 2023-03-03 21-52-31

shiboyang commented 1 year ago

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

ilya-fedin commented 1 year ago

telegram version 4.5.3

so you say 4.4.1 works?

martjay commented 1 year ago

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.

ilya-fedin commented 1 year ago

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

martjay commented 1 year ago

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

shiboyang commented 1 year ago

telegram version 4.5.3

so you say 4.4.1 works?

not work

martjay commented 1 year ago

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

Xuyiyang23333 commented 1 year ago

I‘m using Clash Verge with the Clash.Meta core and have the same problem. 图片

zedifen commented 1 year ago

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.

github-actions[bot] commented 1 year ago

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!