starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Updating Technitium 1. Performs unessasary update 2. doesn't restart the application #2205

New Issue
Closed
opened 2026-02-05 04:12:26 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 04:12:26 +03:00
Owner
Copy Link

Originally created by @DrEVILish on GitHub (Dec 20, 2025).

📌 Task summary

Technitium update script

📋 Task details

Technitium LXC - Debian 13
When running the /bin/update command.
2 Issues but all for the same update script

  1. Even if you're running the latest release and just ran the update script. It always performs the update and never triggers
    msg_ok "No update required. Technitium DNS is already at v${RELEASE}."

so each time I get

...
runtimes/win/lib/net6.0/Microsoft.Win32.SystemEvents.dll
runtimes/win/lib/net6.0/System.Drawing.Common.dll
  ✔️   Updated Technitium DNS
  ✔️   Updated successfully!

Ran both Verbose and Silent modes.

Update script seems to check for release in ~/.technitium but never updates it to the new release version.

  if [[ ! -f ~/.technitium || "${RELEASE}" != "$(cat ~/.technitium)" ]]; then
    msg_info "Updating Technitium DNS"
    curl -fsSL "https://download.technitium.com/dns/DnsServerPortable.tar.gz" -o /opt/DnsServerPortable.tar.gz
    $STD tar zxvf /opt/DnsServerPortable.tar.gz -C /opt/technitium/dns/
    rm -f /opt/DnsServerPortable.tar.gz
    msg_ok "Updated Technitium DNS"
    msg_ok "Updated successfully!"
  else
    msg_ok "No update required.  Technitium DNS is already at v${RELEASE}."
  fi
  1. The Technitum service is never restarted after the update, so even when the update has finished, it is still running the previous version until the service or container is restarted manually by the user.

WebUI : Technitium DNS Server Version 14.2 -> New Update (14.3) Available!

Originally created by @DrEVILish on GitHub (Dec 20, 2025). ### 📌 Task summary Technitium update script ### 📋 Task details Technitium LXC - Debian 13 When running the /bin/update command. 2 Issues but all for the same update script 1. Even if you're running the latest release and just ran the update script. It always performs the update and never triggers `msg_ok "No update required. Technitium DNS is already at v${RELEASE}."` so each time I get ``` ... runtimes/win/lib/net6.0/Microsoft.Win32.SystemEvents.dll runtimes/win/lib/net6.0/System.Drawing.Common.dll ✔️ Updated Technitium DNS ✔️ Updated successfully! ``` Ran both Verbose and Silent modes. Update script seems to check for release in ~/.technitium but never updates it to the new release version. ```RELEASE=$(curl -fsSL https://technitium.com/dns/ | grep -oP 'Version \K[\d.]+') if [[ ! -f ~/.technitium || "${RELEASE}" != "$(cat ~/.technitium)" ]]; then msg_info "Updating Technitium DNS" curl -fsSL "https://download.technitium.com/dns/DnsServerPortable.tar.gz" -o /opt/DnsServerPortable.tar.gz $STD tar zxvf /opt/DnsServerPortable.tar.gz -C /opt/technitium/dns/ rm -f /opt/DnsServerPortable.tar.gz msg_ok "Updated Technitium DNS" msg_ok "Updated successfully!" else msg_ok "No update required. Technitium DNS is already at v${RELEASE}." fi ``` 2. The Technitum service is never restarted after the update, so even when the update has finished, it is still running the previous version until the service or container is restarted manually by the user. WebUI : Technitium DNS Server Version 14.2 -> New Update (14.3) Available!
OVERLORD commented 2026-02-05 04:12:36 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 20, 2025):

Screenshots? Why an Task?

@MickLesk commented on GitHub (Dec 20, 2025): Screenshots? Why an Task?
OVERLORD commented 2026-02-05 04:12:39 +03:00
Author
Owner
Copy Link

@DrEVILish commented on GitHub (Dec 21, 2025):

As I didn't feel it was an Installation BUG it didn't seem to fit with the current "Script Issue", appologise.
I'm generating a PR atm, with the fixes.

@DrEVILish commented on GitHub (Dec 21, 2025): As I didn't feel it was an Installation BUG it didn't seem to fit with the current "Script Issue", appologise. I'm generating a PR atm, with the fixes.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2205
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?