Andreas Schnederle-Wagner

anyone got a solution to this?

@aldy505 - as we operate all our Servers on RHEL based Servers we would like to stay within this universe, if possible. Just tried to install same Sentry Version (23.7.2)...

update: after running /var/www/sentry/self-hosted/scripts/reset.sh and another fresh install the installation went through completely ... but then when I tried to fire it up: ``` # docker compose up -d [+]...

further update: ``` chmod 777 self-hosted cd self-hosted # chmod 777 /var/www/sentry/self-hosted/postgres/postgres-entrypoint.sh # chmod 777 /var/www/sentry/self-hosted/postgres/init_hba.sh # chmod 777 /var/www/sentry/self-hosted/sentry/entrypoint.sh ``` Then the 'Error response from daemon: failed to create...

@aldy505 never worked with Debian so far - but yea - could create a Debian Machine and try. I guess it should work there when it's tested on Debian ^^...

@thmull / @adewes - by any chance - do you maybe have an idea on how to tackle this problem? thx, bye from Tirol Andy

Hey @adewes, thank you for your fast answer. We are aware of these 2 options. However, unfortunately, they do not allow us to configure this scenario. - The Matomo script...

I must contradict here ... We are a Hosting Prodiver using fail2ban on our Shared Hosting Servers (next to Customer VHosts, ...). Very often we need to put Customer IPs...

IPs which I add through "fail2ban-client addignoreip" getting always purged when fail2ban Service is reloaded - not persistant?

@sebres - of course that's a nice approach - but unfortunately not flexible enough for Hosting Providers. Often Customer tells our Support Staff that Technician is coming in X Days...