Impossible de communiquer GET avec le serveur AdGuard | Message : {}||3|

benj29 · Septembre 7, 2022, 2:53

Sur les conseils de @nebz j’ai tenté d’installer adguard sur ma debian11 (fresh après avoir viré pihole).
Il semble parfaitement fonctionner et il est bien plus simple à installer et configurer effectivement !

Par contre, au moment de mettre l’objet dans le plugin :
|2022-09-07 16:46:00|AdGuard|Impossible de communiquer GET avec le serveur AdGuard 192.168.2.94 version.json ! Message : {}||3|

En debug :

[2022-09-07 16:49:50]DEBUG : Modification commande:refresh
[2022-09-07 16:49:50]DEBUG : Modification commande:online
[2022-09-07 16:49:50]DEBUG : Modification commande:hasUpdateAdGuard
[2022-09-07 16:49:50]DEBUG : Modification commande:UpdateAdGuard
[2022-09-07 16:49:50]DEBUG : Modification commande:currentVersion
[2022-09-07 16:49:50]DEBUG : Modification commande:newVersion
[2022-09-07 16:49:50]DEBUG : Modification commande:protection_enabled
[2022-09-07 16:49:50]DEBUG : Modification commande:protection_enable
[2022-09-07 16:49:50]DEBUG : Modification commande:protection_disable
[2022-09-07 16:49:50]DEBUG : Modification commande:filtering_enabled
[2022-09-07 16:49:50]DEBUG : Modification commande:filtering_enable
[2022-09-07 16:49:50]DEBUG : Modification commande:filtering_disable
[2022-09-07 16:49:50]DEBUG : Modification commande:safebrowsing_enabled
[2022-09-07 16:49:50]DEBUG : Modification commande:safebrowsing_enable
[2022-09-07 16:49:50]DEBUG : Modification commande:safebrowsing_disable
[2022-09-07 16:49:50]DEBUG : Modification commande:parental_enabled
[2022-09-07 16:49:50]DEBUG : Modification commande:parental_enable
[2022-09-07 16:49:50]DEBUG : Modification commande:parental_disable
[2022-09-07 16:49:50]DEBUG : Modification commande:safesearch_enabled
[2022-09-07 16:49:50]DEBUG : Modification commande:safesearch_enable
[2022-09-07 16:49:50]DEBUG : Modification commande:safesearch_disable
[2022-09-07 16:49:50]DEBUG : Modification commande:blocked_services
[2022-09-07 16:49:50]DEBUG : Modification commande:service_block
[2022-09-07 16:49:50]DEBUG : Modification commande:service_unblock
[2022-09-07 16:49:50]DEBUG : Modification commande:services_block
[2022-09-07 16:49:50]DEBUG : Modification commande:services_unblock
[2022-09-07 16:49:50]DEBUG : Modification commande:blocked_internet
[2022-09-07 16:49:50]DEBUG : Modification commande:internet_block
[2022-09-07 16:49:50]DEBUG : Modification commande:internet_unblock
[2022-09-07 16:49:50]DEBUG : Modification commande:add_custom_rule
[2022-09-07 16:49:50]DEBUG : Modification commande:del_custom_rule
[2022-09-07 16:49:50]DEBUG : Modification commande:reset_stats
[2022-09-07 16:49:50]DEBUG : Modification commande:num_dns_queries
[2022-09-07 16:49:50]DEBUG : Modification commande:num_blocked_filtering
[2022-09-07 16:49:50]DEBUG : Modification commande:num_replaced_safebrowsing
[2022-09-07 16:49:50]DEBUG : Modification commande:num_replaced_parental
[2022-09-07 16:49:50]DEBUG : Modification commande:num_replaced_safesearch
[2022-09-07 16:49:50]DEBUG : Modification commande:avg_processing_time
[2022-09-07 16:50:00]ERROR : Impossible de communiquer GET avec le serveur AdGuard 192.168.2.94 version.json ! Message : {}
[2022-09-07 16:50:00]INFO : Reçu info de AdGuard Home
[2022-09-07 16:50:00]DEBUG : Reçu:{"dns_addresses":["127.0.0.1","::1","192.168.2.94"],"dns_port":53,"http_port":80,"protection_enabled":true,"dhcp_available":true,"running":true,"version":null,"language":"","safebrowsing":{"enabled":true},"parental":{"enabled":true},"safesearch":{"enabled":true},"filtering":{"filters":"deleted","whitelist_filters":null,"user_rules":["[]"],"interval":24,"enabled":true},"stats":{"time_units":"hours","top_queried_domains":"deleted","top_clients":"deleted","top_blocked_domains":"deleted","dns_queries":"deleted","blocked_filtering":"deleted","replaced_safebrowsing":"deleted","replaced_parental":"deleted","num_dns_queries":670,"num_blocked_filtering":131,"num_replaced_safebrowsing":0,"num_replaced_safesearch":1,"num_replaced_parental":0,"avg_processing_time":0.009228},"clients":{"clients":null,"auto_clients":"deleted","supported_tags":"deleted"},"blocked_services":[]}
[2022-09-07 16:50:12]ERROR : Impossible de communiquer GET avec le serveur AdGuard 192.168.2.94 version.json ! Message : {}
[2022-09-07 16:50:12]INFO : Reçu info de AdGuard Home
[2022-09-07 16:50:12]DEBUG : Reçu:{"dns_addresses":["127.0.0.1","::1","192.168.2.94"],"dns_port":53,"http_port":80,"protection_enabled":true,"dhcp_available":true,"running":true,"version":null,"language":"","safebrowsing":{"enabled":true},"parental":{"enabled":true},"safesearch":{"enabled":true},"filtering":{"filters":"deleted","whitelist_filters":null,"user_rules":["[]"],"interval":24,"enabled":true},"stats":{"time_units":"hours","top_queried_domains":"deleted","top_clients":"deleted","top_blocked_domains":"deleted","dns_queries":"deleted","blocked_filtering":"deleted","replaced_safebrowsing":"deleted","replaced_parental":"deleted","num_dns_queries":670,"num_blocked_filtering":131,"num_replaced_safebrowsing":0,"num_replaced_safesearch":1,"num_replaced_parental":0,"avg_processing_time":0.009228},"clients":{"clients":null,"auto_clients":"deleted","supported_tags":"deleted"},"blocked_services":[]}

