#fail2ban — Public Fediverse posts

🔗 https://ricard.dev/fail2ban-jail-to-block-http-probing/

#linux #fail2ban

Ricard Torres 👨‍💻 @[email protected] · 2026-08-22 · 20:53 UTC

"fail2ban jail to block HTTP probing"

I’ve hardened my VPS with fail2ban to stop WordPress brute‑force attacks, but a recent traffic spike revealed a flood of GET probes searching for vulnerable files. One more fail2ban filter should quickly block this malicious scanning...

🔗 https://ricard.dev/fail2ban-jail-to-block-http-probing/

#linux #fail2ban

Ricard Torres 👨‍💻 @[email protected] · 2026-08-22 · 20:53 UTC

"fail2ban jail to block HTTP probing"

I’ve hardened my VPS with fail2ban to stop WordPress brute‑force attacks, but a recent traffic spike revealed a flood of GET probes searching for vulnerable files. One more fail2ban filter should quickly block this malicious scanning...

🔗 https://ricard.dev/fail2ban-jail-to-block-http-probing/

#linux #fail2ban

Ricard Torres 👨‍💻 @[email protected] · 2026-08-22 · 20:53 UTC

"fail2ban jail to block HTTP probing"

I’ve hardened my VPS with fail2ban to stop WordPress brute‑force attacks, but a recent traffic spike revealed a flood of GET probes searching for vulnerable files. One more fail2ban filter should quickly block this malicious scanning...

🔗 https://ricard.dev/fail2ban-jail-to-block-http-probing/

#fail2ban #linux

Ricard Torres 👨‍💻 @[email protected] · 2026-08-22 · 20:53 UTC

"fail2ban jail to block HTTP probing"

I’ve hardened my VPS with fail2ban to stop WordPress brute‑force attacks, but a recent traffic spike revealed a flood of GET probes searching for vulnerable files. One more fail2ban filter should quickly block this malicious scanning...

#linux #fail2ban

Achim :antifa: @[email protected] · 2026-08-17 · 20:42 UTC

#SelfHosting #ReverseProxy #Fail2Ban #CrowdSec #NginxProxyManager

You have already found the core issue: a ban on VM2 is too late.

VM2 does see the real client address in the HTTP logs if NPM passes X-Forwarded-For correctly, but at the network layer every connection to VM2 still originates from NPM on VM1. Therefore an nftables/UFW rule on VM2 can only block NPM — which is not exactly the intended security feature.

For your setup, I would put the actual enforcement at the ingress point:

Run Fail2Ban on VM1.
Parse the NPM access/error logs there.
Let Fail2Ban add/remove bans locally on VM1.
Ensure NPM logs the real client IP, and only trust forwarded-IP headers from proxies you actually control.
Keep VM2 restricted so it accepts service traffic only from VM1/NPM where possible.

Having Fail2Ban on VM2 execute remote firewall actions on VM1 via SSH can work, but it is basically building a small, brittle distributed ban system yourself: SSH keys, narrowly scoped sudo rules, reliable unban actions, error handling, and so on.

Alternative:
If you want detection from several VMs/services but enforcement centrally at NPM, CrowdSec is a more natural fit. Run agents where the relevant logs live, use a central LAPI, and run a bouncer at VM1/NPM. Then the components are designed to exchange decisions instead of hoping two independent Fail2Ban installations telepathically coordinate.

Also: do not use set_real_ip_from 0.0.0.0/0 just to make X-Forwarded-For work. That turns a client-supplied header into an IP-spoofing API.

#selfhosting #reverseproxy #fail2ban #crowdsec #nginxproxymanager

Achim :antifa: @[email protected] · 2026-08-17 · 20:42 UTC

#SelfHosting #ReverseProxy #Fail2Ban #CrowdSec #NginxProxyManager

You have already found the core issue: a ban on VM2 is too late.

VM2 does see the real client address in the HTTP logs if NPM passes X-Forwarded-For correctly, but at the network layer every connection to VM2 still originates from NPM on VM1. Therefore an nftables/UFW rule on VM2 can only block NPM — which is not exactly the intended security feature.

For your setup, I would put the actual enforcement at the ingress point:

Run Fail2Ban on VM1.
Parse the NPM access/error logs there.
Let Fail2Ban add/remove bans locally on VM1.
Ensure NPM logs the real client IP, and only trust forwarded-IP headers from proxies you actually control.
Keep VM2 restricted so it accepts service traffic only from VM1/NPM where possible.

