Skip to content

0.4.4

Choose a tag to compare

View all tags
@solidDoWant solidDoWant released this 01 Nov 09:14
· 31 commits to master since this release
0.4.4
297c106
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

vault-sync is a self-hosted replacement for Obsidian Sync. It has two parts: an Obsidian plugin, and a sync server that stores its data in PostgreSQL and S3. This release changes only the server, and only how it connects to S3. It fixes a server that cannot reach S3 when a proxy or gateway that offers HTTP/2 sits in front of the S3 endpoint. To install it, use the server image ghcr.io/soliddowant/vault-sync:0.4.4 or the Helm chart oci://ghcr.io/soliddowant/charts/vault-sync (version 0.4.4). It has no database migration and no new setting, so you can upgrade a 0.4.3 server one replica at a time. The plugin has no changes.

Fixes

  • The server no longer fails its S3 requests when a proxy or gateway in front of S3 offers HTTP/2, for example an Envoy or Istio gateway. Before, the server's start-up check failed with HeadBucket ... EOF, and the server restarted in a loop. The server talks to S3 only over HTTP/1.1, but its TLS handshake still offered HTTP/2. A proxy that supports HTTP/2 chose it, got an HTTP/1.1 request, and closed the connection. The handshake now offers only HTTP/1.1, both with and without VAULT_SYNC_S3_TLS_CA_FILE. An S3 endpoint that does not offer HTTP/2 was not affected. The problem started in 0.3.0. (#1467)

Known issues

  • None known.
Assets 5
Loading