# Errore di carico estremo dopo l'aggiornamento a 3.3.0.beta3-dev ieri (on Prem)

**URL:** <https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399>\
**Category:** Self-hosting\
**Created:** [3 Giugno 2024, 7:17pm UTC](https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399 "2024-06-03T19:17:43Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Jose\_C\_Gomez](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jose_c_gomez/32/137297_2.png) [@Jose\_C\_Gomez](https://meta.discourse.org/u/Jose_C_Gomez)\
**Post date:** [4 Giugno 2024, 9:08pm UTC](https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399/9 "2024-06-04T21:08:40Z")

</div>

Ho aggiunto un blocco al crawler di Facebook perché quel tipo stava andando a tutto gas  
 ![image](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/meta/original/4X/9/4/6/94632bf4ba5b377500aff6660586fbbc44e44a29.png)

Tuttavia, ho notato che l’aggiunta di rallentamenti / crawler non sta aggiornando il mio robots.txt

 ![image](https://global.discourse-cdn.com/meta/original/4X/4/7/c/47cac716292e9d02617b29cb87c26b47bec6d081.png)

ma robots.txt non mostra le voci di rallentamento, solo le voci di blocco.

 ![image](https://global.discourse-cdn.com/meta/original/4X/8/4/9/849623ec2a24d72dd72a805bb8b4f0550491f58d.png)

---

_[View the full topic](https://meta.discourse.org/t/extreme-load-error-after-upgrading-to-3-3-0-beta3-dev-yesterday-on-prem/310399)._