Having Fail2Ban on VM2 execute remote firewall actions on VM1 via SSH can work, but it is basically building a small, brittle distributed ban system yourself: SSH keys, narrowly scoped sudo rules, reliable unban actions, error handling, and so on.

Alternative:
If you want detection from several VMs/services but enforcement centrally at NPM, CrowdSec is a more natural fit. Run agents where the relevant logs live, use a central LAPI, and run a bouncer at VM1/NPM. Then the components are designed to exchange decisions instead of hoping two independent Fail2Ban installations telepathically coordinate.

Also: do not use set_real_ip_from 0.0.0.0/0 just to make X-Forwarded-For work. That turns a client-supplied header into an IP-spoofing API.

#selfhosting #reverseproxy #fail2ban #crowdsec #nginxproxymanager

Achim :antifa: @[email protected] · 2026-08-17 · 20:42 UTC

#SelfHosting #ReverseProxy #Fail2Ban #CrowdSec #NginxProxyManager

You have already found the core issue: a ban on VM2 is too late.

VM2 does see the real client address in the HTTP logs if NPM passes X-Forwarded-For correctly, but at the network layer every connection to VM2 still originates from NPM on VM1. Therefore an nftables/UFW rule on VM2 can only block NPM — which is not exactly the intended security feature.

For your setup, I would put the actual enforcement at the ingress point:

Run Fail2Ban on VM1.
Parse the NPM access/error logs there.
Let Fail2Ban add/remove bans locally on VM1.
Ensure NPM logs the real client IP, and only trust forwarded-IP headers from proxies you actually control.
Keep VM2 restricted so it accepts service traffic only from VM1/NPM where possible.

Having Fail2Ban on VM2 execute remote firewall actions on VM1 via SSH can work, but it is basically building a small, brittle distributed ban system yourself: SSH keys, narrowly scoped sudo rules, reliable unban actions, error handling, and so on.

Alternative:
If you want detection from several VMs/services but enforcement centrally at NPM, CrowdSec is a more natural fit. Run agents where the relevant logs live, use a central LAPI, and run a bouncer at VM1/NPM. Then the components are designed to exchange decisions instead of hoping two independent Fail2Ban installations telepathically coordinate.

Also: do not use set_real_ip_from 0.0.0.0/0 just to make X-Forwarded-For work. That turns a client-supplied header into an IP-spoofing API.

#selfhosting #reverseproxy #fail2ban #crowdsec #nginxproxymanager

Achim :antifa: @[email protected] · 2026-08-17 · 20:42 UTC

#SelfHosting #ReverseProxy #Fail2Ban #CrowdSec #NginxProxyManager

You have already found the core issue: a ban on VM2 is too late.

VM2 does see the real client address in the HTTP logs if NPM passes X-Forwarded-For correctly, but at the network layer every connection to VM2 still originates from NPM on VM1. Therefore an nftables/UFW rule on VM2 can only block NPM — which is not exactly the intended security feature.

For your setup, I would put the actual enforcement at the ingress point:

Run Fail2Ban on VM1.
Parse the NPM access/error logs there.
Let Fail2Ban add/remove bans locally on VM1.
Ensure NPM logs the real client IP, and only trust forwarded-IP headers from proxies you actually control.
Keep VM2 restricted so it accepts service traffic only from VM1/NPM where possible.

Having Fail2Ban on VM2 execute remote firewall actions on VM1 via SSH can work, but it is basically building a small, brittle distributed ban system yourself: SSH keys, narrowly scoped sudo rules, reliable unban actions, error handling, and so on.

Alternative:
If you want detection from several VMs/services but enforcement centrally at NPM, CrowdSec is a more natural fit. Run agents where the relevant logs live, use a central LAPI, and run a bouncer at VM1/NPM. Then the components are designed to exchange decisions instead of hoping two independent Fail2Ban installations telepathically coordinate.

Also: do not use set_real_ip_from 0.0.0.0/0 just to make X-Forwarded-For work. That turns a client-supplied header into an IP-spoofing API.

#nginxproxymanager #crowdsec #fail2ban #reverseproxy #selfhosting

Achim :antifa: @[email protected] · 2026-08-17 · 20:42 UTC

#SelfHosting #ReverseProxy #Fail2Ban #CrowdSec #NginxProxyManager

You have already found the core issue: a ban on VM2 is too late.

VM2 does see the real client address in the HTTP logs if NPM passes X-Forwarded-For correctly, but at the network layer every connection to VM2 still originates from NPM on VM1. Therefore an nftables/UFW rule on VM2 can only block NPM — which is not exactly the intended security feature.

