CORE 13.0-U5.3 - Transmission jail won't update from 3.00_5 to 4.0.4

[zmeul]

Error: pkg error: - transmission-web : Refusing to fetch artifact and run post_install.sh!

if I try to create a new Transmission 4.0.4 jail I'll get the same error

full log, if needed, when running iocage update transmission from shell :

Show : log

Snapshot: Seagate_1Tb/iocage/jails/transmission@ioc_update_13.1-RELEASE-p9_2023-09-16_05-58-18 created.
Updating plugin...
Snapshotting transmission...
Snapshot already exists
Updating plugin INDEX...
Updating plugin artifact...
Cloning git repository

Branch 13.1-RELEASE does not exist at https://github.com/freenas/iocage-plugin-transmission.git!
Using "master" branch for plugin, this may not work with your RELEASE
Removing old pkgs...
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 18 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
ca_root_nss: 3.92
curl: 8.2.1
dht: 0.27
gettext-runtime: 0.22_1
indexinfo: 0.3.1
libb64: 1.2.1
libevent: 2.1.12
libidn2: 2.3.4
libnatpmp: 20220122_2
libnghttp2: 1.55.1_1
libpsl: 0.21.2_3
libssh2: 1.11.0,3
libunistring: 1.1
libutp: g20180515
miniupnpc: 2.2.5
pkg: 1.20.5
transmission-daemon: 3.00_5
transmission-web: 3.00_1

Number of packages to be removed: 18

The operation will free 51 MiB.
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
[transmission] [1/18] Deinstalling transmission-daemon-3.00_5...
[transmission] [1/18] Deleting files for transmission-daemon-3.00_5: .......... done
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
==> You should manually remove the "transmission" user.
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
==> You should manually remove the "transmission" group
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
[transmission] [2/18] Deinstalling curl-8.2.1...
[transmission] [2/18] Deleting files for curl-8.2.1: .......... done
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
[transmission] [3/18] Deinstalling libpsl-0.21.2_3...
[transmission] [3/18] Deleting files for libpsl-0.21.2_3: .......... done
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
[transmission] [4/18] Deinstalling libidn2-2.3.4...
[transmission] [4/18] Deleting files for libidn2-2.3.4: .......... done
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
[transmission] [5/18] Deinstalling gettext-runtime-0.22_1...
[transmission] [5/18] Deleting files for gettext-runtime-0.22_1: .......... done
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
[transmission] [6/18] Deinstalling libunistring-1.1...
[transmission] [6/18] Deleting files for libunistring-1.1: .......... done
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
[transmission] [7/18] Deinstalling ca_root_nss-3.92...
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [7/18] Deleting files for ca_root_nss-3.92: .
[transmission] [7/18] Deleting files for ca_root_nss-3.92....
[transmission] [7/18] Deleting files for ca_root_nss-3.92........ done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [8/18] Deinstalling dht-0.27...
[transmission] [8/18] Deleting files for dht-0.27: ........ done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [9/18] Deinstalling indexinfo-0.3.1...
[transmission] [9/18] Deleting files for indexinfo-0.3.1: .... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [10/18] Deinstalling libb64-1.2.1...
[transmission] [10/18] Deleting files for libb64-1.2.1: ....... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [11/18] Deinstalling libevent-2.1.12...
[transmission] [11/18] Deleting files for libevent-2.1.12: .......... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [12/18] Deinstalling libnatpmp-20220122_2...
[transmission] [12/18] Deleting files for libnatpmp-20220122_2: .......... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [13/18] Deinstalling libnghttp2-1.55.1_1...
[transmission] [13/18] Deleting files for libnghttp2-1.55.1_1: .......... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [14/18] Deinstalling libssh2-1.11.0,3...
[transmission] [14/18] Deleting files for libssh2-1.11.0,3: .......... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [15/18] Deinstalling libutp-g20180515...
[transmission] [15/18] Deleting files for libutp-g20180515: ...... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [16/18] Deinstalling miniupnpc-2.2.5...
[transmission] [16/18] Deleting files for miniupnpc-2.2.5: .......... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [17/18] Deinstalling pkg-1.20.5...
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [17/18] Deleting files for pkg-1.20.5: .......... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
[transmission] [18/18] Deinstalling transmission-web-3.00_1...
[transmission] [18/18] Deleting files for transmission-web-3.00_1: .......... done
ca_root_nss-3.92: missing file /usr/local/etc/ssl/cert.pem
ca_root_nss-3.92: missing file /usr/local/openssl/cert.pem
Installing new pkgs...
Repo: iocage-plugins already exists, skipping!

Testing Host DNS response to pkg.FreeBSD.org
Testing transmission's SRV response to pkg.FreeBSD.org
Testing transmission's DNSSEC response to pkg.FreeBSD.org

Installing plugin packages:
- transmission-daemon...
- transmission-web...
- transmission-web failed to install, retry #1
- transmission-web failed to install, retry #2
- transmission-web failed to install, retry #3

pkg error:
- transmission-web :

Refusing to fetch artifact and run post_install.sh!
PKG error, update failed! Rolling back snapshot.

 

[winnielinnie]

