<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with burningboard]]></title><description><![CDATA[A list of topics that have been tagged with burningboard]]></description><link>https://board.circlewithadot.net/tags/burningboard</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 21:37:03 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/tags/burningboard.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Mastodon Incident Report &#x2F; Root cause analysis:]]></title><description><![CDATA[Mastodon Incident Report / Root cause analysis:Earlier today, users experienced timeouts with Search, Hashtags, and Autocomplete. Root Cause: Our setup separates the Mastodon frontend VPS (Hetzner) from backend services (for example Elasticsearch) via an OPNSense firewall. Suricata (our IPS) triggered a false-positive on internal traffic and aggressively blocked the VPS IP, severing the connection to the search database.Resolution: We identified the false-positive, added the frontend IP to the whitelist, and traffic immediately normalized. Everything is back to green!#mastodon #mastoadmin #burningboard #elasticsearch #firewall #opnsense #suricata #oopsie]]></description><link>https://board.circlewithadot.net/topic/029d7511-69a3-425c-bc6a-58a5c6eb2a89/mastodon-incident-report-root-cause-analysis</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/029d7511-69a3-425c-bc6a-58a5c6eb2a89/mastodon-incident-report-root-cause-analysis</guid><dc:creator><![CDATA[larvitz@burningboard.net]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>