For your setup, I would put the actual enforcement at the ingress point:

Run Fail2Ban on VM1.
Parse the NPM access/error logs there.
Let Fail2Ban add/remove bans locally on VM1.
Ensure NPM logs the real client IP, and only trust forwarded-IP headers from proxies you actually control.
Keep VM2 restricted so it accepts service traffic only from VM1/NPM where possible.

Having Fail2Ban on VM2 execute remote firewall actions on VM1 via SSH can work, but it is basically building a small, brittle distributed ban system yourself: SSH keys, narrowly scoped sudo rules, reliable unban actions, error handling, and so on.

Alternative:
If you want detection from several VMs/services but enforcement centrally at NPM, CrowdSec is a more natural fit. Run agents where the relevant logs live, use a central LAPI, and run a bouncer at VM1/NPM. Then the components are designed to exchange decisions instead of hoping two independent Fail2Ban installations telepathically coordinate.

Also: do not use set_real_ip_from 0.0.0.0/0 just to make X-Forwarded-For work. That turns a client-supplied header into an IP-spoofing API.

#selfhosting #reverseproxy #fail2ban #crowdsec #nginxproxymanager

Rad Web Hosting | radwebhosting.com @[email protected] · 2026-08-15 · 11:26 UTC

📚 Deploy #Koha on #Debian #VPS for Self-Hosted Library Management System This article provides a guide to deploy Koha on Debian VPS to ...
Continued 👉 #opensource #letsencrypt #ufw #selfhosting #integratedlibrarysystem #zebraserver #fail2ban #selfhosted #mariadb #mysql #librarymanagementsoftware

📚 Deploy Koha on Debian VPS fo...

#koha #debian #vps #opensource #letsencrypt #ufw

Rad Web Hosting | radwebhosting.com @[email protected] · 2026-08-15 · 11:26 UTC

📚 Deploy #Koha on #Debian #VPS for Self-Hosted Library Management System This article provides a guide to deploy Koha on Debian VPS to ...
Continued 👉 #opensource #letsencrypt #ufw #selfhosting #integratedlibrarysystem #zebraserver #fail2ban #selfhosted #mariadb #mysql #librarymanagementsoftware

📚 Deploy Koha on Debian VPS fo...

#koha #debian #vps #opensource #letsencrypt #ufw

Rad Web Hosting @[email protected] · 2026-08-14 · 21:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #npm #letsencrypt #selfhosting #firewalld #fail2ban #selfhosted

#phanpy #almalinux #vps #mastodon #fediverse #social

Rad Web Hosting @[email protected] · 2026-08-14 · 21:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #npm #letsencrypt #selfhosting #firewalld #fail2ban #selfhosted

#phanpy #almalinux #vps #mastodon #fediverse #social

Rad Web Hosting @[email protected] · 2026-08-14 · 21:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #npm #letsencrypt #selfhosting #firewalld #fail2ban #selfhosted

#selfhosted #fail2ban #firewalld #selfhosting #letsencrypt #npm

Rad Web Hosting @[email protected] · 2026-08-14 · 21:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #npm #letsencrypt #selfhosting #firewalld #fail2ban #selfhosted

#phanpy #almalinux #vps #mastodon #fediverse #social

Rad Web Hosting @[email protected] · 2026-08-14 · 04:40 UTC

Deploy #VoIP Call Center on #VPS

This article provides a guide demonstrating how to deploy VoIP call center on VPS.

This guide covers a complete #ViciBox deployment on a Rad Web Hosting VPS for #VICIdial call center operations, including VPS requirements, installation, networking, firewall configuration, SSL, and post-install verification.
Important: ViciBox is officially supported on bare metal, KVM ...
Continued 👉 https://blog.radwebhosting.com/deploy-voip-call-center-on-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #letsencrypt #php #telephony #fail2ban #certbot

#voip #vps #vicibox #vicidial #letsencrypt #php

Rad Web Hosting @[email protected] · 2026-08-14 · 04:40 UTC

Deploy #VoIP Call Center on #VPS

This article provides a guide demonstrating how to deploy VoIP call center on VPS.

This guide covers a complete #ViciBox deployment on a Rad Web Hosting VPS for #VICIdial call center operations, including VPS requirements, installation, networking, firewall configuration, SSL, and post-install verification.
Important: ViciBox is officially supported on bare metal, KVM ...
Continued 👉 https://blog.radwebhosting.com/deploy-voip-call-center-on-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #letsencrypt #php #telephony #fail2ban #certbot

