search

AdguardTeam / AdGuardHome

Network-wide ads & trackers blocking DNS server
https://adguard.com/adguard-home.html
GNU General Public License v3.0
25.5k stars 1.83k forks source link

Doesn't work in Windows 11 after updating to v0.107.17 #5089

Closed SeriousHoax closed 2 years ago

SeriousHoax commented 2 years ago

Prerequisites

Operating system type

Windows

CPU architecture

x86

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

0.107.17

Description

What did you do?

Updated to the latest version

Expected result

Should work like before

Actual result

Doesn't work anymore

Screenshots (if applicable)

image

Additional information

Adguard Home is installed on my Windows 11 and runs on that device only. It was working fine, but today it asked for an update, so I updated it. After that it doesn't work anymore. When I try to visit websites in my browser, it shows the above error. Looks like the new update broke something.

xxnuo commented 2 years ago

Same as on ADG version: v0.107.17 and v0.108.0-b.20 Sys: Windows 10 专业工作站版 21H2 19044.2130

After updated its service fatals. manually runs panic:

2022/11/03 11:34:53.114326 [info] AdGuard Home, version v0.107.17
...
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x4 pc=0xf8a8bc]

goroutine 66 [running]:
github.com/AdguardTeam/urlfilter.(*DNSEngine).MatchRequest(0x0, 0x13075b3c)
        github.com/AdguardTeam/urlfilter@v0.16.0/dnsengine.go:131 +0xdc
github.com/AdguardTeam/AdGuardHome/internal/aghnet.(*requestMatcher).MatchRequest(0x132a2800, 0x13075b3c)
        github.com/AdguardTeam/AdGuardHome/internal/aghnet/hostscontainer.go:67 +0xf6
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).matchSysHosts(0x132b0a20, {0x14562000, 0x23}, 0x1c, 0x14556100)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:513 +0x10b
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).CheckHost(0x132b0a20, {0x14562000, 0x23}, 0x1c, 0x14556100)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:489 +0x1a7
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).filterDNSRequest(0x132f6000, 0x133a40f0)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/filter.go:71 +0x15e
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).processFilteringBeforeRequest(0x132f6000, 0x133a40f0)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:597 +0xa6
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).handleDNSRequest(0x132f6000, 0x132fe5a0, 0x14564000)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:115 +0x335
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).handleDNSRequest(0x132fe5a0, 0x14564000)
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server.go:130 +0x3d7
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpHandlePacket(0x132fe5a0, {0x13294600, 0x35, 0x35}, {0x0, 0x0, 0x0}, 0x1305f350, 0x142aa148)
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:109 +0x1e9
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop.func1()
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:76 +0x82
created by github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:75 +0x29c
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x4 pc=0xf8a8bc]

goroutine 55 [running]:
github.com/AdguardTeam/urlfilter.(*DNSEngine).MatchRequest(0x0, 0x13057b3c)
        github.com/AdguardTeam/urlfilter@v0.16.0/dnsengine.go:131 +0xdc
github.com/AdguardTeam/AdGuardHome/internal/aghnet.(*requestMatcher).MatchRequest(0x132a2800, 0x13057b3c)
        github.com/AdguardTeam/AdGuardHome/internal/aghnet/hostscontainer.go:67 +0xf6
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).matchSysHosts(0x132b0a20, {0x13117fb0, 0x23}, 0x1, 0x13119a00)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:513 +0x10b
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).CheckHost(0x132b0a20, {0x13117fb0, 0x23}, 0x1, 0x13119a00)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:489 +0x1a7
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).filterDNSRequest(0x132f6000, 0x132f41e0)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/filter.go:71 +0x15e
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).processFilteringBeforeRequest(0x132f6000, 0x132f41e0)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:597 +0xa6
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).handleDNSRequest(0x132f6000, 0x132fe5a0, 0x142a9b90)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:115 +0x335
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).handleDNSRequest(0x132fe5a0, 0x142a9b90)
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server.go:130 +0x3d7
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpHandlePacket(0x132fe5a0, {0x13126300, 0x35, 0x35}, {0x0, 0x0, 0x0}, 0x14558528, 0x142aa148)
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:109 +0x1e9
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop.func1()
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:76 +0x82
created by github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:75 +0x29c

