Community Solution

ZimaOS Update Not Appearing: Automatic Update, Network Checks, and Command-Line Fallback

An October 2025 thread where several ZimaOS 1.4.3 users did not receive the 1.5 update prompt. Community troubleshooting checked DNS and network filtering; one user could not download the release at first but later updated successfully with the official OTA command-line updater.

When a new ZimaOS release exists but your server still shows the old version, the missing button does not automatically mean the installation is broken. The October 2025 source thread involved users stuck on 1.4.3 while waiting for 1.5, and the discussion moved through DNS filtering, Internet access, direct-download failures, and finally the official command-line OTA updater.

Version 1.5 is historical now, but the troubleshooting logic remains useful: automatic update is the recommended path, network filtering can prevent update metadata or packages from downloading, and IceWhale provides a command-line fallback for cases where the normal update workflow fails.

Automatic Upgrade Is the Recommended Method

IceWhale's official installation and upgrade tutorial describes automatic upgrade as the simplest and safest method. ZimaOS downloads the package in the background and shows a notification in Settings after the update is ready.

That means users do not necessarily see an upgrade button the moment a release announcement appears.

Check Connectivity Before Assuming the OTA System Is Broken

In the source thread, community members asked whether Pi-hole, AdGuard Home, NextDNS, firewall rules, or custom DNS could be blocking the update service. One user removed custom DNS and even tested a DMZ configuration without success.

Those negative tests are useful because they show that “check DNS” is a diagnostic branch, not a guaranteed solution.

One User Could Not Download the Release Even Outside the UI

A later participant tried the command-line updater and received a download failure. They also tried downloading directly from IceWhale's GitHub release page and saw extremely slow transfer behavior.

That evidence pointed more strongly toward a connectivity or delivery-path problem than a missing Settings button alone.

IceWhale Provides an Official Command-Line Upgrade Path

The official Zima-Giorgio upgrade tutorial now documents this fallback for cases where automatic upgrade fails:

sudo -i
curl -fsSL 'https://ota.zimaos.com/' | sh

When no version is specified, the script selects the latest release according to the current update channel. IceWhale also documents version-specific URLs for deliberate upgrade or downgrade operations.

Review the official ZimaOS installation and upgrade procedure before forcing an update from a historical forum snippet.

The Source User Ultimately Updated with the OTA Script

On October 25, the participant who had been unable to download the release returned and said the generic OTA command successfully updated their system to ZimaOS 1.5.

That is a confirmed source outcome. It does not prove why the graphical notification had failed to appear.

The Beta Channel Is for Testing, Not a Fix for Every Missing Stable Update

Developer Mode can switch ZimaOS to the Beta update channel. That is useful when you intentionally want pre-release builds. It should not be enabled merely because a stable rollout seems slow.

The official tutorial keeps automatic stable upgrade as the recommended default.

Treat Remote Update Scripts as Privileged System Operations

The OTA command downloads and executes a script as root. Use only the official IceWhale OTA domain, confirm the server has stable power and networking, and back up important data before a forced version change.

Do Not Force the Historical 1.5.0 URL on a Current Server

The source thread was specifically about moving from 1.4.3 to 1.5 in October 2025. Current ZimaOS has advanced well beyond that release. A version-pinned 1.5 command belongs to the historical context, not a current upgrade recommendation.

ZimaOS Update FAQ

Should every new release appear immediately on every server?

Not necessarily. Automatic delivery and package download timing can differ from the public announcement.

Can DNS filtering block updates?

It can interfere with update endpoints, so it is a reasonable check, but the source users did not solve their case simply by changing DNS.

Is there an official CLI updater?

Yes. IceWhale's official upgrade tutorial documents the OTA script as a fallback when automatic upgrade fails.