blog: verified posts + translations for 2026-10-06

blog/2026-10-06-fix-digitalocean-spaces-connection-errors-rcloneview.md

@@ -0,0 +1,83 @@
+---
+slug: fix-digitalocean-spaces-connection-errors-rcloneview
+title: "Fix DigitalOcean Spaces Connection Errors — Troubleshoot Endpoint and Key Issues with RcloneView"
+authors:
+  - jay
+description: "Fix DigitalOcean Spaces connection errors like access denied and signature mismatch by checking endpoint, region, and keys in RcloneView."
+keywords:
+  - fix DigitalOcean Spaces connection error
+  - DigitalOcean Spaces access denied
+  - Spaces SignatureDoesNotMatch
+  - DigitalOcean Spaces endpoint region
+  - S3 compatible troubleshooting
+  - rclone DigitalOcean Spaces
+  - RcloneView DigitalOcean Spaces
+  - Spaces access key
+tags:
+  - RcloneView
+  - troubleshooting
+  - tips
+  - digitalocean-spaces
+  - s3-compatible
+---
+
+import CloudSupportGrid from '../src/components/CloudSupportGrid';
+import cloudIcons from '../src/contexts/cloudIcons';
+import RvCta from '../src/components/RvCta';
+
+# Fix DigitalOcean Spaces Connection Errors — Troubleshoot Endpoint and Key Issues with RcloneView
+
+> Most DigitalOcean Spaces connection failures come down to three settings: the endpoint, the region, and the access keys.
+
+You added a Spaces remote, but the bucket list is empty, or every request returns access denied or a signature error. Because Spaces is an S3-compatible service, the cause is usually a small mismatch in how the remote was configured. RcloneView lets you inspect and correct the remote, then retest from the same window.
+
+<RvCta imageSrc="/img/rcloneview-preview.png" downloadUrl="https://rcloneview.com/src/download.html" />
+
+<!-- truncate -->
+
+## Check the Endpoint and Region First
+
+Spaces endpoints are region specific, in the form `<region>.digitaloceanspaces.com`, for example `nyc3.digitaloceanspaces.com`. If the endpoint region differs from the region where the Space was created, requests fail even when your keys are correct. Open Remote Manager from the Remote tab, edit the remote, and compare the endpoint against the region shown in your DigitalOcean control panel.
+
+Use the bare regional endpoint, not the Space-specific URL that includes the bucket name. Adding the bucket name to the endpoint is a common reason for odd "bucket not found" results.
+
+<img src="/support/images/en/blog/new-remote.png" alt="Editing an S3-compatible remote endpoint in RcloneView" class="img-large img-center" />
+
+## Verify the Access Key and Secret
+
+Spaces uses its own access key pair, separate from your DigitalOcean API token. Pasting an API token into the key field is a frequent mistake. Regenerate a Spaces key pair if you are unsure, then paste both values again, watching for leading or trailing spaces that slip in when copying.
+
+If listing works but uploads fail, the key may lack write permission on that Space. Create a key with the right access and update the remote.
+
+## Test from the Built-in Terminal
+
+RcloneView includes a Terminal tab in the bottom Info View. Run `rclone listremotes` to confirm the remote exists, then `rclone about "myspaces:"` or a simple listing to see the raw error text. The exact message tells you whether the problem is authentication, endpoint, or network.
+
+<img src="/support/images/en/howto/rcloneview-basic/job-history.png" alt="RcloneView job history showing errored transfers" class="img-large img-center" />
+
+Check the Log tab and Job History for repeated failures. If errors appear only on large transfers, lower the number of file transfers in the job's Advanced Settings to ease the load.
+
+## Rule Out Network and Time Problems
+
+A signature error can also come from a system clock that is far off, since signed requests depend on the current time. Correct your clock and retry. Corporate proxies and firewalls that inspect TLS can break connections too, so test from another network if the keys and endpoint look right.
+
+<img src="/support/images/en/blog/cloud-to-cloud-transfer-default.png" alt="Running a transfer to DigitalOcean Spaces in RcloneView" class="img-large img-center" />
+
+## Getting Started
+
+1. **Download RcloneView** from [rcloneview.com](https://rcloneview.com/src/download.html).
+2. Open Remote Manager and edit your Spaces remote; confirm the regional endpoint.
+3. Re-enter the Spaces access key and secret.
+4. Test with a small folder copy, then re-run your full job.
+
+A correctly configured endpoint and key pair turns a vague failure into a reliable, repeatable workflow.
+
+---
+
+**Related Guides:**
+
+- [Manage DigitalOcean Spaces — Sync and Backup with RcloneView](https://rcloneview.com/support/blog/manage-digitalocean-spaces-cloud-sync-backup-rcloneview)
+- [Fix S3 Access Denied Permission Errors with RcloneView](https://rcloneview.com/support/blog/fix-s3-access-denied-permission-errors-rcloneview)
+- [Fix SSL/TLS Certificate Errors with RcloneView](https://rcloneview.com/support/blog/fix-ssl-tls-certificate-errors-cloud-rcloneview)
+
+<CloudSupportGrid />

blog/2026-10-06-hasher-remote-add-checksums-rcloneview.md

@@ -0,0 +1,83 @@
+---
+slug: hasher-remote-add-checksums-rcloneview
+title: "Hasher Remote — Add Checksums to Storage That Lacks Them in RcloneView"
+authors:
+  - steve
+description: "Use the Hasher virtual remote in RcloneView to add hash-based integrity checks to remotes that do not provide checksums themselves."
+keywords:
+  - rclone hasher remote
+  - add checksums to cloud storage
+  - cloud file integrity check
+  - verify file hashes cloud
+  - hasher virtual remote
+  - RcloneView virtual remotes
+  - checksum sync
+  - rclone GUI
+tags:
+  - RcloneView
+  - feature
+  - rclone
+  - cloud-storage
+  - sync
+---
+
+import CloudSupportGrid from '../src/components/CloudSupportGrid';
+import cloudIcons from '../src/contexts/cloudIcons';
+import RvCta from '../src/components/RvCta';
+
+# Hasher Remote — Add Checksums to Storage That Lacks Them in RcloneView
+
+> The Hasher virtual remote adds hashing on top of an existing remote, so integrity checks still work where the storage has no checksums.
+
+Some storage backends cannot supply file hashes, which weakens comparisons and verification after a transfer. RcloneView supports rclone's Hasher virtual remote, a wrapper that layers hashing over a remote you already have. This guide covers when it helps and how to use it.
+
+<RvCta imageSrc="/img/rcloneview-preview.png" downloadUrl="https://rcloneview.com/src/download.html" />
+
+<!-- truncate -->
+
+## What the Hasher Remote Does
+
+Virtual remotes wrap an existing remote to add behavior. Alias shortens paths, Crypt encrypts, and Hasher adds hashing for integrity checks. If a backend does not expose checksums, comparisons fall back to size and modification time, which can miss content that changed without altering either.
+
+By wrapping that backend in a Hasher remote, you give it a hash capability so checksum-based comparison has something to work with. It is a good fit for archives and backups where correctness matters more than speed.
+
+<img src="/support/images/en/blog/new-remote.png" alt="Creating a new virtual remote in RcloneView" class="img-large img-center" />
+
+## Create a Hasher Remote
+
+Open the Remote tab and choose New Remote, then select the Hasher type. Point it at the underlying remote and folder that you want to wrap, and give it a name you will recognize, such as `archive-hashed`. Once saved, it appears in the explorer like any other remote.
+
+Use the wrapped remote wherever you would use the original: browsing, copying, or as a sync source or destination. Keep in mind that hashes are tied to the wrapper, so consistently use the Hasher remote for the data you want verified.
+
+## Use It with Sync and Compare
+
+In a sync job's Advanced Settings, turn on **Enable checksum** so files are compared by hash plus size. Combined with a Hasher remote, this gives more trustworthy results than size and time alone.
+
+<img src="/support/images/en/howto/rcloneview-basic/compare-display-select.png" alt="Folder Compare view showing differences between two folders" class="img-large img-center" />
+
+Run a Dry Run first to preview what will be copied or deleted, then execute. RcloneView mounts AND syncs 90+ providers from one window, on Windows, macOS, and Linux, so the same verification approach works across your clouds.
+
+## Review Results in Job History
+
+After a run, open Job History to confirm status, files transferred, and total size. If a job reports errors, the Log tab shows details.
+
+<img src="/support/images/en/howto/rcloneview-basic/job-history.png" alt="Job history showing completed sync runs" class="img-large img-center" />
+
+## Getting Started
+
+1. **Download RcloneView** from [rcloneview.com](https://rcloneview.com/src/download.html).
+2. Add the remote that lacks checksums, if you have not already.
+3. Create a Hasher remote that wraps it from Remote > New Remote.
+4. Build a sync job with **Enable checksum** on, and run a Dry Run first.
+
+Stronger verification means you find silent differences before they matter.
+
+---
+
+**Related Guides:**
+
+- [Virtual Remotes — Combine, Union, and Alias with RcloneView](https://rcloneview.com/support/blog/virtual-remotes-combine-union-alias-rcloneview)
+- [Fix Cloud Sync Checksum Mismatch with RcloneView](https://rcloneview.com/support/blog/fix-cloud-sync-checksum-mismatch-rcloneview)
+- [Fix Cloud Backup Verification Failures with RcloneView](https://rcloneview.com/support/blog/fix-cloud-backup-verification-failures-rcloneview)
+
+<CloudSupportGrid />

i18n/de/docusaurus-plugin-content-blog/2026-10-06-fix-digitalocean-spaces-connection-errors-rcloneview.md

@@ -0,0 +1,83 @@
+---
+slug: fix-digitalocean-spaces-connection-errors-rcloneview
+title: "DigitalOcean-Spaces-Verbindungsfehler beheben — Endpoint- und Schlüsselprobleme mit RcloneView analysieren"
+authors:
+  - jay
+description: "Beheben Sie DigitalOcean-Spaces-Verbindungsfehler wie „Access Denied“ und Signaturabweichungen, indem Sie Endpoint, Region und Schlüssel in RcloneView prüfen."
+keywords:
+  - DigitalOcean-Spaces-Verbindungsfehler beheben
+  - DigitalOcean Spaces Zugriff verweigert
+  - Spaces SignatureDoesNotMatch
+  - DigitalOcean Spaces Endpoint Region
+  - S3-kompatible Fehlersuche
+  - rclone DigitalOcean Spaces
+  - RcloneView DigitalOcean Spaces
+  - Spaces Access Key
+tags:
+  - RcloneView
+  - troubleshooting
+  - tips
+  - digitalocean-spaces
+  - s3-compatible
+---
+
+import CloudSupportGrid from '@site/src/components/CloudSupportGrid';
+import cloudIcons from '@site/src/contexts/cloudIcons';
+import RvCta from '@site/src/components/RvCta';
+
+# DigitalOcean-Spaces-Verbindungsfehler beheben — Endpoint- und Schlüsselprobleme mit RcloneView analysieren
+
+> Die meisten Verbindungsfehler bei DigitalOcean Spaces lassen sich auf drei Einstellungen zurückführen: Endpoint, Region und Zugriffsschlüssel.
+
+Sie haben ein Spaces-Remote hinzugefügt, aber die Bucket-Liste ist leer, oder jede Anfrage liefert „Access Denied“ oder einen Signaturfehler. Da Spaces ein S3-kompatibler Dienst ist, liegt die Ursache meist in einer kleinen Abweichung bei der Konfiguration des Remotes. Mit RcloneView können Sie das Remote prüfen und korrigieren und anschließend im selben Fenster erneut testen.
+
+<RvCta imageSrc="/img/rcloneview-preview.png" downloadUrl="https://rcloneview.com/src/download.html" />
+
+<!-- truncate -->
+
+## Zuerst Endpoint und Region prüfen
+
+Spaces-Endpoints sind regionsspezifisch und haben die Form `<region>.digitaloceanspaces.com`, zum Beispiel `nyc3.digitaloceanspaces.com`. Weicht die Region des Endpoints von der Region ab, in der der Space erstellt wurde, schlagen Anfragen fehl, selbst wenn Ihre Schlüssel korrekt sind. Öffnen Sie den Remote Manager über den Tab Remote, bearbeiten Sie das Remote und vergleichen Sie den Endpoint mit der Region, die in Ihrer DigitalOcean-Systemsteuerung angezeigt wird.
+
+Verwenden Sie den reinen regionalen Endpoint, nicht die Space-spezifische URL, die den Bucket-Namen enthält. Der Bucket-Name im Endpoint ist ein häufiger Grund für seltsame „bucket not found“-Ergebnisse.
+
+<img src="/support/images/en/blog/new-remote.png" alt="Bearbeiten des Endpoints eines S3-kompatiblen Remotes in RcloneView" class="img-large img-center" />
+
+## Access Key und Secret überprüfen
+
+Spaces verwendet ein eigenes Access-Key-Paar, getrennt von Ihrem DigitalOcean-API-Token. Das Einfügen eines API-Tokens in das Schlüsselfeld ist ein häufiger Fehler. Wenn Sie unsicher sind, erzeugen Sie ein neues Spaces-Schlüsselpaar und fügen Sie beide Werte erneut ein. Achten Sie dabei auf führende oder nachgestellte Leerzeichen, die beim Kopieren hineingeraten.
+
+Funktioniert das Auflisten, aber Uploads schlagen fehl, fehlt dem Schlüssel möglicherweise die Schreibberechtigung für diesen Space. Erstellen Sie einen Schlüssel mit den passenden Rechten und aktualisieren Sie das Remote.
+
+## Im integrierten Terminal testen
+
+RcloneView enthält im unteren Info View einen Tab Terminal. Führen Sie `rclone listremotes` aus, um zu bestätigen, dass das Remote existiert, und anschließend `rclone about "myspaces:"` oder eine einfache Auflistung, um den rohen Fehlertext zu sehen. Die genaue Meldung zeigt, ob das Problem bei der Authentifizierung, beim Endpoint oder im Netzwerk liegt.
+
+<img src="/support/images/en/howto/rcloneview-basic/job-history.png" alt="RcloneView-Jobverlauf mit fehlerhaften Übertragungen" class="img-large img-center" />
+
+Prüfen Sie im Tab Log und im Job History auf wiederholte Fehler. Treten Fehler nur bei großen Übertragungen auf, verringern Sie in den Advanced Settings des Jobs die Anzahl der parallelen Dateiübertragungen, um die Last zu senken.
+
+## Netzwerk- und Zeitprobleme ausschließen
+
+Ein Signaturfehler kann auch von einer stark abweichenden Systemuhr stammen, da signierte Anfragen von der aktuellen Zeit abhängen. Korrigieren Sie die Uhr und versuchen Sie es erneut. Auch Firmen-Proxys und Firewalls, die TLS prüfen, können Verbindungen stören. Testen Sie daher aus einem anderen Netzwerk, wenn Schlüssel und Endpoint korrekt aussehen.
+
+<img src="/support/images/en/blog/cloud-to-cloud-transfer-default.png" alt="Ausführen einer Übertragung zu DigitalOcean Spaces in RcloneView" class="img-large img-center" />
+
+## Erste Schritte
+
+1. **Laden Sie RcloneView herunter** von [rcloneview.com](https://rcloneview.com/src/download.html).
+2. Öffnen Sie den Remote Manager, bearbeiten Sie Ihr Spaces-Remote und bestätigen Sie den regionalen Endpoint.
+3. Geben Sie Access Key und Secret von Spaces erneut ein.
+4. Testen Sie mit dem Kopieren eines kleinen Ordners und führen Sie dann Ihren vollständigen Job erneut aus.
+
+Ein korrekt konfigurierter Endpoint und ein gültiges Schlüsselpaar machen aus einem vagen Fehler einen zuverlässigen, wiederholbaren Workflow.
+
+---
+
+**Weiterführende Anleitungen:**
+
+- [DigitalOcean Spaces verwalten — Synchronisation und Backup mit RcloneView](https://rcloneview.com/support/blog/manage-digitalocean-spaces-cloud-sync-backup-rcloneview)
+- [S3-Berechtigungsfehler „Access Denied“ mit RcloneView beheben](https://rcloneview.com/support/blog/fix-s3-access-denied-permission-errors-rcloneview)
+- [SSL/TLS-Zertifikatsfehler mit RcloneView beheben](https://rcloneview.com/support/blog/fix-ssl-tls-certificate-errors-cloud-rcloneview)
+
+<CloudSupportGrid />