Diagnostics → Services → Fail2ban : Error "Invalid RPC response. Please check the syslog for more information"

Hello,

After creating my shares, some docker container (setting up docker/docker compose is not as simple as it seems, especially when I need to put all the files etc... in a folder inside the OMV install disk), I continue to discover OMV.

Today I go to the Diagnostics → Services → Fail2ban panel, and there I get an error:

"Invalid RPC response. Please check the syslog for more information"

How can I fix this?

I don't see a similar message elsewhere.

Thanks in advance,

Have a nice day.

Quote from ryecoaaron

You should start a new thread for this. Not knowing what you are doing, it is hard to recommend an easier way of doing what you are doing.

You’re right but the meaning of my words was to state what I’ve done with difficulty. I manage to do what’s necessary to get docker compose to work. I deployed Arcane-Agent and with I deployed Scrutiny. Some other containers will follow.

But that indeed not the purpose of this thread.

Quote from ryecoaaron

What did you do to get to that error? The error isn't helpful. Have you refreshed your browser cache? ctrl-shift-R Did you just install the plugin? Did you configure the plugin

I didn’t do anything, really.

After installing OMV , I installed severals plugins included openmediavault-fail2ban 8.0.

I came across the Fail2ban panel page by chance, during my discoveries of OMV.

And I assume something doesn’t works properly if I get this error.

Quote from ryecoaaron

I just realized I misread where you were getting the error. I missed the diagnostics part.

It really isn't an important part of the plugin until you have configured the plugin. Did you enable the plugin?

Ho! I don't enable Fail2ban I think 😅
I'll try to enable it, and the see there.

Thank you

Indeed, I had to enable Fail2ban, and then enable some jails, and now, in Diagnostics → Services → Fail2ban panel, I don't have anymore an error, but now the list of the jails enabled and stats of banned ip (0 for now).