Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Checking the availability of upstream takes longer than expected #5193

Closed
3 tasks done
Versty opened this issue Nov 25, 2022 · 0 comments
Closed
3 tasks done

Checking the availability of upstream takes longer than expected #5193

Versty opened this issue Nov 25, 2022 · 0 comments
Assignees
@EugeneOne1
Labels
bug P3: Medium
Milestone
v0.107.20

Comments

@Versty
Copy link

Versty commented Nov 25, 2022

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

Operating system type

Linux, OpenWrt

CPU architecture

AMD64

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.19

Description

What did you do?

  1. Settings -> DNS settings: Add the blocked by an ISP upstream 94.140.14.140 and Apply settings
  2. Click the Test upstream button

Expected result

Error: Invalid upstream is shown after 2-7 seconds of checking.

Actual result

The checking takes up to 1 minute. If you refresh the page before the check is finished, the UI will be stuck on loading.
If you perform the service action: stop while the UI is being loaded, Adguard Home will be stopped with a delay.
@ainar-g ainar-g added this to the v0.107.20 milestone Dec 1, 2022
@adguard adguard closed this as completed in 6d1adf7 Dec 5, 2022
@ainar-g ainar-g modified the milestones: v0.107.21, v0.107.20 Dec 7, 2022
heyxkhoa pushed a commit to heyxkhoa/AdGuardHome that referenced this issue Mar 20, 2023
@EugeneOne1 @heyxkhoa
Pull request: 5193-long-ups-check
9e317d2 
Merge in DNS/adguard-home from 5193-long-ups-check to master

Closes AdguardTeam#5193.

Squashed commit of the following:

commit 787e6b9
Merge: f62330b 01652e6
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Dec 5 17:07:40 2022 +0300

    Merge branch 'master' into 5193-long-ups-check

commit f62330b
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Dec 5 16:28:47 2022 +0300

    dnsforward: try to fix linux

commit 64bfacc
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Dec 5 15:55:48 2022 +0300

    all: log changes finally

commit 4331d1c
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Dec 5 15:26:45 2022 +0300

    all: imp log of chagnes

commit 62ed3c1
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Dec 5 15:23:17 2022 +0300

    all: log changes

commit 73f4d59
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Dec 5 14:37:18 2022 +0300

    dnsforward: add defer

commit a15072f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Dec 5 14:30:16 2022 +0300

    dnsforward: imp tests

commit e74219f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Sat Dec 3 16:29:31 2022 +0300

    dnsforward: get rid of wg

commit 165da7d
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Fri Dec 2 15:42:55 2022 +0300

    dnsforward: add ups check test

commit 3045273
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Thu Dec 1 20:28:56 2022 +0300

    dnsforward: imp ups check perf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EugeneOne1 EugeneOne1

Labels
bug P3: Medium
Projects
None yet
Milestone
v0.107.20
Development

No branches or pull requests
3 participants
@ainar-g @EugeneOne1 @Versty