Migrate from our Strict Confinement to our new Classic Confinement
v3.3.20 This version will contain information on how to migrate to our classic confinement for our next release.
v3.3.21 This version and higher will require classic confinement in order to be installed.
You'll need to migrate from Strict to Classic confinement if you're experiencing issues within our app, this includes issues such as:
- Accessing directories such as:
- Network drives
- root directories or any directories outside your home folder
- Soft-linked / hard linked directories
- Hidden directories / files (e.g.
- Local directory not displaying files / folders
- Permission errors showing in message log whilst: (local directory only)
- Modifying / saving files
- Downloading / uploading files or directories
- Creating, renaming or deleting a file or directory
- Editing files not showing contents or status showing "Loading File" and never completing
If you've never installed sFTP Client before and have installed the latest version v3.3.21 or higher you will already have the classic confinement and will not need to migrate.
In order to migrate to our classic confinement (from our strict confinement), you'll need to open the terminal and follow the steps below:
- 1.If you do not have syncing enabled, please first backup your connections / data.
- 2.Run the command
snap remove sftpclientto remove the strict version of our app.
- 3.Re-install the app by running
snap install sftpclient --classic --candidateto install the classic version of our app.
- 4.Restore your backup if necessary, if your saved connections no longer show when opening the app please use the backup you created earlier to restore them.
Used by the majority of snaps. Strictly confined snaps run in complete isolation, and consequently, can not access your files, network, processes or any other system resource without requesting specific access via an interface. This is the default for every app and is done so to protect your system from malicious apps.
Allows access to your system’s resources in much the same way traditional packages do. To safeguard against abuse, publishing a classic snap requires approval, and the installation process requires the
--classiccommand line argument (as detailed in "How do i migrate?").