mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
控制程序页面报错Error: control/version.json | checking ability to bind privileged ports: invalid argument | 500 #3739
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#3739
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CJM88888 on GitHub (Jun 14, 2022).
Originally assigned to: @ainar-g on GitHub.
Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Issue Details
Expected Behavior
进入控制程序页面出现报错Error: control/version.json | checking ability to bind privileged ports: invalid argument | 500Actual Behavior
Screenshots
Screenshot:
Additional Information
@yurividal commented on GitHub (Jul 15, 2022):
I have the same problem
@rivalcomp commented on GitHub (Aug 2, 2022):
Same here with v0.107.7, on a QNAP TS-469L NAS (Linux 3.4.6 #2 SMP Thu Mar 3 16:00:20 CST 2022 x86_64 GNU/Linux). Error message is the same. I've installed AdGuard latest QPKG from QnapClub Repo. AdGuard's own automatic update function has been working well until recent times.
@ainar-g commented on GitHub (Aug 3, 2022):
Apologies for the long silence. We can reproduce the issue and we'll try to fix it.
@ainar-g commented on GitHub (Aug 3, 2022):
@CJM88888, @yurividal, @rivalcomp, the latest Edge release,
v0.108.0-a.182+8a3d5f04, contains a fix for this issue. Could any one of you please check it?@berga commented on GitHub (Aug 3, 2022):
Latest version v0.107.9 fixed the problem on armv7
@ainar-g commented on GitHub (Aug 8, 2022):
We'll close this issue for now. Please feel free to open new issues if you find new bugs.
@CJM88888 commented on GitHub (Aug 10, 2022):
thanks
在 2022-08-04 06:57:02,"Marco Bergantin" @.***> 写道:
Latest version v0.107.9 fixed the problem on armv7
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>