starred/AdGuardHome

Fork 0

mirror of https://github.com/AdguardTeam/AdGuardHome.git synced 2026-03-04 00:01:12 -05:00

High CPU Usage and Service Crash in v0.107.61 Under TLS Handshake Failures and DNS Upstream Timeouts #5638

New issue

Open

opened 2026-03-04 06:22:31 -05:00 by deekerman · 3 comments

deekerman commented

2026-03-04 06:22:31 -05:00

Owner

Originally created by @danielraffel on GitHub (Apr 29, 2025).

Prerequisites

I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.61

Action

Since upgrading to v0.107.61, AdGuard Home experiences a sudden CPU spike up to ~180% usage and then crashes/restarts roughly once per day.

This issue was not observed on earlier versions.

Expected result

AdGuard Home should maintain stable CPU usage and operate continuously without crashing.

Actual result

•	CPU usage spikes to ~180% unexpectedly.
•	Application crashes and a script eventually auto-restarts the server
•	Occurs daily, seemingly without manual interaction.

Additional information and/or screenshots

Observed behavior:
Regular TLS handshake errors and DNS upstream timeouts flood logs, corresponding with CPU usage spikes that eventually lead to service crash or watchdog-triggered VM reboot.

Error samples:
[error] http: TLS handshake error from 127.0.0.1:xxxxx: remote error: tls: bad certificate server=https
ERROR response received addr=https://family.adguard-dns.com:443/dns-query proto=tcp status="request canceled (Client.Timeout exceeded while awaiting headers)"

While I don't see a specific issue

✅ TLS issues and DNS timeouts are stressing AdGuard Home.
✅ Large volume of error spam may explain why CPU usage explodes.

Originally created by @danielraffel on GitHub (Apr 29, 2025). ### Prerequisites - [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer - [x] I have searched other issues and found no duplicates - [x] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) - [x] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.) ### Platform (OS and CPU architecture) Linux, AMD64 (aka x86_64) ### Installation GitHub releases or script from README ### Setup On one machine ### AdGuard Home version v0.107.61 ### Action Since upgrading to v0.107.61, AdGuard Home experiences a sudden CPU spike up to ~180% usage and then crashes/restarts roughly once per day. This issue was not observed on earlier versions. ### Expected result AdGuard Home should maintain stable CPU usage and operate continuously without crashing. ### Actual result • CPU usage spikes to ~180% unexpectedly. • Application crashes and a script eventually auto-restarts the server • Occurs daily, seemingly without manual interaction. ### Additional information and/or screenshots Observed behavior: Regular TLS handshake errors and DNS upstream timeouts flood logs, corresponding with CPU usage spikes that eventually lead to service crash or watchdog-triggered VM reboot. Error samples: [error] http: TLS handshake error from 127.0.0.1:xxxxx: remote error: tls: bad certificate server=https ERROR response received addr=https://family.adguard-dns.com:443/dns-query proto=tcp status="request canceled (Client.Timeout exceeded while awaiting headers)" While I don't see a specific issue ✅ TLS issues and DNS timeouts are stressing AdGuard Home. ✅ Large volume of error spam may explain why CPU usage explodes.

deekerman added the

cannot reproduce

waiting for data

labels

2026-03-04 06:22:31 -05:00

deekerman commented

2026-03-04 06:22:44 -05:00

Author

Owner

@tjharman commented on GitHub (May 7, 2025):

Hi,

Are you able to provide anymore logs/details about the crash(es)? There is an option (you'll have to edit yaml) to get detailed logs.
Can you reproduce the same issue if you roll back to the previous version you were using?
Do you have any other network issues ongoing? It appears from the small log snippet you've provided ADH is having trouble reaching the AdGuard servers for the family protection blocking. What happens if you temporarily disable this feature?

I haven't seen any other similar issues to this posted, so I would have to assume at the moment this is something local to your setup. But please look at the steps above and report back.

@tjharman commented on GitHub (May 7, 2025): Hi, 1. Are you able to provide anymore logs/details about the crash(es)? There is an option (you'll have to edit yaml) to get detailed logs. 2. Can you reproduce the same issue if you roll back to the previous version you were using? 3. Do you have any other network issues ongoing? It appears from the small log snippet you've provided ADH is having trouble reaching the AdGuard servers for the family protection blocking. What happens if you temporarily disable this feature? I haven't seen any other similar issues to this posted, so I would have to assume at the moment this is something local to your setup. But please look at the steps above and report back.

deekerman commented

2026-03-04 06:22:48 -05:00

Author

Owner

@sky92682 commented on GitHub (May 19, 2025):

I've recently encountered a similar issue with intermittent high CPU and memory usage. After investigation, it turned out to be the AdGuard Home integration in Home Assistant. It periodically requests paths like /control/stats from the server to obtain information. Disabling this integration resolved the problem. You can try logging into the AdGuard Home management interface in your browser first, and then attempt to access this path to observe if AdGuard Home's CPU usage spikes.

@sky92682 commented on GitHub (May 19, 2025): I've recently encountered a similar issue with intermittent high CPU and memory usage. After investigation, it turned out to be the AdGuard Home integration in Home Assistant. It periodically requests paths like /control/stats from the server to obtain information. Disabling this integration resolved the problem. You can try logging into the AdGuard Home management interface in your browser first, and then attempt to access this path to observe if AdGuard Home's CPU usage spikes.

deekerman commented

2026-03-04 06:22:48 -05:00

Author

Owner

@tjharman commented on GitHub (Jun 30, 2025):

@danielraffel Is this still a problem? Did you get anywhere with logs etc?

@tjharman commented on GitHub (Jun 30, 2025): @danielraffel Is this still a problem? Did you get anywhere with logs etc?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/AdGuardHome#5638

No description provided.

Rows
Columns