AdguardTeam / AdguardForWindows

AdGuard for Windows open bug tracker
https://adguard.com/
679 stars 72 forks source link

[Bug] Teamspeak Sync not working when filtered #1409

Closed Bluscream closed 5 years ago

Bluscream commented 7 years ago

https://www.myteamspeak.com/register http://www.teamspeak.com/downloads.html#client Taken from Teamspeak's logs:

11/23/2016 14:42:03 ProtobufRPC Warning Error contacting URL https://clientapi.myteamspeak.com/addon: SSL_ERROR: Alert on protocol: TLS 1.2 level: fatal error: unsupported_certificate (43)    
11/23/2016 14:42:15 ProtobufRPC Warning Error contacting URL https://clientapi.myteamspeak.com/authentication: SSL_ERROR: Alert on protocol: TLS 1.2 level: fatal error: unsupported_certificate (43)   
11/23/2016 13:44:22 ProtobufRPC Warning Error contacting URL https://clientapi.myteamspeak.com/synchronization: SSL_ERROR: Alert on protocol: TLS 1.2 level: fatal error: unsupported_certificate (43)
11/23/2016 14:41:49 ProtobufRPC Warning Error contacting URL https://clientapi.myteamspeak.com/user: SSL_ERROR: Alert on protocol: TLS 1.2 level: fatal error: unsupported_certificate (43)

I tried to add these rules

@@||clientapi.myteamspeak.com^$document
@@||clientapi.myteamspeak.com^$stealth
@@||clientapi.myteamspeak.com^generichide
@@||clientapi.myteamspeak.com^genericblock

but it still shows this error.

https://www.sslshopper.com/ssl-checker.html#hostname=clientapi.myteamspeak.com

image

https://blogs.msdn.microsoft.com/kaushal/2012/10/05/ssltls-alert-protocol-the-alert-codes/#43

Received an unsupported certificate type.

Microsoft Windows 8.1 [Version 6.3.9600] x64 AdGuard BETA 6.1.287.1519 Chrome Canary 56.0.2889.0 (Official Build) (64-Bit) Opera Stable 41.0.2353.56
ameshkov commented 7 years ago

It should be enough to add clientapi.myteamspeak.com to HTTPS exclusions in AG settings.

Bluscream commented 7 years ago

adding api.myteamspeak.com works fine, thanks. Can you add this to the default list, i think Teamspeak is a very popular application, @ameshkov :)

ameshkov commented 7 years ago

Yep, done

Bluscream commented 7 years ago

Somehow badges are not loading when Adguard filtering is enabled

ameshkov commented 7 years ago

Anything useful in the filtering log?

Bluscream commented 7 years ago

According to TeamSpeak's log:

1/26/2017 17:02:23  Addons  Info    Checking for addon updates...   
1/26/2017 17:02:28  BadgesService   Info    Request user badges callback, received 2 user badges    
1/26/2017 17:03:48      Info    Init dialog with 2 badges   
1/26/2017 17:04:58  BadgesService   Info    No badgeinfo for 1cb07348-34a4-4741-b50f-c41e584370f7   
1/26/2017 17:04:58  BadgesService   Info    No badgeinfo for 50bbdbc8-0f2a-46eb-9808-602225b49627   

image

Not very useful, right? Want adguard's log files?

Bluscream commented 7 years ago

Even with clientapi.myteamspeak.com on my https whitelist I get

1/30/2017 14:58:01  ProtobufRPC Warning Server at URL https://clientapi.myteamspeak.com/authenticationresponded: 500 Internal Server Error  
1/30/2017 14:58:23  ProtobufRPC Warning Server at URL https://clientapi.myteamspeak.com/synchronizationresponded: 500 Internal Server Error 
2017-01-30 14:48:04.790672|WARNING |ProtobufRPC   |   |Server at URL https://clientapi.myteamspeak.com/userresponded: 500 Internal Server Error
2017-01-30 14:47:56.626261|WARNING |ProtobufRPC   |   |Server at URL https://clientapi.myteamspeak.com/addonresponded: 500 Internal Server Error
ameshkov commented 7 years ago