#voip #vps #vicibox #vicidial #letsencrypt #php

Rad Web Hosting @[email protected] · 2026-08-14 · 04:40 UTC

Deploy #VoIP Call Center on #VPS

This article provides a guide demonstrating how to deploy VoIP call center on VPS.

This guide covers a complete #ViciBox deployment on a Rad Web Hosting VPS for #VICIdial call center operations, including VPS requirements, installation, networking, firewall configuration, SSL, and post-install verification.
Important: ViciBox is officially supported on bare metal, KVM ...
Continued 👉 https://blog.radwebhosting.com/deploy-voip-call-center-on-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #letsencrypt #php #telephony #fail2ban #certbot

#voip #vps #vicibox #vicidial #letsencrypt #php

Rad Web Hosting | radwebhosting.com @[email protected] · 2026-08-13 · 21:29 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and ...
Continued 👉 #selfhosting #npm #selfhosted #letsencrypt #firewalld #fail2ban

🚀 How to Deploy Phanpy on Alma...

#phanpy #almalinux #vps #mastodon #selfhosting #npm

Rad Web Hosting | radwebhosting.com @[email protected] · 2026-08-13 · 21:29 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and ...
Continued 👉 #selfhosting #npm #selfhosted #letsencrypt #firewalld #fail2ban

🚀 How to Deploy Phanpy on Alma...

#phanpy #almalinux #vps #mastodon #selfhosting #npm

Rad Web Hosting | radwebhosting.com @[email protected] · 2026-08-13 · 21:29 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and ...
Continued 👉 #selfhosting #npm #selfhosted #letsencrypt #firewalld #fail2ban

🚀 How to Deploy Phanpy on Alma...

#phanpy #almalinux #vps #mastodon #selfhosting #npm

Rad Web Hosting | radwebhosting.com @[email protected] · 2026-08-13 · 21:29 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and ...
Continued 👉 #selfhosting #npm #selfhosted #letsencrypt #firewalld #fail2ban

🚀 How to Deploy Phanpy on Alma...

#fail2ban #firewalld #letsencrypt #selfhosted #npm #selfhosting

Rad Web Hosting | radwebhosting.com @[email protected] · 2026-08-13 · 21:29 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and ...
Continued 👉 #selfhosting #npm #selfhosted #letsencrypt #firewalld #fail2ban

🚀 How to Deploy Phanpy on Alma...

#phanpy #almalinux #vps #mastodon #selfhosting #npm

m23hauke @[email protected] · 2026-08-10 · 17:25 UTC

Mailserver gehackt: Was tun?

https://tube.tchncs.de/w/s9RXbqLUywgMyzyqdjw3mH

#fail2ban #hacking #mailserver #postfix #security

Rad Web Hosting @[email protected] · 2026-08-10 · 10:40 UTC

Deploy #VoIP Call Center on #VPS

This article provides a guide demonstrating how to deploy VoIP call center on VPS.

This guide covers a complete #ViciBox deployment on a Rad Web Hosting VPS for #VICIdial call center operations, including VPS requirements, installation, networking, firewall configuration, SSL, and post-install verification.
Important: ViciBox is officially supported on bare metal, KVM ...
Continued 👉 https://blog.radwebhosting.com/deploy-voip-call-center-on-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #telephony #letsencrypt #php #certbot #fail2ban

#voip #vps #vicibox #vicidial #telephony #letsencrypt

Rad Web Hosting @[email protected] · 2026-08-10 · 10:40 UTC

Deploy #VoIP Call Center on #VPS

This article provides a guide demonstrating how to deploy VoIP call center on VPS.

This guide covers a complete #ViciBox deployment on a Rad Web Hosting VPS for #VICIdial call center operations, including VPS requirements, installation, networking, firewall configuration, SSL, and post-install verification.
Important: ViciBox is officially supported on bare metal, KVM ...
Continued 👉 https://blog.radwebhosting.com/deploy-voip-call-center-on-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #telephony #letsencrypt #php #certbot #fail2ban

#voip #vps #vicibox #vicidial #telephony #letsencrypt

Rad Web Hosting @[email protected] · 2026-08-10 · 10:40 UTC

Deploy #VoIP Call Center on #VPS

This article provides a guide demonstrating how to deploy VoIP call center on VPS.

This guide covers a complete #ViciBox deployment on a Rad Web Hosting VPS for #VICIdial call center operations, including VPS requirements, installation, networking, firewall configuration, SSL, and post-install verification.
Important: ViciBox is officially supported on bare metal, KVM ...
Continued 👉 https://blog.radwebhosting.com/deploy-voip-call-center-on-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #telephony #letsencrypt #php #certbot #fail2ban

