configuration menu does not accept ports

[dabeegmon]

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 or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

FreeBSD, AMD64 (aka x86_64)

Installation

Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)

Setup

On one machine

AdGuard Home version

no way of checking right at the moment

Action

Replace the following command with the one you're calling or a
description of the failing action:

in configuration menu trying to enter ports for web admin interface and DNS

Expected result

ports accepted and allowed to enter name and password

Actual result

getting red network issues listed
sometimes only one or two sometimes quite a few more

So - - - I'm supposed to have installed AND configured AdGuard correctly (its a demand in the prerequisites) but this is precisely where I'm have the problem. Have to check this so that I can submit the issue. (Awkward logic in my opinion forcing an answer that is incorrect as a requirement to enter an issue!)

Additional information and/or screenshots

No response

[tjharman]

I'm very sorry but I don't really understand the bug report. Could you prehaps include some screenshots or something to make it clear what the issue is. Where did you install AdguardHome from? Could you also please include the version you've got installed - you say no way of checking, but how/where did you install it in the first place?

Thanks.

[ainar-g]

Likely a duplicate of #741 and/or #2860.

[dabeegmon]

On Mon, Jul 15, 2024 at 7:21 AM Ainar Garipov ***@***.***> wrote: Likely a duplicate of #741 <#741> and/or #2860 <#2860>.

I have been unable to provide information yet because its a bloody complicated route to get any. Have read through the listed other issue ###s and I don't think that this issue will be like these. AdGuard Home 0.107.50 <https://adguard.com/en/versions/home/release.html#version-010750> Release date: May 24, 2024 They say, if it isn't broken — don't fix it. Unfortunately, this is not the case with the last AdGuard Home update 😓 A small portion of users haven't been able to start AdGuard Home at all, and so we are rolling out this hotfix. This (above) scares me as this seems to be close to what I'm experiencing. Issues : AdGuard Home is being used as a community supported service in OPNsense. Repository is held by one mimugmail and I don't think the same version numbers are used. The system that is running OPNsense in on a mini-pc and I'm using a very low strength laptop to try and use the web management (coming to not be too fond of web applications in the process!). The bloody thing (laptop) has a very very short life (runtime) so it takes the coordination of quite a number of factors to get the information that I have to get to you - - - hopefully very soon. Thanking you all for your patience and consideration Message ID: ***@***.***>

…

[tjharman]

Do you really think this is an Adguard Home issue, and if so can you articulate clearly why? This seems like some issue with an underpowered laptop, running Opnsense and some unknown 3rd party package of Adguard Home that's broken/not working.

[dabeegmon]

On Mon, Jul 15, 2024 at 6:24 PM Tim Harman ***@***.***> wrote: Do you really think this is an Adguard Home issue, and if so can you articulate clearly why? This seems like some issue with an underpowered laptop, running Opnsense and some unknown 3rd party package of Adguard Home that's broken/not working.

What I can articulate is that you are not carefully reading what I have written! laptop is NOT running opnsense! Opnsense is on a mini-pc that is quite capable of handling close to 1 Gbps - - - - which for a firewall router isn't too shabby. Laptop is underpowered but that's only being used to manipulate opnsense (seems to be a web kind of platform AFAICT). Hmmmmmmmmmm - - - unknown 3rd party package - - - have you actually looked up mimugmail - - - sure doesn't seem like it. I included in my previous message some text from Adguard Home's own release notes which so far seem quite closely aligned with the issues I've had. Had you read that part of the message? I'm presently at the end of my day and I won't be starting stuff that takes concentration and is fraught with challenges at this time. Hopefully I will be able to tackle things in my late morning. Until then

…

Message ID: ***@***.***>

[tjharman]

Apologies for obviously upsetting you. I would still recommend you take up your issues with the person/group that has packaged your version of AdguardHome you are running on your opnsense router. If they are adamant the problem is with AdGuardHome itself, please get them to put some technical details into this ticket.

[dabeegmon]

On Mon, Jul 15, 2024 at 9:59 PM Tim Harman ***@***.***> wrote: Apologies for obviously upsetting you. I would still recommend you take up your issues with the person/group that has packaged your version of AdguardHome you are running on your opnsense router. If they are adamant the problem is with AdGuardHome itself, please get them to put some technical details into this ticket.

I wasn't so much upset as frustrated that what I was reported was being half read with judgements being levied based upon incomplete evidence. Installed was AdGuardHome-maxit version 1.12 from the repository run by mimugmail. The info section indicates that version 1.12 is version 0.107.45 of AdGuardHome. The issue shows up when the initial setup of AdGuardHome is attempted. On a screen that looks somewhat like the attached pic I was trying to setup the first two items. 1. 192.168.1.1 LAN #### 2. 192.168.1.1 LAN #### I was following https://windgate.net/setup-adguard-home-opnsense-adblocker/ to get things working. #1 I tried everything from 3000 to 3020 for port numbers #2 I tried everything from 5553 and 5053 to some few up and down each time there would be a red text popup which stated something like that there was a networking setup error going back to setup screen 2 / 5 and trying different numbers resulted in the configuration screen disappearing. After this happened a couple times it was no longer possible to use 192.168.1.1:3000 to log into the configuration menu. (Digging for any possible information there are at least blogs or info pages of well over a half dozen different entities running AdGuardHome on OPNsense (and maybe Pfsense) so my guess is that there are more than an occasional number of entities actually using (or trying to use) this combination.) I really don't know what the problem is (or are) but the update for 0.107.50 indicates that I'm not the only one having some difficulties. Will the trying to contact the mimugmail repository and asking about a possible update - - - what version should I be asking for - - - perhaps 0.107.52? TIA

…

Message ID: ***@***.***>