Adguard not starting

I try to install Adguard Home add-on but htius Add-on does not start.
I have a fix ip-adres.

Had Adguard installed before and then it was working. Now i will not start :slight_smile:
Here is the log :

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: AdGuard Home
Network-wide ads & trackers blocking DNS server

Add-on version: 4.8.5
You are running the latest version of this add-on.
System: Home Assistant OS 9.5 (aarch64 / raspberrypi3-64)
Home Assistant Core: 2023.4.4
Home Assistant Supervisor: 2023.04.0

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-adguard: starting
s6-rc: info: service init-nginx successfully started
s6-rc: info: service init-adguard successfully started
s6-rc: info: service adguard: starting
s6-rc: info: service adguard successfully started
s6-rc: info: service discovery: starting
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
[16:03:29] INFO: Starting AdGuard Home server…
2023/04/15 16:03:29.981053 [info] AdGuard Home, version v0.107.28
2023/04/15 16:03:29.982399 [info] AdGuard Home updates are disabled
2023/04/15 16:03:29.983666 [info] home.upgradeSchema0to1(): called
2023/04/15 16:03:29.984004 [info] deleting /data/adguard/dnsfilter.txt as we don’t need it anymore
2023/04/15 16:03:29.984410 [info] home.upgradeSchema1to2(): called
2023/04/15 16:03:29.984642 [info] deleting /data/adguard/Corefile as we don’t need it anymore
2023/04/15 16:03:29.984892 [info] home.upgradeSchema2to3(): called
2023/04/15 16:03:29.985062 [info] home.upgradeSchema3to4(): called
2023/04/15 16:03:29.985265 [info] home.upgradeSchema4to5(): called
2023/04/15 16:03:29.985413 [info] home.upgradeSchema5to6(): called
2023/04/15 16:03:29.985533 [info] Upgrade yaml: 6 to 7
2023/04/15 16:03:29.985637 [info] Upgrade yaml: 7 to 8
2023/04/15 16:03:29.985755 [info] Upgrade yaml: 8 to 9
2023/04/15 16:03:29.985884 [info] Upgrade yaml: 9 to 10
2023/04/15 16:03:29.986012 [info] Upgrade yaml: 10 to 11
2023/04/15 16:03:29.986203 [info] Upgrade yaml: 11 to 12
2023/04/15 16:03:29.986343 [info] Upgrade yaml: 12 to 13
2023/04/15 16:03:29.986474 [info] Upgrade yaml: 13 to 14
2023/04/15 16:03:29.986678 [info] Upgrade yaml: 14 to 15
2023/04/15 16:03:29.986820 [info] Upgrade yaml: 15 to 16
2023/04/15 16:03:29.986985 [info] Upgrade yaml: 16 to 17
2023/04/15 16:03:29.987157 [info] Upgrade yaml: 17 to 18
2023/04/15 16:03:29.987317 [info] Upgrade yaml: 18 to 19
2023/04/15 16:03:29.987476 [info] Upgrade yaml: 19 to 20
2023/04/15 16:03:30.012469 [info] tls: using default ciphers
2023/04/15 16:03:30.041692 [info] safesearch default: reset 253 rules
2023/04/15 16:03:30.062435 [info] Initializing auth module: /data/adguard/data/sessions.db
2023/04/15 16:03:30.075388 [info] auth: initialized. users:0 sessions:0
2023/04/15 16:03:30.075477 [info] web: initializing
2023/04/15 16:03:30.092368 [info] dnsproxy: cache: enabled, size 4096 b
2023/04/15 16:03:30.092450 [info] MaxGoroutines is set to 300
2023/04/15 16:03:30.092971 [info] AdGuard Home is available at the following addresses:
2023/04/15 16:03:30.093056 [info] go to http://127.0.0.1:45158
2023/04/15 16:03:30.113683 [info] Starting the DNS proxy server
2023/04/15 16:03:30.113759 [info] Ratelimit is enabled and set to 20 rps
2023/04/15 16:03:30.113780 [info] The server is configured to refuse ANY requests
2023/04/15 16:03:30.113802 [info] dnsproxy: cache: enabled, size 4194304 b
2023/04/15 16:03:30.113839 [info] MaxGoroutines is set to 300
2023/04/15 16:03:30.113892 [info] Creating the UDP server socket
2023/04/15 16:03:30.114390 [info] Listening to udp://127.0.0.1:53
2023/04/15 16:03:30.114826 [info] Creating a TCP server socket
2023/04/15 16:03:30.115753 [info] Listening to tcp://127.0.0.1:53
2023/04/15 16:03:30.116199 [info] Entering the UDP listener loop on 127.0.0.1:53
2023/04/15 16:03:30.116815 [info] Entering the tcp listener loop on 127.0.0.1:53
[16:03:30] INFO: Starting NGinx…
2023/04/15 16:03:31.813625 [info] saving contents of filter #1 into /data/adguard/data/filters/1.txt
2023/04/15 16:03:31.814684 [info] updated filter 1: 1006856 bytes, 51269 rules
2023/04/15 16:03:31.815576 [info] Updated filter #1. Rules: 0 → 51269
[16:03:32] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

Please help.

Finale, after three day looking for an answer, after summiting this threat I found the solution :

ha supervisor restart