#voip #vps #vicibox #vicidial #telephony #letsencrypt

mastodon.raddemo.host @[email protected] · 2026-08-09 · 05:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.raddemo.host #selfhosted #selfhosting #firewalld #letsencrypt #fail2ban #npm

#phanpy #almalinux #vps #mastodon #fediverse #social

mastodon.raddemo.host @[email protected] · 2026-08-09 · 05:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.raddemo.host #selfhosted #selfhosting #firewalld #letsencrypt #fail2ban #npm

#phanpy #almalinux #vps #mastodon #fediverse #social

mastodon.raddemo.host @[email protected] · 2026-08-09 · 05:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.raddemo.host #selfhosted #selfhosting #firewalld #letsencrypt #fail2ban #npm

#phanpy #almalinux #vps #mastodon #fediverse #social

mastodon.raddemo.host @[email protected] · 2026-08-09 · 05:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.raddemo.host #selfhosted #selfhosting #firewalld #letsencrypt #fail2ban #npm

#npm #fail2ban #letsencrypt #firewalld #selfhosting #selfhosted

mastodon.raddemo.host @[email protected] · 2026-08-09 · 05:40 UTC

🚀 How to Deploy #Phanpy on #AlmaLinux #VPS

This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for #Mastodon and compatible #Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious #social client that lets users browse, post, reply, boost, and manage Mastodon accounts ...
Continued 👉 https://blog.radwebhosting.com/deploy-phanpy-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.raddemo.host #selfhosted #selfhosting #firewalld #letsencrypt #fail2ban #npm

#phanpy #almalinux #vps #mastodon #fediverse #social

Michael @[email protected] · 2026-08-07 · 16:00 UTC

Über 600'000 gebannte IPs auf einem Forgejo-System. Was zunächst nur als dauerhaft hohe CPU-Last in Checkmk auffiel, entpuppte sich als massiver Crawler-Traffic.

Mit Log-Analyse und gezielten Fail2Ban-Jails konnten wir die Zugriffe automatisiert blockieren. Die CPU-Last fiel danach drastisch.

Den technischen Ablauf habe ich im Blog festgehalten:
https://www.onesystems.ch/blog/wie-monitoring-und-fail2ban-ueber-600000-ips-blockiert-haben/

#checkmk #fail2ban #linux #monitoring

Michael @[email protected] · 2026-08-07 · 16:00 UTC

Über 600'000 gebannte IPs auf einem Forgejo-System. Was zunächst nur als dauerhaft hohe CPU-Last in Checkmk auffiel, entpuppte sich als massiver Crawler-Traffic.

Mit Log-Analyse und gezielten Fail2Ban-Jails konnten wir die Zugriffe automatisiert blockieren. Die CPU-Last fiel danach drastisch.

Den technischen Ablauf habe ich im Blog festgehalten:
https://www.onesystems.ch/blog/wie-monitoring-und-fail2ban-ueber-600000-ips-blockiert-haben/

#checkmk #fail2ban #linux #monitoring

Michael @[email protected] · 2026-08-07 · 16:00 UTC

Über 600'000 gebannte IPs auf einem Forgejo-System. Was zunächst nur als dauerhaft hohe CPU-Last in Checkmk auffiel, entpuppte sich als massiver Crawler-Traffic.

Mit Log-Analyse und gezielten Fail2Ban-Jails konnten wir die Zugriffe automatisiert blockieren. Die CPU-Last fiel danach drastisch.

Den technischen Ablauf habe ich im Blog festgehalten:
https://www.onesystems.ch/blog/wie-monitoring-und-fail2ban-ueber-600000-ips-blockiert-haben/

#checkmk #fail2ban #linux #monitoring

Michael @[email protected] · 2026-08-07 · 16:00 UTC

Über 600'000 gebannte IPs auf einem Forgejo-System. Was zunächst nur als dauerhaft hohe CPU-Last in Checkmk auffiel, entpuppte sich als massiver Crawler-Traffic.

Mit Log-Analyse und gezielten Fail2Ban-Jails konnten wir die Zugriffe automatisiert blockieren. Die CPU-Last fiel danach drastisch.

Den technischen Ablauf habe ich im Blog festgehalten:
https://www.onesystems.ch/blog/wie-monitoring-und-fail2ban-ueber-600000-ips-blockiert-haben/