Threat Shield DNS blacklist end with an error

It was working well on the blue interface than I activated the service on the green interface, than played with the rule and now I have this Error

Error while updating settings

The following command has failed:
nethserver-blacklist/dnss/update

Unfortunately we couldn’t catch the exact error. If you want to help, please click on the button below to copy the failed command to the clipboard, paste it into the Terminal and submit command output to the developers.

which

echo ‘{“status”:“enabled”,“Url”:“https://github.com/NethServer/dns-community-blacklist",“Bypass”:[],“Categories”:[“abuse_ch”,“adguarddns”,“phisingarmy”],“Roles”:["blue”]}’ | /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/nethserver-blacklist/dnss/update | jq

return

{
“steps”: 4,
“pid”: 27654,
“args”: “dnss”,
“event”: “nethserver-blacklist-save”
}
{
“step”: 1,
“pid”: 27654,
“action”: “S05generic_template_expand”,
“event”: “nethserver-blacklist-save”,
“state”: “running”
}
{
“progress”: “0.25”,
“time”: “0.093697”,
“exit”: 0,
“event”: “nethserver-blacklist-save”,
“state”: “done”,
“step”: 1,
“pid”: 27654,
“action”: “S05generic_template_expand”
}
{
“step”: 2,
“pid”: 27654,
“action”: “S20nethserver-blacklist-conf”,
“event”: “nethserver-blacklist-save”,
“state”: “running”
}

Remark, the error remains even if I deselect all categories and interfaces. The only successful action I could do it to disable the service

How I could fix that ?

You will find more details in /var/log/messages. Look for FAIL and/or lines in the time range close to when you played with the UI.

@filippo_carletti thanks for your replied.

sadly I saw nothing interesting in the /var/log/messages

however under cockpit :/nethserver#/services I had a new message

  • ftl : The service is either not running or not enabled

so I decided to yum remove nethserver-blacklist than yum install nethserver-blacklist
and everything is back to normal :slight_smile:

Hello;

I do that solution, but have the same problem, what I can do.?

what is your error ?
did the module ever work before the error ?