Le port 80 et 53 sont ouverts (après avoir installé ufw).
Je reste déjà sur le plain DNS pour démarrer.

J’ai loupé quoi ?

nebz · Septembre 7, 2022, 3:25

normalement tu dois avoir un fichier version.json :

http://IP/control/version.json

comme indiqué dans leur API de la v0.107 : https://github.com/AdguardTeam/AdGuardHome/blob/master/openapi/openapi.yaml#L129

tu as installé quelle version ?

tu vois le numéro de version tout en bas à droite, tu as bien installé adguard home ?

nebz · Septembre 7, 2022, 3:30

tu n’aurais pas un problème du coté de tes logs adguard ?

github.com/AdguardTeam/AdGuardHome

Request issue while using webinterface

opened 08:43AM - 07 Sep 22 UTC

closed 09:44AM - 07 Sep 22 UTC

BoBBer446

invalid

### Prerequisites - [X] I have checked the [Wiki](https://github.com/AdguardTea…m/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions) 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 ### Operating system type Other (please mention in the description) ### CPU architecture 64-bit ARM ### Installation GitHub releases or script from README ### Setup On one machine ### AdGuard Home version Version: v0.102.0 ### Description After installation i get this issue on webinterface: `Error: control/version.json | Couldn't get version check json from https://static.adguard.com/adguardhome/release/version.json: *url.Error Get "https://static.adguard.com/adguardhome/release/version.json": couldn't initialize HTTP client or transport, cause: couldn't do a POST request to 'https://dns10.quad9.net:443/dns-query', cause: Get "https://dns10.quad9.net:443/dns-query?dns=dpgBAAABAAAAAAAACGlwdjRvbmx5BGFycGEAAAEAAQ": x509: certificate signed by unknown authority | 502` Installed on Rasbian OS `pi@raspberrypi:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" `

nebz · Septembre 7, 2022, 3:40

Tu es dans une période de bad luck pour l’instant non ?

nebz · Septembre 7, 2022, 3:51

Comme ça peut arriver que le fichier ne soit pas là, je vais passer le log en warning dans ce cas la

benj29 · Septembre 7, 2022, 6:47

Oui, adguard home.

http://192.168.2.94/control/version.json
me retourne :

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=nYgBAAABAAAAAAAABnN0YXRpYwZhZHRpZHkDb3JnAAABAAE": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Version :
v0.107.11

J’ai ça qui apparait régulièrement :

J’ai bien tenté :

dpkg-reconfigure ca-certificates

qui donne rien de probant :

Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Processing triggers for ca-certificates (20210119) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.

et qui ne résoud rien…

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=iuEBAAABAAAAAAAABnN0YXRpYwZhZHRpZHkDb3JnAAAcAAE": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

nebz · Septembre 7, 2022, 7:05

Encore une fois j’y suis pour rien… tu peux ignorer les erreurs en attendant que je réduise le niveau de log

benj29 · Septembre 8, 2022, 4:00

Mais le tien marche ? Tu l’utilises sous quelle distrib ?

nebz · Septembre 8, 2022, 5:28

oui aucun problème debian 11 sur LXC

nebz · Septembre 8, 2022, 5:50

hier 22h10 ils ont sorti la v0.107.12 et qui continue de fonctionner chez moi

benj29 · Septembre 8, 2022, 8:07

OK je vais voir… sérieux

benj29 · Septembre 9, 2022, 6:19

Et c’est réglé.
j’ai réinstallé la nouvelle version, il a fallu reconfigurer et j’ai ajouté les filtrages DNS et tout tourne !

system · Septembre 10, 2022, 6:20

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.