after fresh install it happens again.

xxnuo commented 2 years ago

AdGuard Home v0.108.0-b.19 Works normally.

hl2guide commented 2 years ago

Yeah for me after upgrading to AdGuard Home v0.107.17 in Windows 11, the Windows Service keeps stopping.

A downgrade to AdGuard Home v0.107.16 worked though.

ZTHawk commented 2 years ago

Same issue with AdGuard v0.107.17. AdGuard v0.108.0-b.20 not working.

I am also on Windows 11 (22H2 -- 22621.674).

My log:

2022/11/03 10:43:37.761081 [info] AdGuard Home, version v0.108.0-b.20
2022/11/03 10:43:37.825951 [info] tls: using default ciphers
2022/11/03 10:43:37.828628 [info] Initializing auth module: <PRIVATE>
2022/11/03 10:43:37.829166 [info] auth: initialized.  users:1  sessions:5
2022/11/03 10:43:37.829708 [info] tls: number of certs: 1
2022/11/03 10:43:37.858632 [info] web: initializing
2022/11/03 10:43:39.961144 [info] DNS cache is enabled
2022/11/03 10:43:39.961854 [info] MaxGoroutines is set to 300
2022/11/03 10:43:39.967737 [info] AdGuard Home is available at the following addresses:
2022/11/03 10:43:39.968280 [info] Go to <PRIVATE>
2022/11/03 10:43:40.618098 [info] Starting the DNS proxy server
2022/11/03 10:43:40.619071 [info] Ratelimit is enabled and set to 50 rps
2022/11/03 10:43:40.619071 [info] The server is configured to refuse ANY requests
2022/11/03 10:43:40.619071 [info] DNS cache is enabled
2022/11/03 10:43:40.620108 [info] MaxGoroutines is set to 300
2022/11/03 10:43:40.620108 [info] Creating the UDP server socket
2022/11/03 10:43:40.620108 [info] Listening to udp://[::]:53
2022/11/03 10:43:40.620108 [info] Creating a TCP server socket
2022/11/03 10:43:40.621098 [info] Listening to tcp://[::]:53
2022/11/03 10:43:40.621098 [info] Creating a TLS server socket
2022/11/03 10:43:40.623045 [info] Listening to tls://[::]:853
2022/11/03 10:43:40.623045 [info] Creating a QUIC listener
2022/11/03 10:43:40.624057 [info] Listening to quic://[::]:784
2022/11/03 10:43:40.626584 [info] Entering the tls listener loop on [::]:853
2022/11/03 10:43:40.629516 [info] Entering the UDP listener loop on [::]:53
2022/11/03 10:43:40.633407 [info] Entering the tcp listener loop on [::]:53
2022/11/03 10:43:40.635432 [info] Entering the DNS-over-QUIC listener loop on [::]:784
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x8 pc=0x516738]

goroutine 33 [running]:
github.com/AdguardTeam/urlfilter.(*DNSEngine).MatchRequest(0x0, 0xc0007136d0)
        github.com/AdguardTeam/urlfilter@v0.16.0/dnsengine.go:131 +0x118
github.com/AdguardTeam/AdGuardHome/internal/aghnet.(*requestMatcher).MatchRequest(0xc0002d2d00, 0xc0006136d0)
        github.com/AdguardTeam/AdGuardHome/internal/aghnet/hostscontainer.go:67 +0x13a
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).matchSysHosts(0xc0002d9000, {0xc001372498, 0x16}, 0x9cc8?, 0xc0009833e0)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:513 +0x176
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).CheckHost(0xc0002d9000, {0xc001372498?, 0x1d710e0?}, 0x7ea0?, 0xc0009833e0)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:489 +0x247
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).filterDNSRequest(0xc000312000, 0xc0014554d0)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/filter.go:71 +0x1ab
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).processFilteringBeforeRequest(0xc000312000?, 0xc0014554d0)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:597 +0xbd
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).handleDNSRequest(0xc000312000, 0x912560?, 0xc0002d5200)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:115 +0x387
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).handleDNSRequest(0xc000134380, 0xc0002d5200)
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server.go:130 +0x398
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpHandlePacket(0xc000134380, {0xc0000ccab0, 0x28, 0x28}, {0x0, 0x0, 0x0}, 0xc0005d3710, 0xc0002b4058)
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:109 +0x2cb
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop.func1()
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:76 +0x4f
created by github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:75 +0x33e
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x8 pc=0x516738]

