Last Updated on May 14, 2026 by g6nhu
These are the most common issues with HamClock and upgrading.
If these don’t resolve your problem, please email me using my address shown on qrz, ideally including a screenshot of any errors (even just a photo taken with your phone) so I can help directly.
Q1 – Can I avoid using these scripts?
A1 – Yes. From HamClock 4.24 onwards, the backend is hardcoded to OHB. If you’re using a Pi, you can quit HamClock, run ‘sudo csi’ just to switch back to the default server, reboot and re-download and run the installer as described here. It won’t even overwrite your settings. If you’re using a Quadra, download the factory reset image from here and reflash your device.
Q2 – I get an error when I use the curl command to download the tools.
A2 – This is almost always down to typing errors. Make sure you type the command exactly. It is case sensitive so ensure you use capital letters when needed. Ideally, copy and paste it.
The command is below and it’s automatically tested on a daily basis to make sure it works.
curl -fsSL https://hamclock.co.uk/tools | sudo bashQ3 – I get a certificate error when I try and upgrade my HamClock past version 4.22
A3 – If you’re using a Quadra, you may have used the provided utility under the Ham Apps Installer to switch to OHB. That doesn’t do a full switch. The fix is to use the scripts described here.
If you’re using a Pi, you may have installed the scripts and switched before the upgrade mechanism was fully understood. Exit HamClock, download the scripts again and switch again using these three commands:
curl -fsSL https://hamclock.co.uk/tools | sudo bash
sudo csi
sudo ohbQ4 – When I type the sudo password, nothing shows
A4 – This is correct, passwords are not echoed to the screen for security reasons. Just type it and then press the enter/return key.
Q5- Show me a video of how to switch.
A5
