# Self-ddos
**URL:** https://meta.discourse.org/t/self-ddos/388614
**Category:** Support
**Tags:** unsupported-install
**Created:** [November 17, 2025, 12:28am UTC](https://meta.discourse.org/t/self-ddos/388614 "2025-11-17T00:28:51Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Eviepayne](https://meta.discourse.org/u/Eviepayne)
#### Post date: [November 17, 2025, 12:28am UTC](https://meta.discourse.org/t/self-ddos/388614/1 "2025-11-17T00:28:51Z")
I’m unsure if this is a bug or not but I seem to be experiencing my forum self-ddossing.
Once a day the site will go down because it seems to be creating an index:
> CREATE INDEX CONCURRENTLY temp\_idx\_recent\_regular\_post\_search\_data
> ON post\_search\_data USING GIN(search\_data)
> WHERE NOT private\_message AND post\_id \>= 0
This in turn creates a lot of parallellised queries:
> SELECT “posts”.“id”, “posts”.“user\_id”, “posts”.“topic\_id”, “posts”.“post\_number”, “posts”.“raw”, “posts”.“cooked”, “posts”.“created\_at”, “posts”.“updated\_at”, “posts”.“reply\_to\_post\_number”, “posts”.“reply\_count”, “posts”.“quote\_count”, “posts”.“deleted\_at”, “posts”.“off\_topic\_count”, “posts”.“like\_count”, “posts”.“incoming\_link\_count”, “posts”.“bookmark\_count”, “posts”.“score”, “posts”.“reads”, “posts”.“post\_type”, “posts”.“sort\_order”, “posts”.“last\_editor\_id”, “posts”.“hidden”, “posts”.“hidden\_reason\_id”, “posts”.“notify\_moderators\_count”, “posts”.“spam\_count”, “posts”.“illegal\_count”, “posts”.“inappropriate\_count”, “posts”.“last\_version\_at”, “posts”.“user\_deleted”, “posts”.“reply\_to\_user\_id”, “posts”.“percent\_rank”, “posts”.“notify\_user\_count”, “posts”.“like\_score”, “posts”.“deleted\_by\_id”, “posts”.“edit\_reason”, “posts”.“word\_count”, “posts”.“version”, “posts”.“cook\_method”, “posts”.“wiki”, “posts”.“baked\_at”, “posts”.“baked\_version”, “posts”.“hidden\_at”, “posts”.“self\_edits”, “posts”.“reply\_quoted” …
The issue here is im using a managed database that has a connection pool of 197 which is quickly filled up.
# Versions:
3.6.0.beta2-latest
c3efcc99e3e1f3a0855527d669d8b8f27cdd901b
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [November 17, 2025, 2:01am UTC](https://meta.discourse.org/t/self-ddos/388614/2 "2025-11-17T02:01:35Z")
This smells like you are running in an under-powered or misconfigured database.
How large is your database and what are the database server specs?
---
### Author:  [@Eviepayne](https://meta.discourse.org/u/Eviepayne)
#### Post date: [November 17, 2025, 2:26am UTC](https://meta.discourse.org/t/self-ddos/388614/3 "2025-11-17T02:26:25Z")
Digitalocean managed
8 GB RAM / 4vCPU / 160 GiB Disk / Primary only / TOR1 - PostgreSQL 15
Transaction mode pool (197 connections)
100GB uncompressed is used
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [December 3, 2025, 8:10pm UTC](https://meta.discourse.org/t/self-ddos/388614/4 "2025-12-03T20:10:04Z")
@Eviepayne were you able to get this resolved? If not, can you tell us what more you tried and have found out about your problem? Is this a supported install, created using the [official install](https://meta.discourse.org/t/142537?silent=true) instructions?
---
### Author:  [@Eviepayne](https://meta.discourse.org/u/Eviepayne)
#### Post date: [December 4, 2025, 4:42pm UTC](https://meta.discourse.org/t/self-ddos/388614/5 "2025-12-04T16:42:32Z")
As far as I can tell I _think_ it’s resolved. idk how I fixed it but it seemed to have stopped after some updates to newer container revisions.
I’m on: [4d20baa8754fd782f01fbf8bf5c687cae846915a](https://github.com/discourse/discourse/tree/4d20baa8754fd782f01fbf8bf5c687cae846915a)
My installation is fairly removed from the supported install at this point.
The [standard install](https://meta.discourse.org/t/142537?silent=true) applies but what has changed is:
External Database (managed with digitalocean)
External Cache (managed valkey with digitalocean)
Pinned container revision
ACME Client reconfigured for DNS challenges
There was an issue in the past where I couldn’t update due to pgvector versions changing and not being available at DO for pg15, that’s since been resolved so I updated and the self-ddosing behavior appears to not be occurring anymore.
I think the version I was on before was: [db67a0841e8e14ae70de0890441f8158c50ae3c9](https://github.com/discourse/discourse/tree/db67a0841e8e14ae70de0890441f8158c50ae3c9)
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [January 3, 2026, 4:43pm UTC](https://meta.discourse.org/t/self-ddos/388614/6 "2026-01-03T16:43:20Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.