I get the ‘Unable to write public key file’ error I get the ‘Unable to write public key file’ error

I get the ‘Unable to write public key file’ error

Dmitry Machulo Dmitry Machulo

The 'Unable to write public key file' error may occur when one connects to a host on an iOS / iPadOS device after restoring a backup or direct data transfer between two devices. The error will occur if the key that was used to connect to that host was not restored or transferred. Keys, passwords and passphrases are not included or can't be restored from unsupported backup types, and they can't be transferred between two devices of different type.

After you restore an unsupported backup or transfer data between two devices of not the same type, the following fields will be empty: 'Password' (part of host entries, identities, proxy), 'Passphrase' and 'Private' (both parts of a key entry).

This problem can be fixed by readding the keys, passwords and passphrases or, if you’ve been a subscriber, by reloading your data from the servers of Termius. Reloading data means deleting all locally stored data and downloading the data from the cloud (i.e. data that was synchronized).

⚠️ If some of your data hasn’t been synchronised, you’ll lose it if you reload data. For example, it may happen if you recently canceled your subscription and some changes that you made since then haven’t been synchronized.

To redownload the data, tap your e-mail displayed on the main app screen and then tap Reload data.

IMG_EA5A9A935241-1.jpeg

Supported backup types

An encrypted backup made on a computer should let someone transfer all data to the same type of device (between two iPhones or iPads). If that backup is restored on a device of a different type, keys, passwords and passphrases won't be restored. A non-encrypted backup made on a computer doesn't include this data.

An iCloud backup made on a phone will let someone transfer all data to the same device. However, if that backup is restored on a different device, keys, passwords and passphrases won't be restored.

Add comment

Please sign in to leave a comment.