goroutine 9 [running]:
github.com/AdguardTeam/urlfilter.(*DNSEngine).MatchRequest(0x0, 0xc00160b6d0)
        github.com/AdguardTeam/urlfilter@v0.16.0/dnsengine.go:131 +0x118
github.com/AdguardTeam/AdGuardHome/internal/aghnet.(*requestMatcher).MatchRequest(0xc0002d2d00, 0xc0002756d0)
        github.com/AdguardTeam/AdGuardHome/internal/aghnet/hostscontainer.go:67 +0x13a
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).matchSysHosts(0xc0002d9000, {0xc0005c9a58, 0x16}, 0x9cc8?, 0xc0002ccf60)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:513 +0x176
github.com/AdguardTeam/AdGuardHome/internal/filtering.(*DNSFilter).CheckHost(0xc0002d9000, {0xc0005c9a58?, 0x1d710e0?}, 0x7ea0?, 0xc0002ccf60)
        github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:489 +0x247
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).filterDNSRequest(0xc000312000, 0xc0002c46c0)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/filter.go:71 +0x1ab
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).processFilteringBeforeRequest(0xc000312000?, 0xc0002c46c0)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:597 +0xbd
github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(*Server).handleDNSRequest(0xc000312000, 0x912560?, 0xc00015c300)
        github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:115 +0x387
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).handleDNSRequest(0xc000134380, 0xc00015c300)
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server.go:130 +0x398
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpHandlePacket(0xc000134380, {0xc0005e48d0, 0x28, 0x28}, {0x0, 0x0, 0x0}, 0xc001334000, 0xc0002b4058)
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:109 +0x2cb
github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop.func1()
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:76 +0x4f
created by github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop
        github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:75 +0x33e
raykai commented 2 years ago

Having the same problem as above and https://github.com/AdguardTeam/AdGuardHome/issues/5095

Chromos-Def commented 2 years ago

Downgrade restored functionality.

Something that caught my eye is the service would continue to run whenever I didn't have 127.0.0.1 set as my DNS through IPv4 network adapter settings.

sklynic commented 2 years ago

Same error on my ADG v0.107.17,running on win11 22h2 22621-674. Have to fallback to v0.107.16 to solve the problem. log: `panic: runtime error: invalid memory address or nil pointer dereference [signal 0xc0000005 code=0x0 addr=0x8 pc=0x12c6738]

goroutine 14 [running]: github.com/AdguardTeam/urlfilter.(DNSEngine).MatchRequest(0x0, 0xc000fd96d0) github.com/AdguardTeam/urlfilter@v0.16.0/dnsengine.go:131 +0x118 github.com/AdguardTeam/AdGuardHome/internal/aghnet.(requestMatcher).MatchRequest(0xc0001a3e80, 0xc0000d16d0) github.com/AdguardTeam/AdGuardHome/internal/aghnet/hostscontainer.go:67 +0x13a github.com/AdguardTeam/AdGuardHome/internal/filtering.(DNSFilter).matchSysHosts(0xc0001dd400, {0xc000fb0010, 0xd}, 0x9ce3?, 0xc000486180) github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:513 +0x176 github.com/AdguardTeam/AdGuardHome/internal/filtering.(DNSFilter).CheckHost(0xc0001dd400, {0xc000fb0010?, 0x2b210e0?}, 0x7ea0?, 0xc000486180) github.com/AdguardTeam/AdGuardHome/internal/filtering/filtering.go:489 +0x247 github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(Server).filterDNSRequest(0xc00017a000, 0xc0000a4120) github.com/AdguardTeam/AdGuardHome/internal/dnsforward/filter.go:71 +0x1ab github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(Server).processFilteringBeforeRequest(0xc00017a000?, 0xc0000a4120) github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:597 +0xbd github.com/AdguardTeam/AdGuardHome/internal/dnsforward.(Server).handleDNSRequest(0xc00017a000, 0x16c2560?, 0xc000fba000) github.com/AdguardTeam/AdGuardHome/internal/dnsforward/dns.go:115 +0x387 github.com/AdguardTeam/dnsproxy/proxy.(Proxy).handleDNSRequest(0xc000138380, 0xc000fba000) github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server.go:130 +0x398 github.com/AdguardTeam/dnsproxy/proxy.(Proxy).udpHandlePacket(0xc000138380, {0xc0014809a0, 0x1f, 0x1f}, {0x0, 0x0, 0x0}, 0xc001170000, 0xc00014e140) github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:109 +0x2cb github.com/AdguardTeam/dnsproxy/proxy.(Proxy).udpPacketLoop.func1() github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:76 +0x4f created by github.com/AdguardTeam/dnsproxy/proxy.(*Proxy).udpPacketLoop github.com/AdguardTeam/dnsproxy@v0.46.2/proxy/server_udp.go:75 +0x33e`

