New feature: domain name expiration check. From now on the bot will remind you if your domain name expires in 14 days (or less).
Improvement: 3 months interval added in response time metrics (command /metrics)
Improvement: the bot has migrated to a powerful new server: nothing should be broken, but don't hesitate to drop a line to @CaddisFly in case of any troubles. New IP addresses: https://watchbot.fflow.net/ip-list.txt.
Update for Cloudflare clients: in some cases, especially when your website in Bot Fight Mode, Cloudflare may block the monitoring bot. In this case you receive the alert
To unblock the bot, got to Cloudflare → Security → WAF → Tools → IP Access Rules (https://dash.cloudflare.com/?to=/:account/:zone/firewall/tools) and allow all the IP addresses (listed here: https://watchbot.fflow.net/ip-list.txt).
https://your.website is DOWN (HTTP 403: Forbidden) from the bot.To unblock the bot, got to Cloudflare → Security → WAF → Tools → IP Access Rules (https://dash.cloudflare.com/?to=/:account/:zone/firewall/tools) and allow all the IP addresses (listed here: https://watchbot.fflow.net/ip-list.txt).
Fellow system administrators, be aware of a new SSH vulnerability: https://www.qualys.com/regresshion-cve-2024-6387/
Mitigation for Ubuntu servers: https://ubuntu.com/security/CVE-2024-6387
Mitigation for Ubuntu servers: https://ubuntu.com/security/CVE-2024-6387
One more critical Linux vulnerability: https://securityonline.info/severe-unauthenticated-rce-flaw-cvss-9-9-in-gnu-linux-systems-awaiting-full-disclosure/ (in Russian: https://habr.com/en/companies/spring_aio/articles/846498/)
TL;DR: if
TL;DR: if
sudo systemctl status cups-browsed shows "Active: inactive (dead)", then your system is not vulnerable; otherwise it is vulnerable. Mitigation: stop and disable "cups-browsed" service: sudo systemctl stop cups-browsed; sudo systemctl disable cups-browsedTo everyone who got dozens of error messages during last 8 hours — I'm sorry! It was a bug in my bot, it is fixed now.
👍9👏2