[Solved] DNS 14.3 Ignoring Web Port Settings #1915
Replies: 8 comments
-
|
Thanks for the post. You need to check for logs in the Logs > View Logs section on the panel to find out the reason for this. Usually the web service port will revert to default if the server fails to bind to the configured ports. So the error log will tell you the reason for the failure. Share the error log here if you need help with that. |
Beta Was this translation helpful? Give feedback.
-
|
Shreyas, Here is a cropped extract that covers the period where I fail to change the listening port:- I am not sure if it is related to the problem, but I also spotted another unexpected log entry:- My two DNS Servers are "bill" and "ben" [Primary / Secondary, respectively]... I have not looked in to that yet, not sure what that might be. Looking at the log data concerning the TCP port 80 issue... I think this is the relevant problem:- Failed to bind to address http://[::]:80: address already in use. But if I read that correctly, it is saying that there is an issue because I have an IPv6 address on the host that is trying to listen on TCP port 80... This seems a bit odd, given that I do not believe I have any active IPv6 configurations on the host:- I definitely see the port conflict error in the log... I am just not sure what can possibly be causing it, or why Technitium thinks there is IPv6 involved. When I check "Settings" > "General Settings" > "IPv6 Support", the toggle setting for "Prefer IPv6" is disabled [box is empty] and I see the error - I am just not sure what could possibly cause it... and it is puzzling because this is happening on one of my two "Production" Pi machines... and the only changes I've made to it recently were some hardening measures - in the file /boot/firmware/config.txt I added the value: dtoverlay=disable-wifi, then I used "sudo systemctl stop bluetooth" and "sudo systemctl disable bluetooth". Other than that - and regular software updates - this host hasn't been changed in weeks. |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if it helps... but the only other piece of software on this host that is likely to be listening on TCP socket 80 would be Apache2. After i saw the conflict previously [with Apache listening to all ports on socket 80] I made changes to Apache's ports.conf file to address the problem. Here is the edited/active version of /etc/apache2/ports.conf:- |
Beta Was this translation helpful? Give feedback.
-
|
Another piece to the puzzle... Given the nature of the Technitium error message - suggesting that there was something listening to socket 80... I went to my workstation and tried to perform an nmap port scan of the IPv6 address showing when I run "ip addr" on the Technitium host, just to see if there are active listeners. This is what I see in response:- |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the details.
This error confirms that the port is already in use. You need to run The DNS web service listens on
That is not related to this issue. You need to make sure that the source IP of the primary DNS is allowed by the secondary DNS. Check for the logs on secondary DNS to find out what source IP is being used.
You do have ipv6 addresses in there like
The IPv6 Support option is unrelated and used only for outbound requests. The source address too is not related to this and is also for outbound DNS requests. |
Beta Was this translation helpful? Give feedback.
-
|
OK, here's a really weird conclusion to this thread. If you know that expression, "Cannot see the wood for the trees" then you will understand that I went snowblind to the problem, even though it was right in front of me. I was able to resolve this issue by making one change to the "Settings" > "Web Service" page, where I removed the value found in the "Web Service Local Addresses" field - which was "::" and I changed that back to what it should have been, which was 172.16.100.1. I made the corresponding change to the Secondary DNS server and I've re-tested and I find that the web interface now has returned to operating as expected on socket 80. What I can't explain - at least not yet - is how or why the value of the "Web Service Local Addresses" field managed to change from my desired IPv4 address and had left the field at "::". That explains why the Technitium DNS Log made a reference to the web server listening on socket 80. But here's the weird thing... what seems to have happened here is that the way I had manually set each server [with "::" in the Web Service Local Addresses" and then specifying "80" in the Port field... Even though that should not have caused conflict, it seems to have done so. I'm not sure if this is an indicator that the service allows an internally inconsistent configuration that then undertakes some automated reset process. I have a strong hunch that the automatic reset is happening in the .Net library code on which Technitium is built - and I stress that I don't think that's in error. I'm sufficient intrigued that I'm going to experiment a bit more with this. That will have to wait just a little while though - I'm currently wrangling with a postfix/dovecot setup, but will circle back to this when I have that up and running. Thanks again, Shreyas, for responding to this thread. |
Beta Was this translation helpful? Give feedback.
-
|
For completeness, here's the output from "sudo ss -nlpt":- |
Beta Was this translation helpful? Give feedback.
-
|
You're welcome. Good to know that the issue is resolved with the config update. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Thought I would share a really weird behavior that I am seeing from my Primary/Secondary pair of DNS Servers, running codebase v14.3. I'm not recording this as a bug, because I know for a fact that prior to the last couple of days this setup has worked perfectly, so I suspect that what I'm experiencing is being caused by an external factor.
But I'm sharing in the hope that if anyone else sees this, they can speak up.
The behaviour is: both of my DNS Servers have unilaterally changed their Web Service Listener port back to 5380 after I went in and changed it to the HTTP default of 80. I can now go to the Web Admin interface [on port 5380], select "Settings" and then "Web Service" and change the value of "Web Service HTTP Port" from the default value of 5380 to my preference of 80. I then "Save Settings" - but immediately after doing that, my Firefox browser tries to reload the page and reports an error.
Because this is Firefox 150.0.1, it also automatically ignores my use of "HTTP" and restores the browser to using HTTPS by default.
The odd thing is that the "Save Settings" with the port changed to 80 seems to work... but the moment I try to reload the page, either the core code hasn't actually written the change to disk, or it simply ignores and resets it.
I did see something very similar to this a while back, but that was caused when another piece of software on the same host [Apache] started to listen on socket 80 on the same IP Address - Technitium simply reverted to 5380. This time there is nothing on this IP address listening on this port.
I can work around the problem by editing my browser bookmarks to record socket 5380 for my two DNS instances... but I'd be very interested to know if anyone else has seen this and - if so - what they found or did to fix the issue...
In case it is relevant, both machines running Technitium DNS in my case are Raspberry Pi 4B/8Gb models, running the full Trixie image.
The only other thing I see when looking at the machines is that they were both reboot yesterday, about 27.5 hours ago. I did not intentionally reboot either of these machines, so I'm starting to wonder if maybe I had a power grid failure and didn't notice it, or maybe there was something else that happened.
Again, I'm not convinced this is an issue caused by Technitium - the DNS on both machines has been running flawlessly for weeks now. I suspect that something else in my environment is causing this... but I just can seem to find it [yet].
Any thoughts/suggestions very gratefully received.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions