Try to use your script but not working

[midosa14]

Hi,

First of all, thanks for your work.

I try to use the script to add cert to Technitium.

I don't have the totp activated. When putting admin, admin password, for totp, i'll try empty or numbers, but i have every time the same error

[ERROR] Technitium settings/set failed.

How can i bypass this issue ?

Thanks for your help.

[midosa14]

i know why. Sorry

[luizbizzio]

Hi, great that you could solve the problem, also could you tell me what was the problem? Maybe it can help others in the future

[midosa14]

Hi, in fact problem is not solved. I'll try to install Technitium locally, not in container but same problem.
After admin user (admin), admin password and enter (because no totp), i've the same error " [ERROR] Technitium settings/set failed."

Any idea, why is not working ?
Thanks

[luizbizzio]

First, I would like to know the hardware you are using, also the OS and the version

Technitium username no need for typing, you can just press enter

The password, are you sure it is "admin"?

And TOTP if you are not using, just press enter

Btw, what version of the Technitium?

[midosa14]

OS: Ubuntu 24.04.4 LTS (GNU/Linux 6.8.0-137-generic x86_64)
I'll try to press enter, same error
password is not admin
for totp, i press enter
Technitium Version 15.4

[luizbizzio]

Since version 15 of technitium they changed some stuff and how the API works, your login is working, otherwise would show a different message, however it is not applying the settings correctly, by tomorrow I will finish the code and publish it under a new release

[luizbizzio]

Hi,

I found the cause of this issue.

TOTP is not the problem here. The login is working, and the error happens later when the script tries to apply the TLS certificate with settings/set.

Since Technitium v15, new Linux installations run the DNS service as a non-root user (dns-server). The script was creating the certificate with access through the certs group, but the Technitium service user was not added to this group, so it could not read the PFX file.

I reproduced the same situation on a fresh Technitium installation and confirmed the issue.

I have prepared a fix that:

Detects the real Technitium systemd service user
Adds the non-root service user to the certs group when required
Restarts Technitium only when the new group permission needs to be activated
Keeps compatibility with older Technitium installations that still run as root
Shows the real API error if settings/set fails again

This fix will be included in v1.1.1.

Thanks for reporting it.

[midosa14]

Hi, very strange, because script stops at
[✓] Technitium reachable at: http://127.0.0.1:5380
and restart server without any advice.
i'll run it 2 times, and same issue.

[luizbizzio]

Hi,

That is unexpected. At the point shown in your screenshot, the script has only detected that Technitium is reachable. It should not restart Technitium or the system there.

Could you confirm what exactly restarts?

• The whole Linux server
• Only the Technitium DNS service
• Or your SSH/session disconnects

After it happens, please run these commands and send the output:

uptime

last -x | head -20

systemctl status dns.service --no-pager

journalctl -b -1 -n 100 --no-pager

systemctl show dns.service -p User -p Group -p ExecStart

Also, please run the installer once with verbose output:

curl -fsSL https://raw.githubusercontent.com/luizbizzio/local-https/main/install.sh | sudo LOCAL_HTTPS_VERBOSE=1 bash

The screenshot stops immediately after Technitium detection, before the part of the script that changes certificate permissions or restarts Technitium, so I would like to confirm whether the whole machine is actually rebooting or if only a service/session is restarting.

[midosa14]

The whole machine is actually rebooting.
And after the reboot is very slow and some services doesn't start.

[midosa14]

I've prepared an Ubuntun VM for testing.

By the way, the reboot was on "Linux 6.18.34+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.18.34-1+rpt1 (202 6-06-09) aarch64"

Installed Technitium and then your script. This time, no reboot but an another. Run it 2 times, and same error.

I've checked, file is present in the directory /etc/ssl/servercerts.