# Impossibile eseguire il backup o navigare tra i backup

**URL:** https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899
**Category:** Bug
**Tags:** s3
**Created:** [11 Novembre 2024, 7:51am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899 "2024-11-11T07:51:40Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [11 Novembre 2024, 7:51am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/1 "2024-11-11T07:51:40Z")

</div>

Ottenere

```plaintext
Il backup è fallito.

Ecco il log:

undefined method `start_with?' for nil /var/www/discourse/app/models/site_setting.rb:172:in `use_dualstack_endpoint’
/var/www/discourse/lib/s3_helper.rb:269:in `s3_options' /var/www/discourse/lib/backup_restore/s3_backup_store.rb:14:in `initialize’
/var/www/discourse/lib/backup_restore/backup_store.rb:17:in `new'`

```

dopo una ricostruzione molto recente all’ultima versione.

Nel mio caso S3 è ospitato con un bucket AWS standard.

Potrebbe essere correlato?

---

<div class="post-metadata">

### Author: ![hosna](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hosna/32/99969_2.png) [@hosna](https://meta.discourse.org/u/hosna)
#### Post date: [11 Novembre 2024, 8:17am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/2 "2024-11-11T08:17:53Z")

</div>

Utilizzo lo storage di oggetti minio per il mio s3 e ricevo questo errore:

```plaintext
rake aborted!
Aws::S3::Errors::Http504Error: Aws::S3::Errors::Http504Error (Aws::S3::Errors::Http504Error)
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/seahorse/client/plugins/raise_response_errors.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-s3-1.143.0/lib/aws-sdk-s3/plugins/sse_cpk.rb:24:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-s3-1.143.0/lib/aws-sdk-s3/plugins/dualstack.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-s3-1.143.0/lib/aws-sdk-s3/plugins/accelerate.rb:43:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/plugins/checksum_algorithm.rb:111:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/plugins/jsonvalue_converter.rb:16:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/plugins/idempotency_token.rb:19:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/plugins/param_converter.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/seahorse/client/plugins/request_callback.rb:89:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/plugins/response_paging.rb:12:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/seahorse/client/plugins/response_target.rb:24:in `call'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/seahorse/client/request.rb:72:in `send_request'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-s3-1.143.0/lib/aws-sdk-s3/client.rb:11285:in `list_objects_v2'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-s3-1.143.0/lib/aws-sdk-s3/bucket.rb:1304:in `block (2 levels) in objects'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/plugins/user_agent.rb:28:in `feature'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-s3-1.143.0/lib/aws-sdk-s3/bucket.rb:1303:in `block in objects'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:101:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:101:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:101:in `block in non_empty_batches'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:52:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:52:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:52:in `block in each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:58:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:58:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/aws-sdk-core-3.191.3/lib/aws-sdk-core/resources/collection.rb:58:in `each'
/var/www/discourse/lib/tasks/s3.rake:14:in `map'
/var/www/discourse/lib/tasks/s3.rake:14:in `existing_assets'
/var/www/discourse/lib/tasks/s3.rake:210:in `block in <main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Tasks: TOP => s3:expire_missing_assets
(See full trace by running task with --trace)
I, [2024-11-11T08:02:51.942337 #1] INFO -- : Checking for stale S3 assets...

I, [2024-11-11T08:02:51.944197 #1] INFO -- : Terminating async processes
I, [2024-11-11T08:02:51.944334 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 39
I, [2024-11-11T08:02:51.944432 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 107
2024-11-11 08:02:51.944 UTC [39] LOG: received fast shutdown request
107:signal-handler (1731312171) Received SIGTERM scheduling shutdown...
2024-11-11 08:02:51.945 UTC [39] LOG: aborting any active transactions
2024-11-11 08:02:51.949 UTC [39] LOG: background worker "logical replication launcher" (PID 54) exited with exit code 1
2024-11-11 08:02:51.950 UTC [49] LOG: shutting down
107:M 11 Nov 2024 08:02:51.960 # User requested shutdown...
107:M 11 Nov 2024 08:02:51.960 * Saving the final RDB snapshot before exiting.
2024-11-11 08:02:52.047 UTC [39] LOG: database system is shut down
107:M 11 Nov 2024 08:02:52.207 * DB saved on disk
107:M 11 Nov 2024 08:02:52.208 # Redis is now ready to exit, bye bye...

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse &amp;&amp; sudo -E -u discourse bundle exec rake s3:expire_missing_assets failed with return #&lt;Process::Status: pid 3550 exit 1&gt;
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "cmd"=>["sudo -E -u discourse bundle exec rake s3:upload_assets", "sudo -E -u discourse bundle exec rake s3:expire_missing_assets"]}
bootstrap failed with exit code 1
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
4f601885ffad64bcd29f6dbd06df1f0f86ad301341d40e752df7447809a32eff

```

@martin

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [11 Novembre 2024, 11:16pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/3 "2024-11-11T23:16:34Z")

</div>

Un altro problema è che non è più possibile navigare nei backup:

 ![Questo immagine mostra un messaggio di errore del server da un sito web sconosciuto, con un emoji di faccina triste e testo che dice 'Errore del server' e 'Codice di errore: errore 500'. (Sottotitolato dall'IA)](https://global.discourse-cdn.com/meta/original/4X/4/0/f/40f64864852135df9bb71fcc4a980d8b46bb3d30.png)

```plaintext
Errore durante il calcolo del report `storage_stats`: metodo non definito `start_with?' per nil
/var/www/discourse/app/models/site_setting.rb:172:in `use_dualstack_endpoint'
/var/www/discourse/lib/s3_helper.rb:269:in `s3_options'

```

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [11 Novembre 2024, 11:24pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/4 "2024-11-11T23:24:12Z")

</div>

Potrebbe essere questo il motivo?

```plaintext
[7] pry(main)> SiteSetting.Upload.s3_region
=> nil
[8] pry(main)> SiteSetting.s3_region
=> "eu-west-2"
[9] pry(main)>

```

`SiteSetting.Upload.s3_region` è vuoto sulla mia istanza, quindi `starts_with?` sta generando un errore.

> <https://github.com/discourse/discourse/blob/4816e8e0ecebe7048a0b2ea65bf52d66eabe4515/app/models/site_setting.rb#L172>

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [11 Novembre 2024, 11:30pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/5 "2024-11-11T23:30:15Z")

</div>

In questo PR:

> <https://github.com/discourse/discourse/pull/29654/files>
>
> Followup 0568d36133081e52f25f05585c1a568c3b828d79
> 
> S3 itself and other S3-comp…atible providers do not
> allow using an S3 custom endpoint and dualstack at
> the same time, so this commit fixes that by not using
> dualstack when the endpoint is present.
> 
> c.f. https://meta.discourse.org/t/rebuild-issue-cannot-set-dual-stack-in-combination-with-a-custom-endpoint/334902

La spec usa `SiteSetting.s3_region`, ma il codice usa `SiteSetting.Upload.s3_region` 🤔

---

<div class="post-metadata">

### Author: ![martin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/martin/32/491371_2.png) [@martin](https://meta.discourse.org/u/martin)
#### Post date: [12 Novembre 2024, 5:56am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/6 "2024-11-12T05:56:38Z")

</div>

@hosna e @merefield, `SiteSetting.enable_s3_uploads` è vero per entrambi? Se lo è, dovremmo semplicemente usare `SiteSetting.s3_region`:

> <https://github.com/discourse/discourse/blob/f9d92fa8776134836d4fd717f11c937f6609337d/app/models/site_setting.rb#L151-L153>

Cosa ne dici di `SiteSetting::Upload.enable_s3_uploads`, cosa ti restituisce?

Potrei fare una correzione come questa, usando la navigazione sicura per `s3_region`:

```ruby
def self.use_dualstack_endpoint
  SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region&.start_with?("cn-")
end

```

Ma voglio capire perché `SiteSetting.Upload.s3_region` è vuoto per te.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [12 Novembre 2024, 6:40am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/7 "2024-11-12T06:40:30Z")

</div>

OK, questo diventa più strano, ci sono due impostazioni?

![image](https://global.discourse-cdn.com/meta/original/4X/e/d/a/eda6a6fd0b439da2985122fdfd8b6295c30b7019.png)

- Sto usando S3 per i backup ma _non_ per i caricamenti (che è una scelta valida ed è così da anni?)
- Abilitarli entrambi non è imposto dall’interfaccia.
- Non ho cambiato alcuna impostazione per anni.

Quindi `SiteSetting::Upload.s3_region` è vuoto poiché non lo sto usando?

Anche se, come nota a margine, i caricamenti dovrebbero essere inclusi nei backup, ma `SiteSetting.s3_region` dovrebbe essere sufficiente per questo?

I miei backup continuano a fallire

 ![Questa immagine raffigura uno screenshot dall'app di posta elettronica, Mail, che mostra le ultime email, una delle quali è evidenziata come non letta. (Didascalia dell'IA)](https://global.discourse-cdn.com/meta/original/4X/0/1/7/017502e01c9e317f454ccecf8c47c52ffd64c879.png)

---

<div class="post-metadata">

### Author: ![hosna](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hosna/32/99969_2.png) [@hosna](https://meta.discourse.org/u/hosna)
#### Post date: [12 Novembre 2024, 11:42am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/8 "2024-11-12T11:42:17Z")

</div>

> [@martin](#):
>
> `enable_s3_uploads`

se intendi questa impostazione, no, non è abilitata per me

 ![image](https://global.discourse-cdn.com/meta/original/4X/5/f/a/5fab5a24d670f9e8ec9bf600c34a580e65581d9d.png)

ho configurato s3 nel mio file app.yml in questo modo

 ![image](https://global.discourse-cdn.com/meta/original/4X/1/4/d/14d8e4a38bc2932579f4a8a11173efaa32f5d7a6.png)

come menzionato [qui](https://meta.discourse.org/t/configure-an-s3-compatible-object-storage-provider-for-uploads/148916#minio-storage-server-9)

@martin

---

<div class="post-metadata">

### Author: ![omarfilip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/omarfilip/32/208019_2.png) [@omarfilip](https://meta.discourse.org/u/omarfilip)
#### Post date: [13 Novembre 2024, 3:03am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/9 "2024-11-13T03:03:40Z")

</div>

Segnalo lo stesso problema menzionato sopra. Nessun accesso a `/admin/backups` (errore 500), backup fallito.

I backup S3 sono abilitati, gli upload S3 no - è stato così e ha funzionato con successo per anni.

 ![Configurazione S3](https://global.discourse-cdn.com/meta/original/4X/1/e/d/1ed9594426be0b1c608b9a7dc5b143cebbc65f1a.png)

> **Log degli errori**
>
> ```plaintext
> ### Messaggio (14 copie segnalate)
> 
> Errore durante il calcolo del report `storage_stats`: undefined method `start_with?' for nil /var/www/discourse/app/models/site_setting.rb:172:in `use_dualstack_endpoint' /var/www/discourse/lib/s3_helper.rb:269:in `s3_options' /var/www/discourse/lib/backup_restore/s3_backup_store.rb:14:in `initialize' /var/www/discourse/lib/backup_restore/backup_store.rb:17:in `new' /var/www/discourse/lib/backup_restore/backup_store.rb:17:in `create' /var/www/discourse/app/models/concerns/reports/storage_stats.rb:10:in `report_storage_stats' /var/www/discourse/app/models/report.rb:269:in `public_send' /var/www/discourse/app/models/report.rb:269:in `block in find' /var/www/discourse/app/models/report.rb:165:in `block in wrap_slow_query' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.5/lib/active_record/connection_adapters/abstract/transaction.rb:535:in `block in within_new_transaction' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.5/lib/active_support/concurrency/null_lock.rb:9:in `synchronize' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.5/lib/active_record/connection_adapters/abstract/transaction.rb:532:in `within_new_transaction' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.5/lib/active_record/connection_adapters/abstract/database_statements.rb:344:in `transaction' /var/www/discourse/app/models/report.rb:160:in `wrap_slow_query' /var/www/discourse/app/models/report.rb:267:in `find' /var/www/discourse/app/controllers/admin/reports_controller.rb:97:in `block (2 levels) in bulk' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/actionpack-7.1.5/lib/action_controller/metal/strong_parameters.rb:400:in `block in each_pair' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/actionpack-7.1.5/lib/action_controller/metal/strong_parameters.rb:399:in `each_pair' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/actionpack-7.1.5/lib/action_controller/metal/strong_parameters.rb:399:in `each_pair' /var/www/discourse/app/contro...
> 
> ### Backtrace
> 
> activesupport-7.1.5/lib/active_support/broadcast_logger.rb:134:in `block in error'
> 
> activesupport-7.1.5/lib/active_support/broadcast_logger.rb:231:in `block in dispatch'
> 
> activesupport-7.1.5/lib/active_support/broadcast_logger.rb:231:in `each'
> 
> activesupport-7.1.5/lib/active_support/broadcast_logger.rb:231:in `dispatch'
> 
> activesupport-7.1.5/lib/active_support/broadcast_logger.rb:134:in `error'
> 
> /var/www/discourse/app/models/report.rb:295:in `rescue in find'
> 
> /var/www/discourse/app/models/report.rb:262:in `find'
> 
> /var/www/discourse/app/controllers/admin/reports_controller.rb:97:in `block (2 levels) in bulk'
> 
> actionpack-7.1.5/lib/action_controller/metal/strong_parameters.rb:400:in `block in each_pair'
> 
> actionpack-7.1.5/lib/action_controller/metal/strong_parameters.rb:399:in `each_pair'
> 
> actionpack-7.1.5/lib/action_controller/metal/strong_parameters.rb:399:in `each_pair'
> 
> /var/www/discourse/app/controllers/admin/reports_controller.rb:76:in `block in bulk'
> 
> /var/www/discourse/lib/hijack.rb:64:in `instance_eval'
> 
> /var/www/discourse/lib/hijack.rb:64:in `block in hijack'
> 
> concurrent-ruby-1.3.4/lib/concurrent-ruby/concurrent/promises.rb:911:in `callback_on_resolution'
> 
> concurrent-ruby-1.3.4/lib/concurrent-ruby/concurrent/promises.rb:797:in `call_callback'
> 
> concurrent-ruby-1.3.4/lib/concurrent-ruby/concurrent/promises.rb:803:in `call_callbacks'
> 
> concurrent-ruby-1.3.4/lib/concurrent-ruby/concurrent/promises.rb:692:in `resolve_with'
> 
> concurrent-ruby-1.3.4/lib/concurrent-ruby/concurrent/promises.rb:1325:in `resolve'
> 
> /var/www/discourse/lib/scheduler/defer.rb:115:in `block in do_work'
> 
> rails_multisite-6.1.0/lib/rails_multisite/connection_management/null_instance.rb:49:in `with_connection'
> 
> rails_multisite-6.1.0/lib/rails_multisite/connection_management.rb:21:in `with_connection'
> 
> /var/www/discourse/lib/scheduler/defer.rb:109:in `do_work'
> 
> /var/www/discourse/lib/scheduler/defer.rb:97:in `block (2 levels) in start_thread'
> 
> ### Env
> 
> 1/14
> 
> |hostname|forum-app|
> | --- | --- |
> |process_id|849|
> |application_version|234133bd3b0750b2675a1c2c6745616c899df990|
> |HTTP_HOST|forum.glasair-owners.com|
> |REQUEST_METHOD|GET|
> |HTTP_USER_AGENT|Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36|
> |HTTP_ACCEPT|application/json, text/javascript, */*; q=0.01|
> |HTTP_REFERER|https://forum.glasair-owners.com/admin|
> |HTTP_X_FORWARDED_FOR|xxx|
> |HTTP_X_REAL_IP|xxx|
> |username|xxx|
> |time|6:47 pm|
> ||params null|
> 
> ```

---

<div class="post-metadata">

### Author: ![Chet\_McDoniel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chet_mcdoniel/32/463598_2.png) [@Chet\_McDoniel](https://meta.discourse.org/u/Chet_McDoniel)
#### Post date: [13 Novembre 2024, 3:30am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/10 "2024-11-13T03:30:57Z")

</div>

Stesso problema qui…

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [14 Novembre 2024, 5:07pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/12 "2024-11-14T17:07:02Z")

</div>

> [@martin](#):
>
> @hosna e @merefield, `SiteSetting.enable_s3_uploads` è vero per entrambi?

No. Questo è il problema, ne sono abbastanza sicuro. Usano S3 per i backup, ma non per gli upload, che è una configurazione abbastanza comune per gli self-hoster. È facile configurare i backup S3 e non richiede una CDN o la modifica dello YML per caricare gli asset da precompilare.

> [@martin](#):
>
> Voglio capire perché `SiteSetting.Upload.s3_region` è vuoto per te.

È vuoto perché non usano S3 per gli upload.

```plaintext
      SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region.start_with?("cn-")

```

dal link di github sopra, dovrebbe essere

```plaintext
      GlobalSettings.use_s3 && SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region.start_with?("cn-")

```

o forse

```plaintext
      SiteSetting.enable_s3_uploads && SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region.start_with?("cn-")

```

Non sono abbastanza sicuro di come `use_s3` e `enable_s3_uploads` siano collegati.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [14 Novembre 2024, 5:18pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/13 "2024-11-14T17:18:44Z")

</div>

E penso che

> <https://github.com/discourse/discourse/blob/4816e8e0ecebe7048a0b2ea65bf52d66eabe4515/app/models/site_setting.rb#L175>

dovrebbe davvero essere `def self.enable_s3_uploads?` (poiché riporta se s3\_uploads sono abilitati piuttosto che abilitare s3 uploads) e poi

```plaintext
  SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region.start_with?("cn-")

```

dovrebbe essere

```plaintext
  use_s3_uploads? && SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region.start_with?("cn-")

```

D’altra parte, è così che l’ha chiamato Sam 7 anni fa, e sembra che sia andato tutto bene.🙂

quindi, come si chiama ora la funzione

```plaintext
  use_s3_uploads && SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region.start_with?("cn-")

```

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [14 Novembre 2024, 6:50pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/14 "2024-11-14T18:50:46Z")

</div>

> [@pfaffman](#):
>
> ` use_s3_uploads? && SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region.start_with?("cn-")`

non dovrebbe essere?:

` use_s3_uploads? && !SiteSetting.Upload.s3_endpoint.blank? && !SiteSetting.Upload.s3_region.start_with?("cn-")`

cioè l’endpoint di upload s3 _non_ è vuoto?

---

<div class="post-metadata">

### Author: ![hosna](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hosna/32/99969_2.png) [@hosna](https://meta.discourse.org/u/hosna)
#### Post date: [14 Novembre 2024, 7:04pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/15 "2024-11-14T19:04:02Z")

</div>

> [@pfaffman](#):
>
> No. Questo è il problema, ne sono abbastanza sicuro. Stanno usando S3 per i backup,

ma uso anche s3 per i caricamenti. L’ho configurato nel mio app.yml.

 ![image](https://global.discourse-cdn.com/meta/original/4X/a/1/8/a1801738208e65dc12ab0e4c25b6049f63be4ffa.png)

---

<div class="post-metadata">

### Author: ![MarcP](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marcp/32/160184_2.png) [@MarcP](https://meta.discourse.org/u/MarcP)
#### Post date: [14 Novembre 2024, 7:29pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/16 "2024-11-14T19:29:01Z")

</div>

Ho lo stesso problema.. ho effettuato l’accesso al mio provider di archiviazione per verificare se avessi pagato la fattura, e l’ho fatto.

Perché una modifica così drastica è stata implementata senza alcun annuncio?

Dobbiamo inserire tutti i dettagli in app.yml ora?

Perché tutte le impostazioni sono state rimosse dal backend di amministrazione? Come possiamo recuperare quelle impostazioni? L’ho configurato una volta anni fa e non ho idea di quale sia la mia chiave o il mio segreto e non sono nemmeno sicuro se posso recuperarlo senza reimpostare la chiave (il che influirebbe su altri servizi per i quali utilizzo gli stessi endpoint s3…).

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [14 Novembre 2024, 8:12pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/17 "2024-11-14T20:12:13Z")

</div>

Credo che le impostazioni siano ancora presenti nell’interfaccia utente (posizione di backup, frequenza, bucket S3, ecc.), semplicemente non funzionano più come prima.  
Non credo che si tratti di una modifica funzionale intenzionale, è semplicemente rotto?  
Dovrebbe sicuramente essere ancora possibile eseguire il backup su S3 senza dover archiviare gli upload su S3: questi sono due casi d’uso separati, sebbene in qualche modo allineati…

---

<div class="post-metadata">

### Author: ![Al\_Ni](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/al_ni/32/464453_2.png) [@Al\_Ni](https://meta.discourse.org/u/Al_Ni)
#### Post date: [14 Novembre 2024, 9:36pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/18 "2024-11-14T21:36:07Z")

</div>

Stesso problema  
Stavo usando S3 per il backup, non per il caricamento

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [14 Novembre 2024, 11:02pm UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/19 "2024-11-14T23:02:15Z")

</div>

> [@MarcP](#):
>
> Perché una modifica così drastica è stata implementata senza alcun preavviso?

Perché non avrebbe dovuto causare problemi, ma il codice s3 deve supportare una serie di casi limite e, a meno che tu non abbia scritto quel codice o prestato attenzione al suo sviluppo nel corso degli anni, è piuttosto difficile intervenire e capire quanto sia grande il problema.

---

<div class="post-metadata">

### Author: ![martin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/martin/32/491371_2.png) [@martin](https://meta.discourse.org/u/martin)
#### Post date: [15 Novembre 2024, 2:06am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/20 "2024-11-15T02:06:02Z")

</div>

Mi dispiace a tutti, sono stato assente per un paio di giorni perché malato. Questo dovrebbe risolvere il problema:

> <https://github.com/discourse/discourse/pull/29775>
>
> Followup 0568d36133081e52f25f05585c1a568c3b828d79
> Followup 97cf069a061e350edfc5…310266e80e58532a39a4
> 
> Due to the S3 dualstack endpoint change, sites with
> S3 backups configured but \_not\_ S3 uploads were erroring,
> with admins unable to access the backups page. This
> commit fixes the error by not enabling S3 dualstack
> endpoints if S3 uploads have not been enabled, backups
> don't need to use them.
> 
> c.f. https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899

Ho provato localmente con caricamenti S3 disabilitati e backup S3 abilitati prima e dopo la correzione, sono stato in grado di replicare lo stesso errore e poi risolverlo.

---

<div class="post-metadata">

### Author: ![omarfilip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/omarfilip/32/208019_2.png) [@omarfilip](https://meta.discourse.org/u/omarfilip)
#### Post date: [15 Novembre 2024, 3:42am UTC](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899/21 "2024-11-15T03:42:50Z")

</div>

Ricostruito e sottoposto a backup con successo.

Grazie @martin .

[Pagina seguente](https://meta.discourse.org/t/unable-to-backup-or-navigate-to-backups/335899.md?page=2)