Exception: KeyError:'adminportal' occured, destroyed fail2ban.

[sonnius]

As per the title, I get the above error when using the plugin on FreeNas:

rob@becks:~/iocage-plugin-fail2ban % sudo iocage fetch -P -n fail2ban.json ip4_addr="em0|192.168.20.200/24"
Plugin: Fail2Ban
Official Plugin: False
Using RELEASE: 11.2-RELEASE
Using Branch: 11.2-RELEASE
Post-install Artifact: .
These pkgs will be installed:
- python36
- vim-tiny
- bash
- security/py-fail2ban

Testing SRV response to iocage-plugins
Testing DNSSEC response to iocage-plugins

Installing plugin packages:

• python36...
• vim-tiny...
• bash...
• security/py-fail2ban...

Fetching artifact...

Branch 11.2-RELEASE does not exist at .!
Using "master" branch for plugin, this may not work with your RELEASE

Running post_install.sh

Command output:
Updating iocage-plugins repository catalogue...
iocage-plugins repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): . done
Processing candidates (0 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Updating iocage-plugins repository catalogue...
iocage-plugins repository is up to date.
All repositories are up to date.
Checking integrity... done (1 conflicting)

• py36-fail2ban-0.10.4 conflicts with py27-fail2ban-0.10.4 on /usr/local/man/man1/fail2ban-client.1.gz
  Checking integrity... done (0 conflicting)
  The following 2 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
py27-fail2ban-0.10.4

New packages to be INSTALLED:
py36-fail2ban: 0.10.4

Number of packages to be removed: 1
Number of packages to be installed: 1
[fail2ban] [1/2] Deinstalling py27-fail2ban-0.10.4...
[fail2ban] [1/2] Deleting files for py27-fail2ban-0.10.4:
[fail2ban] [1/2] Deleting files for py27-fail2ban-0.10.4............. done
[fail2ban] [2/2] Installing py36-fail2ban-0.10.4...
[fail2ban] [2/2] Extracting py36-fail2ban-0.10.4: .......... done
Message from py36-fail2ban-0.10.4:

---

Please do not edit the fail2ban.conf, jail.conf, or any other
files in the distributen as they will be overwritten upon each
upgrade of the port. Instead, create new files named *.local e.g.
fail2ban.local or jail.local.

For more information, see the official manual:
http://www.fail2ban.org/wiki/index.php/MANUAL_0_8#Configuration

If you have custom filters or actions and you are upgrading from
0.9.x please check them.

Users of pf: please read the notes in action.d/pf.conf and the
discussion at fail2ban/fail2ban#1925
Please note that fail2ban will put curly braces '{}' around the
ports in the action so you shouldn't do it yourself.

---

fail2ban_enable: -> YES
Server ready

Exception: KeyError:'adminportal' occured, destroyed fail2ban.
rob@becks:~/iocage-plugin-fail2ban % uname -a
FreeBSD becks.local 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+3b66a34f3aa(HEAD): Thu Feb 14 13:40:20 EST 2019 root@nemesis.tn.ixsystems.com:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64
r

[voltechs]

Hi @sonnius,

Thanks for reporting this! I can't get to my FreeNAS box easily at the moment, but I think I know what the issue is.

Can you modify the ui.json file to read:

{
	"adminportal": ""
}

I think that should fix the issue. Report back and we'll go from there.