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

validating ports: duplicated values: [3000] #4095

Closed
3 tasks
faisalramly opened this issue Jan 6, 2022 · 7 comments
Closed
3 tasks

validating ports: duplicated values: [3000] #4095

faisalramly opened this issue Jan 6, 2022 · 7 comments
Assignees
@EugeneOne1
Labels
bug P2: High
Milestone
v0.107.3

Comments

@faisalramly
Copy link

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.

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

Issue Details

  • Version of AdGuard Home server:
  • How did you install AdGuard Home:
  • How did you setup DNS configuration:
  • If it's a router or IoT, please write device model:
  • CPU architecture:
  • Operating system and version:

Expected Behavior

Actual Behavior

Screenshots

Screenshot:

Additional Information
@v2raye
Copy link

v2raye commented Jan 7, 2022

After the new installation, I also encountered the same problem as you, and I fell back to v0.106.3 (Google Translate)

@EugeneOne1
Copy link
Member

@faisalramly, hello. Could you please fill in the issue template since we couldn't determine the actual problem otherwise. However I suppose you're trying to set the port 3000 somewhere during the initial setup. The thing is that the initial setup web page is using it so it can't be assigned to anything else at this moment. You may try to set another temporary port (e.g. 4000) and change it afterwards via the AdGuardHome.yaml configuration file. Please let us know if it worked for you.

@EugeneOne1 EugeneOne1 added the waiting for data Waiting for users to provide more data. label Jan 10, 2022
@EugeneOne1 EugeneOne1 mentioned this issue Jan 18, 2022
Closed
@ainar-g ainar-g self-assigned this Jan 18, 2022
@ainar-g ainar-g added bug P3: Medium and removed waiting for data Waiting for users to provide more data. labels Jan 18, 2022
@ainar-g ainar-g added this to the v0.107.3 milestone Jan 18, 2022
@ainar-g ainar-g added waiting for data Waiting for users to provide more data. and removed bug P3: Medium labels Jan 18, 2022
@ainar-g ainar-g removed this from the v0.107.3 milestone Jan 18, 2022
@ainar-g ainar-g removed their assignment Jan 18, 2022
@Kratosak
Copy link

Kratosak commented Jan 18, 2022 •
edited
Loading

I was running AdguardHome via docker smoothly without issues but then I found out that AGH is not working anymore. I had port 3000 assigned for web interface and when I opened link to web interface I get initial setup page. So whole configuration seems to be deleted. I tried assign port 3000 to web interface in step 2/5 but I get error "validating ports: duplicated values: [3000]". I thought that another application is using port 3000 but it is not true. So in this case because of this bug I probably lost whole AGH setup and need to do whole process again when it will be fixed.

@ainar-g ainar-g added bug P2: High and removed waiting for data Waiting for users to provide more data. labels Jan 19, 2022
@ainar-g ainar-g added this to the v0.107.3 milestone Jan 19, 2022
adguard pushed a commit that referenced this issue Jan 19, 2022
@EugeneOne1
Pull request: 4095 fix duplicating port
d82b290 
Merge in DNS/adguard-home from 4095-port-3000 to master

Updates #4095.

Squashed commit of the following:

commit 968cc80
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:26:33 2022 +0300

    home: fix typo

commit 03c6798
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:20:34 2022 +0300

    all: more naming imps

commit d3d417f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:10:14 2022 +0300

    aghalgo: rename into aghalg

commit 6e10600
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:05:43 2022 +0300

    all: imp names, docs

commit 12c8d9f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 19:57:21 2022 +0300

    all: fix log of changes

commit 49c7a70
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 19:51:00 2022 +0300

    home: fix duplicating port 3000
@EugeneOne1
Copy link
Member

EugeneOne1 commented Jan 19, 2022 •
edited
Loading

@faisalramly, @Kratosak, hello again. After a little internal discussion we've decided to restore the ability of specifying 3000 for web interface's port during the initial setup. The latest build in the edge channel should implement it. Could you please try it and check if it now works? Thanks.

@Kratosak
Copy link

@EugeneOne1 hello. I did following thing:
docker pull adguard/adguardhome:edge
Now I was able to use port 3000 for web interface. I see that version is v0.108.0-a.34+2fdda8a2. What was the reason for denying port 3000?
I would be ok to use port 3001 for web interface but I would like to avoid situation in the future that also 3001 would be denied.

Thank you.

@EugeneOne1
Copy link
Member

@Kratosak. That was a bug actually, no actual reasons for denying it, sorry for confusion.

As for port 3001, it is used for beta web interface but only in development builds like edge/beta ones. In release builds it should also be free for binding.

@EugeneOne1
Copy link
Member

@faisalramly, I'll close the issue for now since it seems being resolved. Please feel free to reopen it if the problem remains.

adguard pushed a commit that referenced this issue Jan 21, 2022
@EugeneOne1 @ainar-g
cherry-pick: 4095 fix duplicating port
b7f0247 
Merge in DNS/adguard-home from 4095-port-3000 to master

Updates #4095.

Squashed commit of the following:

commit 968cc80
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:26:33 2022 +0300

    home: fix typo

commit 03c6798
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:20:34 2022 +0300

    all: more naming imps

commit d3d417f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:10:14 2022 +0300

    aghalgo: rename into aghalg

commit 6e10600
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:05:43 2022 +0300

    all: imp names, docs

commit 12c8d9f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 19:57:21 2022 +0300

    all: fix log of changes

commit 49c7a70
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 19:51:00 2022 +0300

    home: fix duplicating port 3000
heyxkhoa pushed a commit to heyxkhoa/AdGuardHome that referenced this issue Mar 20, 2023
@EugeneOne1 @heyxkhoa
Pull request: 4095 fix duplicating port
b1dad4d 
Merge in DNS/adguard-home from 4095-port-3000 to master

Updates AdguardTeam#4095.

Squashed commit of the following:

commit 968cc80
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:26:33 2022 +0300

    home: fix typo

commit 03c6798
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:20:34 2022 +0300

    all: more naming imps

commit d3d417f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:10:14 2022 +0300

    aghalgo: rename into aghalg

commit 6e10600
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 20:05:43 2022 +0300

    all: imp names, docs

commit 12c8d9f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 19:57:21 2022 +0300

    all: fix log of changes

commit 49c7a70
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Jan 19 19:51:00 2022 +0300

    home: fix duplicating port 3000
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EugeneOne1 EugeneOne1

Labels
bug P2: High
Projects
None yet
Milestone
v0.107.3
Development

No branches or pull requests
5 participants
@ainar-g @EugeneOne1 @v2raye @Kratosak @faisalramly