I definitely need Adguard's log

Bluscream commented 7 years ago

I will send logs quickly after it happened next time.

Bluscream commented 7 years ago

Update:

Bluscream commented 7 years ago

Fix for badges: Add badges-content.teamspeak.com to HTTPS exceptions =)

Bluscream commented 5 years ago

With 7.X DNS resolving inside TeamSpeak is broken while AG filtering is on (tray icon has green checkmark) and ts3client_win64.exe is filtered (even with the "lock icon" crossed out [https filtering disabled], it just resolves all DNS queries until timeout.

Log with filtering enabled:

3/6/2019 16:34:15   ClientUI    Info    Connect to server: gommehd.net  
3/6/2019 16:34:15   ClientUI    Info    Trying to resolve gommehd.net   
3/6/2019 16:37:14   TSDNS   Info    A/AAAA DNS resolve unsuccessful, "gommehd.net" Timeout while contacting DNS servers 
3/6/2019 16:37:24   TSDNS   Info    SRV DNS resolve unsuccessful, "_ts3._udp.gommehd.net" Timeout while contacting DNS servers  
3/6/2019 16:37:24   TSDNS   Info    A/AAAA DNS resolve unsuccessful, "gommehd.net" DNS server returned answer with no data  
3/6/2019 16:37:28   TSDNS   Info    SRV DNS resolve unsuccessful, "_tsdns._tcp.gommehd.net" Timeout while contacting DNS servers    
3/6/2019 16:37:28   ClientUI    Info    Lookup finished: query= error=2 
3/6/2019 16:37:28   ClientUI    Info    Failed to resolve gommehd.net   

Log with filtering disabled:

3/6/2019 16:43:38   ClientUI    Info    Trying to resolve gommehd.net   
3/6/2019 16:43:38   ClientUI    Info    Connect to server: gommehd.net  
3/6/2019 16:43:41   TSDNS   Info    SRV DNS resolve unsuccessful, "_tsdns._tcp.gommehd.net" Domain name not found   
3/6/2019 16:43:41   TSDNS   Info    A/AAAA DNS resolve successful, "gommehd.net" =(h: 212.224.77.85 p:0)    
3/6/2019 16:43:42   TSDNS   Info    A/AAAA DNS resolve for possible TSDNS successful, "gommehd.net" =(h: 212.224.77.85 p:0) 
3/6/2019 16:43:42   TSDNS   Info    SRV DNS resolve successful, "_ts3._udp.gommehd.net" =(h: ts3.gommehd.net p:9987)    
3/6/2019 16:43:44   TSDNS   Info    TSDNS queried unsuccessfully 212.224.77.85:41144    
3/6/2019 16:43:44   TSDNS   Info    No TSDNS found  
3/6/2019 16:43:45   TSDNS   Info    A/AAAA DNS resolve successful, "ts3.gommehd.net" =(h: 79.133.54.207 p:0)    
3/6/2019 16:43:45   ClientUI    Info    Lookup finished: ip=79.133.54.207 port=9987 query=gommehd.net error=0   
3/6/2019 16:43:45   ClientUI    Info    Resolve successful: 79.133.54.207:9987  
3/6/2019 16:43:45   ClientUI    Info    Initiating connection: 79.133.54.207:9987   
3/6/2019 16:43:45   ClientUI    Info    Connect status: Connecting  
3/6/2019 16:43:45   ClientUI    Info    Connect status: Connected   
3/6/2019 16:43:46   ClientUI    Info    Connect status: Establishing connection 
3/6/2019 16:43:46   ClientUI    Info    Connect status: Connection established  
maurawa commented 5 years ago

how can i do this with kaspersky?

ameshkov commented 5 years ago

It is now possible to disable HTTPs filtering for a particular app

Bluscream commented 5 years ago

how can i do this with kaspersky?

https://forum.teamspeak.com/threads/129989-Can-t-Login-To-Teamspeak-Account-(SSL_ERROR-Alert-on-protocol-TLS-1-2)?s=c851d61f1c9d2446912cfaee81cbbeb2&p=443379#post443379