http: TLS handshake error #1081

New issue

Closed

opened 2026-03-04 01:03:20 -05:00 by deekerman · 3 comments

deekerman commented

2026-03-04 01:03:20 -05:00

Owner

Originally created by @ammnt on GitHub (Nov 8, 2019).

Originally assigned to: @szolin on GitHub.

Hello,

VPS, Debian 9, AGH 0.99.2. I'm not sure it 's a bug. But when I use the web-interface, i at once see a errors in the log:

2019/11/08 20:58:50 http: TLS handshake error from IP:53525: EOF
2019/11/08 21:37:59 http: TLS handshake error from IP:55822: EOF
2019/11/08 21:45:27 http: TLS handshake error from IP:56389: EOF

I use a certificate from Lets Encrypt for DoH, DoT, and HTTPS. DoT/DoH handshakes works without any errors. Tests on ssllabs.com and sslshopper.com successful. I can send the configuration file, domain and full logs to devteam@adguard.com.

Thank you.

Originally created by @ammnt on GitHub (Nov 8, 2019). Originally assigned to: @szolin on GitHub. Hello, VPS, Debian 9, AGH 0.99.2. I'm not sure it 's a bug. But when I use the web-interface, i at once see a errors in the log: ``` 2019/11/08 20:58:50 http: TLS handshake error from IP:53525: EOF 2019/11/08 21:37:59 http: TLS handshake error from IP:55822: EOF 2019/11/08 21:45:27 http: TLS handshake error from IP:56389: EOF ``` I use a certificate from Lets Encrypt for DoH, DoT, and HTTPS. DoT/DoH handshakes works without any errors. Tests on ssllabs.com and sslshopper.com successful. I can send the configuration file, domain and full logs to devteam@adguard.com. Something similar is described here: https://stackoverflow.com/questions/34823724/golang-tls-handshake-error https://stackoverflow.com/questions/39547459/golang-http2-and-tls-handshake-errors Thank you.

deekerman

2026-03-04 01:03:20 -05:00

closed this issue
added the
enhancement

P4: Low
labels

deekerman commented

2026-03-04 01:03:26 -05:00

Author

Owner

@ameshkov commented on GitHub (Nov 13, 2019):

This means that the client closed connections unexpectedly, this is not really a problem.

I think we should simply log this with DEBUG level, not ERROR.

@ameshkov commented on GitHub (Nov 13, 2019): This means that the client closed connections unexpectedly, this is not really a problem. I think we should simply log this with DEBUG level, not ERROR.

deekerman commented

2026-03-04 01:03:26 -05:00

Author

Owner

@szolin commented on GitHub (Nov 13, 2019):

These don't seem like our log messages. What application writes these logs?

@szolin commented on GitHub (Nov 13, 2019): These don't seem like our log messages. What application writes these logs?

deekerman commented

2026-03-04 01:03:26 -05:00

Author

Owner

@ameshkov commented on GitHub (Nov 13, 2019):

@szolin it's ours of course. We should've configured ErrorLog *log.Logger for the http.Server instance.

@ameshkov commented on GitHub (Nov 13, 2019): @szolin it's ours of course. We should've configured `ErrorLog *log.Logger` for the `http.Server` instance.

deekerman referenced this issue

2026-03-04 01:12:31 -05:00

Set name for clients #1298

deekerman referenced this issue

2026-03-04 01:15:07 -05:00

Assigning tags to clients in AdGuardHome UI #1362

deekerman referenced this issue

2026-03-04 01:17:31 -05:00

Allow one time or temporary unblock of sites on the client #1422