Cannot manually sync vault on local instance 1.33.0 #5472
Unanswered
boooooooaq
asked this question in
Q&A
Replies: 1 comment 4 replies
-
But, why not fix a valid certificate then? I do not know how Vaultwarden would be able to fix a client side issue which sanely checks and verifies a certificate for security reasons, and denies a connection if that isn't valid. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
v1.33.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
none
Host/Server Operating System
Linux
Operating System Version
Debian 12
Clients
Browser Extension
Client Version
2025.1.1
Steps To Reproduce
Expected Result
Syncing successful message appears, and sync's
Actual Result
Syncing failed message appears, and does not sync
Logs
Screenshots or Videos
No response
Additional Context
I don't have a valid local tls certificate, so every few days I had to clear the
net::ERR_CERT_AUTHORITY_INVALID
message, and after that sync workt fine, but that was with previous version's of Vaultwarden, now on 1.33.0 even when I clear that message sync fails, also I get the following in the web-browsers console every time I click the sync button:Error refreshing access token: TypeError: Failed to fetch at Ev.nativeFetch (background.js:2:1245480) at Ev.<anonymous> (background.js:2:1245440) at Generator.next (<anonymous>) at s (background.js:2:1219626)
Finally manual sync DOES work when proxy-ing my instance with Cloudflare tunnels to my domain.
Would like it if this could get resolved, if not thank you anyways for making and maintaining Vaultwarden!
Beta Was this translation helpful? Give feedback.
All reactions