AnthonyBe commented 2 years ago

Same for me on Windows Server 2012 R2.

v0.107.16 running fine. v0.107.17 the service stops immediately after starting.

Looks like there are plenty of sets of logs from other reporters, but I can grab some if needed.

bh commented 2 years ago

Same on Archlinux ARM aarch64: https://aur.archlinux.org/packages/adguardhome#comment-887980

RealAmes commented 2 years ago

Same on Server 2019

jakesteele commented 2 years ago

Same Windows Server 2022

kissgaby commented 2 years ago

Sys: Windows 10 专业 2004 19041.264 v0.107.17 Works normally.

pekkle-hksar commented 2 years ago

Same problem here... I'm using Edge version in Windows 11.

v0.108.0-a.357+68d13fcc is still working, seems some changes after this break Windows version.

BTW, I'm also running latest Linux Edge version under Ubuntu, and it works fine.

Steve-337 commented 2 years ago

Same problem Windows 11 pro 22H2（22623.875）

TheWizzard2203 commented 2 years ago

v0.107.16 running fine. v0.107.17 the service stops immediately after starting.

This on Win11_22H2 with latest updates. Any fix?

Workaround: Rolling back to former version 0.107.16

TheWizzard2203 commented 2 years ago

v0.107.16 running fine. v0.107.17 the service stops immediately after starting.

This on Win11_22H2 with latest updates. Any fix?

Workaround: Rolling back to former version 0.107.16

the cdn for winget source down used vpn and choose canda server,to check the winget source update

I'm not sure what you mean and how to do it🙈

q54528 commented 2 years ago

Same issue on Windows 10 (21H1) v0.107.17 the service stops immediately after starting. Windows Defender Defined the program(AdGuardHome.exe) as an unsafe app. However , When I return to v0.107.16 , when I set up my computer's DNS(127.0.0.1) ，I can't visit any website.

two error ： 1、【When I run AdGuardHome.exe 】 Failed to update filter https://adguardteam.github.io/AdGuardSDNSFilter/Filters/filter.txt: Get "https://adguardteam.github.io/AdGuardSDNSFilter/Filters/filter.txt": requesting https://dns10.quad9.net:443/dns-query: Get "https://dns10.quad9.net:443/dns-query?dns=AAABAAABAAAAAAABC2FkZ3VhcmR0ZWFtBmdpdGh1YgJpbwAAAQABAAApCAAAAIAAAAA": read tcp 192.168.0.64:4777->9.9.9.10:443: wsarecv: An existing connection was forcibly closed by the remote host.

