I locked myself from the WebUI

[Gapoly]

Hello,

I've accidently put 127.0.0.1 in the WebUI allow access and I can't change it anymore. I still have access to SSH but I don't know which file I'm supposed to look in to change it? I've looked in /etc/dns and /opt/technitium/dns.

I've installed it in a Debian LXC container.

[ShreyasZare]

Thanks for asking. There are a few methods you can do to fix this issue:

• If you can remember and redo all the option in the Settings section then just stop the DNS server with "systemctl stop dns", delete the file "/etc/dns/dns.config" and start the DNS server back with "systemctl start dns". This will reset all the settings and you can then access the panel on HTTP with port 5380.

• The other option is to use a reverse proxy like nginx if you already have it installed on the server. You will need to create a TCP stream that proxies to "127.0.0.1:53443" or "127.0.0.1:5380" and then gain access to change the setting.

• Another option is to use the HTTP API to change the settings from SSH console using curl and jq commands (install curl and jq if not already installed using apt-get). Run the commands shown below:

$ DNS_TOKEN=`curl "http://localhost:5380/api/user/login?user=admin&pass=<your-admin-password-here>" | jq -r ".token"`
$ curl "http://localhost:5380/api/settings/set?token=$DNS_TOKEN&webServiceLocalAddresses=0.0.0.0,[::]&webServiceHttpToTlsRedirect=false"
$ curl "http://localhost:5380/api/user/logout?token=$DNS_TOKEN"

The above commands will reset the web server's local addresses to default and also disable HTTP to HTTPS redirection so that you can access the admin panel from port 5380 in case HTTPS still does not work.

Let me know if you were able to get it working.

[Gapoly]

Thank, I used the first since it was the easier.

One question though, why is the file dns.config crypted?

Wouldn't have been easier to leave it uncrypted for easier modifying?

[ShreyasZare]

All the config files are in binary format. The reason for this is that the DNS server itself updates the config files as required. So, its done to discourage users from editing it manually since any changes made directly may get overwritten by the DNS server when you restart it to try to apply those manual changes. The only way available to configure the DNS server is using the HTTP API which also does proper validation and prevents from having incorrect config which may cause downtime.