How a wrong clock bricked a reMarkable 2 — and the SSH fix that revived it

A reMarkable 2 e-paper tablet left unused since 2021 refused to sync (a cryptic ‘error 0’) or update. The root cause was a badly drifted system clock, which blocks reMarkable’s software updater — a failure mode the company also documents officially. SSHing into the device over USB and correcting the date with timedatectl (disabling NTP first, then re-enabling it) immediately unblocked the first update.

Recovery took several more hops. The initial update only reached firmware 3.11.2.5, and the cloud then rejected the device as too old. The updater had also silently failed after a reboot because it launched before Wi-Fi and DNS were ready and never retried; restarting swupdate.service and update-engine.service surfaced the next version and eventually pulled the tablet up to current firmware. Notably, since version 3.22 reMarkable silently disables SSH over Wi-Fi, so port 22 only answers over the USB link unless you re-enable it with rm-ssh-over-wlan or a marker file.

Cloud sync never fully recovered, so the author sidestepped it entirely by enabling the tablet’s built-in web interface (WebInterfaceEnabled=true, also toggleable in Settings) and pushing PDFs over USB with curl. The takeaway for anyone with a long-dormant device: check the clock before assuming the hardware or account is dead, and know that vendor firmware updates can quietly remove local access paths you previously relied on.