2、【on 127.0.0.1:3000】 Error: control/version.json | getting version info from https://static.adtidy.org/adguardhome/release/version.json: updater: HTTP GET https://static.adtidy.org/adguardhome/release/version.json: Get "https://static.adtidy.org/adguardhome/release/version.json": requesting https://dns10.quad9.net:443/dns-query: Get "https://dns10.quad9.net:443/dns-query?dns=AAABAAABAAAAAAABBnN0YXRpYwZhZHRpZHkDb3JnAAABAAEAACkIAAAAgAAAAA": context deadline exceeded | 502.

So I update “filter.txt" manually , then I can visit non-https website , but can't visit https website

TheWizzard2203 commented 2 years ago

So what's the fix, besides not updating?

ainar-g commented 2 years ago

We weren't able to reproduce this crash, unfortunately. The version v0.108.0-a.378+464fbf0b, which we have just released to the Edge channel, fixes the most probable cause of this crash. Can anyone please confirm, if it does fix the crash?

If it does, we will release a hotfix for both Release and Beta channels.

If not, please configure your AdGuard Home to collect verbose logs and attach them to the issue. Thanks, and apologies for the inconvenience.

TheWizzard2203 commented 2 years ago

We weren't able to reproduce this crash, unfortunately. The version v0.108.0-a.378+464fbf0b, which we have just released to the Edge channel, fixes the most probable cause of this crash. Can anyone please confirm, if it does fix the crash?

If it does, we will release a hotfix for both Release and Beta channels.

If not, please configure your AdGuard Home to collect verbose logs and attach them to the issue. Thanks, and apologies for the inconvenience.

Hi Ainar-g. I'll test that as soon as I get home from work and let you know.

bh commented 2 years ago

We weren't able to reproduce this crash, unfortunately. The version v0.108.0-a.378+464fbf0b, which we have just released to the Edge channel, fixes the most probable cause of this crash. Can anyone please confirm, if it does fix the crash?

If it does, we will release a hotfix for both Release and Beta channels.

If not, please configure your AdGuard Home to collect verbose logs and attach them to the issue. Thanks, and apologies for the inconvenience.

@ainar-g I rebuilt the package with https://github.com/AdguardTeam/AdGuardHome/archive/464fbf0b543e6bc52eba0d5fdb305658e5669b68.tar.gz and it seems to be fixed. Archlinux ARM, aarch64, PI4

TheWizzard2203 commented 2 years ago

We weren't able to reproduce this crash, unfortunately. The version v0.108.0-a.378+464fbf0b, which we have just released to the Edge channel, fixes the most probable cause of this crash. Can anyone please confirm, if it does fix the crash? If it does, we will release a hotfix for both Release and Beta channels. If not, please configure your AdGuard Home to collect verbose logs and attach them to the issue. Thanks, and apologies for the inconvenience.

Hi Ainar-g. I'll test that as soon as I get home from work and let you know.

Hi ainar-g,

It is probably me not used to how github works but I can't find the link to the version you mentioned.

bh commented 2 years ago

@ainar-g I rebuilt the package with https://github.com/AdguardTeam/AdGuardHome/archive/464fbf0b543e6bc52eba0d5fdb305658e5669b68.tar.gz and it seems to be fixed. Archlinux ARM, aarch64, PI4

@TheWizzard2203 Use this Tar archieve, this is v0.108.0-a.378+464fbf0b.

ainar-g commented 2 years ago

@TheWizzard2203, you can get the archives for any CPU architecture, OS, and release channel from this Wiki page. After that, backup your AdGuard Home data and reinstall using the binary in the archive.

TheWizzard2203 commented 2 years ago

@TheWizzard2203, you can get the archives for any CPU architecture, OS, and release channel from this Wiki page. After that, backup your AdGuard Home data and reinstall using the binary in the archive.

Thanks, that's clear.

TheWizzard2203 commented 2 years ago

@TheWizzard2203, you can get the archives for any CPU architecture, OS, and release channel from this Wiki page. After that, backup your AdGuard Home data and reinstall using the binary in the archive.

This works flawlessly again. Just overwritten the files of the latest edge version to the files of 0.107.16 and it is still working.

ainar-g commented 2 years ago

Thanks everyone for testing! We'll make a hotfix release later today.