# \#dev-ops

**URL:** https://meta.discourse.org/tag/dev-ops/871.md

[Latest](https://meta.discourse.org/latest.md) · [Categories](https://meta.discourse.org/categories.md) · [Tags](https://meta.discourse.org/tags.md)

---

## [Dealing with illegal (CSAM) content?](https://meta.discourse.org/t/dealing-with-illegal-csam-content/378529)

<div class="topic-metadata">

**Author:** [@RichardNooooh](https://meta.discourse.org/u/RichardNooooh)\
**Replies:** 0\
**Last updated:** [August 14, 2025, 4:11am UTC](https://meta.discourse.org/t/dealing-with-illegal-csam-content/378529 "2025-08-14T04:11:51Z")

</div>

:warning: This is not a request for legal advice, and any responses in this topic should not be taken as legal advice. :warning: This is a request for general, nonspecific advice. This is really awkward to ask as my …

---

## [When is it safe to \`Reset Update\`?](https://meta.discourse.org/t/when-is-it-safe-to-reset-update/375126)

<div class="topic-metadata">

**Author:** [@blaisep](https://meta.discourse.org/u/blaisep)\
**Replies:** 1\
**Last updated:** [July 22, 2025, 6:30pm UTC](https://meta.discourse.org/t/when-is-it-safe-to-reset-update/375126 "2025-07-22T18:30:39Z")

</div>

TL;DR: How can I tell if it’s safe to Reset Update? In the (wonderful, BTW) web app, the admin/update/discourse window shows a empty status window and only the red Reset Update after three hours of starting the Discours…

---

## [Unable to correctly obtain the list of users to be reviewed](https://meta.discourse.org/t/unable-to-correctly-obtain-the-list-of-users-to-be-reviewed/341149)

<div class="topic-metadata">

**Author:** [@B1397KB](https://meta.discourse.org/u/B1397KB)\
**Replies:** 7\
**Last updated:** [December 10, 2024, 2:43pm UTC](https://meta.discourse.org/t/unable-to-correctly-obtain-the-list-of-users-to-be-reviewed/341149 "2024-12-10T14:43:20Z")

</div>

After I restored the data through the backup file, the website could not obtain the new user registration review information. Specifically, I can find the users waiting for review in the user list, but there is no data …

---

## [Permissions trouble upgrading data container](https://meta.discourse.org/t/permissions-trouble-upgrading-data-container/327794)

<div class="topic-metadata">

**Author:** [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Replies:** 3\
**Last updated:** [October 1, 2024, 3:29pm UTC](https://meta.discourse.org/t/permissions-trouble-upgrading-data-container/327794 "2024-10-01T15:29:36Z")

</div>

I recently rebuilt a data container that was 2 years old. The new container expected different permissions than the old one did, presumably because the postgres user and group had new IDs in the current base OS. I fixed…

---

## [Update takes ~20 minutes and progress update breaks (temporarily) at step multisite:migrate](https://meta.discourse.org/t/update-takes-20-minutes-and-progress-update-breaks-temporarily-at-step-multisite-migrate/326533)

<div class="topic-metadata">

**Author:** [@schneeland](https://meta.discourse.org/u/schneeland)\
**Replies:** 5\
**Last updated:** [September 18, 2024, 1:59am UTC](https://meta.discourse.org/t/update-takes-20-minutes-and-progress-update-breaks-temporarily-at-step-multisite-migrate/326533 "2024-09-18T01:59:02Z")

</div>

I just did the weekly update for our Discourse site and found that instead of taking the regular 1-2 minutes, this time about 20 minutes were needed. Also, progress update temporarily broke with timeout errors in the Chr…

---

## [Rebuilding always fails when the MAXMIND daily limit is exhausted](https://meta.discourse.org/t/rebuilding-always-fails-when-the-maxmind-daily-limit-is-exhausted/312775)

<div class="topic-metadata">

**Author:** [@kuaza](https://meta.discourse.org/u/kuaza)\
**Replies:** 62\
**Last updated:** [August 5, 2024, 1:35am UTC](https://meta.discourse.org/t/rebuilding-always-fails-when-the-maxmind-daily-limit-is-exhausted/312775 "2024-08-05T01:35:00Z")

</div>

Rebuilding always fails when the daily limit is exhausted. I think it would be good to fix this because I lost 2 days and set up a server twice until I found out what caused this problem. Maybe I’m not very smart …
