New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git repos: x509: certificate signed by unknown authority #26247
Comments
Same here:
|
This has happened before. See #2371. |
Seems related to some upgrade they ran last night. We had the same problem but it's working again. They wrote "Pretty smooth upgrade last night, but we hit some issues with KBFS this morning. KBFS will be in read-only mode until Merkle Trees are rebuilt. Might take up to 24 hours. Thanks for your patience." |
For future reference, have you got a link for that? |
All my devices cannot connect because of this error, if i don't have paper keys am I lost my data? |
@bon sorry I don't have it. I only saw mention of it here: keybase/keybase-issues#4241 (comment) (or here keybase/keybase-issues#4241) @kuril you MUST upgrade to mac client version 6.2.5. we experienced the certificate issue on macs several weeks ago and the solution was to upgrade to version 6.2.5 |
@osilva how can I upgrade? New version asks to confirm login from any other device but all devices are not able to connect due to this error. |
@kuril sorry but I don't know. I had the same error with the certificate in January and I downloaded the new client (didn't try any upgrades) and reinstalled it. That worked for me but I can't offer any other advice/suggestion if that does not work for you. |
I can confirm on Windows. I was getting the certificate errors. Went to the keybase website, downloaded the latest client, and as soon as I launched keybase, I received a notification on the "People" tab explaining the issue and a message at the top which said
Everything works as it should now. |
Yeah, I would have liked that message in the version that didn't work, lol. Thanks for the heads up! |
I was going to screenshot the message so people knew what to look for, but as a dummy, I closed it and then thought about it afterwards. Keybase has been running fine since then though. You're welcome. |
Nice, yeah that's the message I saw. Weird thing is I don't recall ever seeing anything on the old non-working client to inform users. Not sure if keybase has any type of "announcement" feature, or if that notification was implemented specifically for this issue. |
Where are you getting that error at? I've never seen that one popup. |
Are you really using a keybase issue to advertise your scams. This is for keybase discussion, not whatever you're going on about. |
Since roughly today, I get the "x509: certificate signed by unknown authority" error when trying to work with my repos. Last time I've seen it working was yesterday.
C:\Windows\System32>keybase version
Client: 6.2.5-20231231232650+3bdf76f84a
Service: 6.2.5-20231231232650+3bdf76f84a
my log id: 7da4aeb84a8fb6ec2fc6bf1c
The text was updated successfully, but these errors were encountered: