# «Zlib::BufError: errore del buffer» - Aggiornamento di Discourse fallisce

**URL:** https://meta.discourse.org/t/zlib-buffer-error-discourse-update-fails/311347
**Category:** Self-hosting
**Created:** [10 Giugno 2024, 6:53am UTC](https://meta.discourse.org/t/zlib-buffer-error-discourse-update-fails/311347 "2024-06-10T06:53:31Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [13 Giugno 2024, 2:43am UTC](https://meta.discourse.org/t/zlib-buffer-error-discourse-update-fails/311347/5 "2024-06-13T02:43:06Z")

</div>

Ho appena riscontrato questo problema durante l’aggiornamento di un’installazione di Discourse…

Credo che la causa sia dovuta al fatto che `DISCOURSE_MAXMIND_LICENSE_KEY` è specificato nel file contenitore `.yml` senza un corrispondente `DISCOURSE_MAXMIND_ACCOUNT_ID`.

La pull request di @tgxworld aggiunge l’uso di `DISCOURSE_MAXMIND_ACCOUNT_ID` in più punti e spiega la necessità di un “Account ID”:

> <https://github.com/discourse/discourse_docker/pull/796>
>
> In order to download the free MaxMind GeoLite2 databases, an account ID
> and lic…ense key is required going forward. This commit updates
> \`discourse-setup\` to start prompting the user to provide the MaxMind
> Account ID first before asking for the MaxMind license key. If the user
> does not provide the Account ID, the script will not prompt for the
> license key as we assume the user has opted out.
> 
> We are aware that we don't have a reliable way to test for changes to
> the \`discourse-setup\` script but it is what it is at this point in time.
> We intend to invest resources in improving things in the future but now
> is not the time.
> 
> \### Review notes
> 
> We unfortunately have to test out the changes by hand:
> 
> 1. Clone this repo
> 2. Run \`sudo SKIP\_CONNECTION\_TEST=1 ./discourse-setup\`
> 3. Enter random values when prompted because the values don't matter. 
> 4. The script will print out "Unfortunately, there was an error changing containers/app.yml" but we can ignore it.
> 5. Run \`sudo cat containers/app.yml | grep MAXMIND\` to see that the envs have been updated to the values prompted before.

Per me la soluzione è stata aggiungere `DISCOURSE_MAXMIND_ACCOUNT_ID` e ricostruire (ho ricostruito due volte, ma questo era molto probabilmente un problema temporaneo).

---

_[View the full topic](https://meta.discourse.org/t/zlib-buffer-error-discourse-update-fails/311347)._