All guides and articles

Practical SSH guides, troubleshooting, comparisons and Server Manager news.

SSH client for Windows, macOS and Linux

Connect to a Linux server with an SSH profile, verify its host key and work in the CH-J Server Manager terminal.

Transfer and edit remote files over SSH using File Manager with save conflict detection.

Check the actual HTTP protocol with the bundled client and inspect TLS 1.2/1.3.

Calculate local checksums, compare files or verify an expected SHA-512 or BLAKE3 digest.

Inspect CPU, RAM, swap, filesystems, uptime and network interfaces with the System Monitor plugin.

Before running an installer, check its OpenPGP signature, key fingerprint and complete SHA-512 checksum.

Set up the signed CH-J Alpha repository on Ubuntu 24.04 amd64 and install Server Manager with APT.

Version 0.1.1 moves to Rust and Tauri 2. Discover the architectural benefits behind the next desktop generation.

What the Rust and Tauri transition means for existing users, profiles and the encrypted vault.

Compare terminal access, file transfers and administration workflows, including the strengths and limits of both tools.

Identify whether SSH fails at the port, network or authentication stage before changing server configuration.

Choose a compatible key, protect its private half and test the new login before removing the old access method.

Check the Windows feature, start SSH, restrict network access and verify the host key before connecting.

Reach internal servers through one or more jump hosts, verify every host key and avoid forwarding your agent.

Copy files between two remote servers through your own computer, handle conflicts and verify the result with SHA-256.

Measured package size, disk space, RAM and CPU on macOS, Windows and Ubuntu, including where Alpha 0.1.1 is currently worse.

After enlarging a virtual disk, extend the partition, LVM and the ext4 or XFS file system in the right order.

Check memory use, create a swap file, make it persistent and resize it safely, with notes on Btrfs and zram.

Back up the configuration, test it with nginx -t, apply it with a graceful reload and roll back when something fails.

Keep several servers organised with SSH aliases and side-by-side terminals, and avoid running a command on the wrong one.