Don't use plugins. Switch to manually created jails (with "installer scripts" if relevant).

Secondly, FreeBSD 13.1 is EOL. You need to fetch and upgrade your jail to 13.2.

 

[zmeul]

Secondly, FreeBSD 13.1 is EOL. You need to fetch and upgrade your jail to 13.2.

it won't do it

I ran sudo iocage fetch, selected 13.2-RELEASE, then sudo iocage upgrade -r 13.2-RELEASE transmission and I get the same error

and if I try to create a brand new Transmission 4.0.4 jail I'll get the same error

 

[winnielinnie]

and if I try to create a brand new Transmission 4.0.4 jail I'll get the same error

Creating a new vanilla jail or Plugin?


Use Basejail when prompted, as they're much less of a headache to upgrade; they don't require the original release to remain indefinitely.


What is the output of:

Code:

iocage list -l

 

[zmeul]

What is the output of:

Code:

iocage list -l

Code:

+-----+--------------+------+-------+----------+-----------------+---------------------+-----+----------+----------+
| JID |     NAME     | BOOT | STATE |   TYPE   |     RELEASE     |         IP4         | IP6 | TEMPLATE | BASEJAIL |
+=====+==============+======+=======+==========+=================+=====================+=====+==========+==========+
| 15  | transmission | on   | up    | pluginv2 | 13.1-RELEASE-p9 | vnet0|172.16.0.2/30 | -   | -        | yes      |
+-----+--------------+------+-------+----------+-----------------+---------------------+-----+----------+----------+

 

[winnielinnie]

It's a "plugin". Unfortunately, they are deprecated.

Going forward, you'll have to create and configure a manual jail (Basejail), install the relevant packages (with "pkg"), and config the settings / services.

From this point onwards you can occasionally update your packages ("pkg"), less often update the patch level ("p1, p2, p3, etc"), and on rare occasion upgrade the underlying FreeBSD release ("13.3, 13.4, 14.1, etc").

 

[zmeul]

It's a "plugin". Unfortunately, they are deprecated.

Going forward, you'll have to create and configure a manual jail (Basejail), install the relevant packages (with "pkg"), and config the settings / services.

From this point onwards you can occasionally update your packages ("pkg"), less often update the patch level ("p1, p2, p3, etc"), and even more less often upgrade the underlying FreeBSD release ("13.3, 13.4, 14.1, etc").

that's too much for me to undertake from scratch, not that I may not do it but I may not do it properly and I'll end up with something borked

if it somehow sorts itself out with 14 release or if I have to install it fresh, I think I'll leave it as is .. unless it will stop working and I'll be forced to do something about it

tanks for your time

 

[winnielinnie]

that's too much for me to undertake from scratch, not that I may not do it but I may not do it properly and I'll end up with something borked

Understood, but to "pull back the curtain", this is what using the "Plugin" essentially is, except for the initial setup and ongoing upgrades/maintenance.

You obviously had to configure mountpoints, permissions, and Transmission settings after installing the Plugin. Yes?

The last time the plugin was updated was over a year ago. If you look inside its post-installer script, you'll see that it doesn't actually do that much. It's trivial enough to run it yourself in a newly created vanilla jail:



Initial "Plugin" creation:

Code:

{
    "name": "Transmission",
    "release": "13.1-RELEASE",
    "artifact": "https://github.com/freenas/iocage-plugin-transmission.git",
    "official": false,
    "properties": {
        "nat": 1,
        "nat_forwards": "tcp(9091:9091)"
    },
    "pkgs": [
        "transmission-daemon",
        "transmission-web"
    ],
    "packagesite": "http://pkg.FreeBSD.org/${ABI}/latest",
    "fingerprints": {
        "iocage-plugins": [
            {
                "function": "sha256",
                "fingerprint": "b0170035af3acc5f3f3ae1859dc717101b4e6c1d0a794ad554928ca0cbb2f438"
            }
        ]
    },
    "revision": 0
}

To do the above yourself manually:

1. Create a new jail (Basejail, not Clone jail) based on FreeBSD 13.2
2. Use DHCP or a static IP (your preference); forward ports on your router if desired; etc.
3. Inside the jail, switch to the "latest" repository (thanks @Patrick M. Hausen)
   • mkdir -p /usr/local/etc/pkg/repos
   • echo 'FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest" }' >/usr/local/etc/pkg/repos/FreeBSD.conf
4. Inside the jail, use the pkg command to install the package transmission-daemon
   • pkg update -f
   • pkg install transmission-daemon

That's basically it. Your Transmission jail has now been created, based on FreeBSD 13.2.




Here is the "post install" stuff that the "Plugin" does:

Code:

#!/bin/sh
sysrc -f /etc/rc.conf transmission_enable="YES"
sysrc -f /etc/rc.conf transmission_download_dir="/usr/local/etc/transmission/home/Downloads"
# Start service once to create the files needed
service transmission start
sleep 2 # It can take a few seconds.

# Without the whitelist disabled, the user will not be able to access it. They can reenable and manually whitelist their IP's.
SETTINGS="/usr/local/etc/transmission/home/settings.json"

