Roxedus

So the regex is working, the only thing is that f2b doesn't start

Test the failregex on the command line fail2ban-regex /bitwarden/bitwarden.log /config/fail2ban/filter.d/bitwardenrs.local

Ok, that logline indicates that f2b doesnt start afaik. I dont have any default banaction, but i imagine defining the same action twice isnt optimal

What does your jail look like?

The bitwarden filter that comes with fail2ban is not for bitwarden_rs. You need to create a new file, and use the correct failregex. This is the filter I use. As noted you have to call it something else than bitwarden.conf, i called it bitwarden_rs.conf

The missing link tends to show when you use a registry thats not dockerhub

Don't add && between the packages

You can use this method to install ipmitools and the sensors at startup, this way you can get auto-updates for telegraf. https://selfhosters.net/docker/telegraf/ipmi/

My deemix still works @PaDadof2

@m4gicfour Thanks, should be updated now.

[mention]Squid [/mention] has there been some changes regarding the dropdown logic?

I kept the beta tag since I no longer actively use the software, but I still maintain the image, for the times I do use it.

Great show

It does.

Share the errors...

Despite the name change, it is for Organizr V2. Migration should be very easy, just replace the repository field to organizr/organizr. If you used another tag, see the migration note on how the get the same result. Support thread for the Official container for Organizr V2 DockerHub: https://hub.docker.com/r/organizr/organizr/ GitHub: https://github.com/Organizr/docker-organizr Discord: https://organizr.app/discord

The bwdata is the appdata folder.

Only on buildtime, not runtime. A new image is now built, with the 5.0.1 version

Using radarr 3?

The password is hashed in the settings.json, your best bet is to reach out to the developers on github or trough discord

You need to add a variable with the key `OOKLA_EULA_GDPR` and set it to `true`. The i updated the template to account for this now.

wonder if it is your custom network doing some funky stuff, does it work with the default bridge?

Can you do post a screenshot of the settings for the container?

Yes, it is still working. Does the container log say "starting services"? Are you using the new port "6595"?

We have atleast 15 templates that are set up like this, and this is the first time i have heard it is being a "problem"