client icon indicating copy to clipboard operation
client copied to clipboard

Published 20 hours ago • verified publisher icon keybase

Git repos: x509: certificate signed by unknown authority

Open kovrob opened this issue 1 year ago • 19 comments

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

kovrob avatar Feb 16 '24 14:02 kovrob

Same here:

Client:  6.2.4-20240101011938+ae7e4a1c15
Service: 6.2.4-20240101011938+ae7e4a1c15

epichoxha avatar Feb 16 '24 15:02 epichoxha

This has happened before. See #2371. I'm seeing it now too. Same client as @epichoxha

bon avatar Feb 16 '24 16:02 bon

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."

osilva avatar Feb 16 '24 16:02 osilva

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?

bon avatar Feb 17 '24 11:02 bon

All my devices cannot connect because of this error, if i don't have paper keys am I lost my data? here is my mac client Version 6.2.4-20231019211625+5cfcf6b41e (6.2.4-20231019211625+5cfcf6b41e)

kuril avatar Feb 18 '24 19:02 kuril

@bon sorry I don't have it. I only saw mention of it here: https://github.com/keybase/keybase-issues/issues/4241#issuecomment-1948808404 (or here https://github.com/keybase/keybase-issues/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 avatar Feb 19 '24 07:02 osilva

@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 avatar Feb 19 '24 08:02 kuril

@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.

osilva avatar Feb 19 '24 09:02 osilva

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

Keybase experienced an expired certificate. You must visit the keybase website and upgrade your client. If you can see this message, then your current client is working.

Everything works as it should now.

Aetherinox avatar Feb 19 '24 23:02 Aetherinox

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

Keybase experienced an expired certificate. You must visit the keybase website and upgrade your client. If you can see this message, then your current client is working.

Yeah, I would have liked that message in the version that didn't work, lol.

Thanks for the heads up!

nilskp avatar Mar 06 '24 12:03 nilskp

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.

Aetherinox avatar Mar 06 '24 12:03 Aetherinox

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.

Here's the screenshot. ;)

grafik

morphtown avatar Mar 14 '24 22:03 morphtown

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.

Aetherinox avatar Mar 15 '24 03:03 Aetherinox

Is this ever going to be fixed? What's the deal with this... I need my stuff i thought the whole point of keybase is it was e2e image

silence48 avatar Apr 23 '24 21:04 silence48

Where are you getting that error at? I've never seen that one popup.

Aetherinox avatar Apr 23 '24 21:04 Aetherinox

Is this ever going to be fixed? What's the deal with this... I need my stuff i thought the whole point of keybase is it was e2e image

I don't know if it'll get fixed for the future, but you need to manually install the latest version to resolve this.

nilskp avatar Apr 23 '24 21:04 nilskp

Are you really using a keybase issue to advertise your scams. This is for keybase discussion, not whatever you're going on about.

Aetherinox avatar May 12 '24 21:05 Aetherinox