echo "Disabling RPC whitelist, you may want to reenable it with the specific IP's you will access transmission with by editing $SETTINGS"
sed -i '' -e 's/\([[:space:]]*"rpc-whitelist-enabled":[[:space:]]*\)true,/\1false,/' $SETTINGS

#Create a Download Directory
mkdir -p /usr/local/etc/transmission/home/Downloads
chmod 755 /usr/local/etc/transmission/home/Downloads

# Start the service
service transmission reload

To do the above yourself manually, first enter the jail, and then literally just execute the above script. Done. (As the root user when you enter the jail, create a new file called post_install.sh, run it, done.)



Congratulations, you now have a fully operable and manageable Transmission jail based on FreeBSD 13.2, without relying on the deprecated "Plugins" system.

Anything else? You have to configure mountpoints, permissions, and Transmission yourself, which is no different than when you use a "Plugin".




How do you "maintain" and "update" this jail?

1. Once in a while, inside the jail run pkg update -f && pkg upgrade to update any installed packages to the latest versions.
   • Optionally: Use pkg clean -a to clean the package cache to keep your jail lean (saves space)
2. Less often from the TrueNAS "Jails" page, you can "update" the jail if there's a "patch" available for FreeBSD 13.2
   • Hint: The Jail GUI "Update" button is equivalent to using the iocage update command
3. Rarely you'll need to upgrade the FreeBSD release using iocage fetch and iocage upgrade

 

[Alecmascot]

No Transmission V4 in pkg yet though it is in Freshports....

 

[Patrick M. Hausen]

No Transmission V4 in pkg yet though it is in Freshports....

I am not familiar with Transmission but the transmission-gtk and the transmission-cli packages are available as version 4.0.4 for FreeBSD 13 - which you can verify on Freshports.

You will need to switch your package repo from quarterly to latest in your jail to install that package:

Code:

mkdir -p /usr/local/etc/pkg/repos
echo 'FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest" }' >/usr/local/etc/pkg/repos/FreeBSD.conf

 

[Alecmascot]

I am not familiar with Transmission but the transmission-gtk and the transmission-cli packages are available as version 4.0.4 for FreeBSD 13 - which you can verify on Freshports.

You will need to switch your package repo from quarterly to latest in your jail to install that package:

Code:

mkdir -p /usr/local/etc/pkg/repos
echo 'FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest" }' >/usr/local/etc/pkg/repos/FreeBSD.conf

Thanks. Got the updated transmission-daemon now

 

[winnielinnie]

You will need to switch your package repo from quarterly to latest in your jail to install that package:

Good reminder!

I've edited my post to include this important step!

 

[winnielinnie]

@zmeul in case you're still interested: I've updated my post to include an important step shared by @Patrick M. Hausen.

(Switching to the "latest" repository will land you up-to-date software versions, such as Transmission 4.0, rather than arbitrarily waiting for the "quarterly" repository to catch up every few months.)

EDIT: For what it's worth, I got a Transmission (4.0.4) jail up and running (using the above steps) in less than a couple minutes. (I've since destroyed it, because I use qBittorrent anyways.)

 

[zmeul]

@zmeul in case you're still interested: I've updated my post to include an important step shared by @Patrick M. Hausen.

(Switching to the "latest" repository will land you up-to-date software versions, such as Transmission 4.0, rather than arbitrarily waiting for the "quarterly" repository to catch up every few months.)

EDIT: For what it's worth, I got a Transmission (4.0.4) jail up and running (using the above steps) in less than a couple minutes. (I've since destroyed it, because I use qBittorrent anyways.)

yes, I got it up and running but with some tweaks of my own
I didn't want to do it again since I knew it was pain when I 1st configured it and I had to use VIM ... oh god!
now I installed nano and modded the settings.json to my needs - so far so good, seems to be working

ps: the script, ./post_install.sh would absolutely not run, it would say permission denied or something like that, so I had to execute each command manually

 

[Patrick M. Hausen]

Code:

sh ./post_install.sh

# or

chmod +x ./post_install.sh
./post_install.sh

 

[zmeul]

Code:

sh ./post_install.sh

# or

chmod +x ./post_install.sh
./post_install.sh

well ... I'm not that accustomed to the BSD way of doing things, way too much Linux for me

now I know

 

[Patrick M. Hausen]

Linux behaves exactly the same in that regard. If you don't set the "executable" bit, you get a "permission denied".

 

[zmeul]

Linux behaves exactly the same in that regard. If you don't set the "executable" bit, you get a "permission denied".

absolutely, but in LINUX I use sudo ./install.sh, not sh ./install.sh
there are many things I still don't know, learning as I go

 

[Patrick M. Hausen]

sudo if you are not already root. With sh somefile you can have the shell interpret the file as a script even when the execute bit is NOT set. Again same in Linux. And you probably got into your jail with iocage console, so you are root, so no sudo.

 

[zmeul]

sudo if you are not already root. With sh somefile you can have the shell interpret the file as a script even when the execute bit is NOT set. Again same in Linux. And you probably got into your jail with iocage console, so you are root, so no sudo.

I'm telling you it didn't want to do it, and using sudo inside the iocage console returned unknown command