Next Batch of Updated Plugins and How to Recover from Failed Plugin Updates

Another Plugins update has been released. The updated versions are now available for new installs in the Plugins ⇾ Available section of the UI. Existing plugin installations can be updated to the new versions using the CLI instructions in this post.

Before updating a plugin, review its Release Notes in the table below to determine if the update will impact your configuration. Then, determine the jail_name for the plugin:  go to Plugins ⇾ Installed and note the name of the plugin in the Jails column.

While iocage automatically takes a snapshot before updating, it is a good habit to make your own manual snapshot before performing a plugin update. Substitute snap_name with a useful name (such as plugin name, version, and date) and jail_name with the name of the plugin in the Jails column:

iocage snapshot -n snap_name jail_name

Next, to update the plugin, type this command, replacing jail_name with the actual name shown in Plugins ⇾ Installed:

iocage update jail_name

Note that you will need to restart the plugin once the update is finished.

If you encounter issues with the updated plugin, you can rollback to the previous version of the plugin. Ensure the plugin is stopped, determine the name of the snapshot, then specify it with the rollback command:

iocage stop jail_name

iocage snaplist jail_name

iocage rollback -n snap_name jail_name

Note that rolling back will destroy all subsequent snapshots for that plugin, including any version updates and configuration changes. You should only rollback a plugin snapshot if your intent is to return the plugin to the state it was in when the snapshot was taken, such as when returning to a previously working plugin version after a failed plugin upgrade.

Plugin from to Release Notes
ClamAV 0.101.1,1 0.101.2
GitLab 11.9.6 11.10.1

Jenkins 2.171 2.174
Jenkins (LTS) 2.150.2 2.164.2
Nextcloud 15.0.5 16.0.0
Plex Media Server
Plex Media Server (plexpass)
Resilio Sync 2.6.1 2.6.3



  1. Gordon

    FYI: (As of 2019-06-27) Anybody thinking about updating FreeNAS Resilio Sync from 2.6.1 (or lower) to 2.6.3 in FreeNAS beware that FreeNAS Resilio 2.6.3 has a bug and will not sync files above 4GB – you can search and find this issue. Regular windows clients are not affected by this only the FreeNAS Resilio.

    To fix you end up rolling back 2.6.3 to 2.6.1 snapshot per this article or you can manually do it (article about Resilio above 4GB files tells you how to manually do it)

    I rolled back the snapshot to the 2.6.1 and it worked great for files above 4GB again. I guess they are going to fix the FreeNAS Resilio 2.6.3 bug for files above 4GB in next release.

    Hope this saves someone the headache.

    • Dru Lavigne


    • Martin


      If you don’t mind to open a ticket with some logs, because according to the change-log this issue was fixed in version 2.5.5


Submit a Comment

Your email address will not be published. Required fields are marked *

ESG Labs: TrueNAS Technical Report
Download Enterprise Storage Guide Button
iXsystems values privacy for all visitors. Learn more about how we use cookies and how you can control them by reading our Privacy Policy.