[macOS Big Sur] Cannot connect to Extensions Marketplace, ERR_CERT_INVALID

[microdee]

• VS Code Version: 1.54.3
  • Version: 1.54.3
  • Commit: 2b9aebd
  • Date: 2021-03-15T11:00:52.911Z
  • Electron: 11.3.0
  • Chrome: 87.0.4280.141
  • Node.js: 12.18.3
  • V8: 8.7.220.31-electron.0
  • OS: Darwin arm64 20.3.0
• OS Version: macOS Big Sur 11.2.3

Issue:

Cannot install or list extensions, extensions sidebar says "We cannot connect to the Extension Marketplace at this time, please try again later". When network error is checked in devtools, it complains about certificate being invalid.

Steps to Reproduce:

1. Go to extensions sidebar
2. It displays "We cannot connect to the Extension Marketplace at this time, please try again later" instead of the list of Popular extensions.
3. F1 -> Developer: Toggle Developer Tools
4. Refresh the Extensions Sidebar which should result in this:
   
   

VSCode on Windows has no problem loading extensions at the same time.

Does this issue occur when all extensions are disabled?: Yes, I cannot install any :P

[sandy081]

I see ERR_CERT_INVALID error - you seem to have proxy set up, please check your proxy settings and retry

@chrmarti FYI

[chrmarti]

@microdee Can you access https://marketplace.visualstudio.com using Chrome/Chromium?

[microdee]

yeah it appears that I cannot access that URL from chromium either. but I don't understand, this is a brand new machine I've never touched or even looked at proxy settings. I'll see what I can do in that regard

[microdee]

yeah I cannot see anything enabled in the proxy settings
Safari can load the https://marketplace.visualstudio.com URL but not chromium

[chrmarti]

When you click on the icon to the left of the URL in the location bar in Chromium, you can get additional details on the certificate. What does that show?

[microdee]

I hope this includes info which helps. This is chromium:

DNS names

DNS names continued:

More DNS names:

End of certificate:

[microdee]

Oh yeah! one detail which I forgot to mention. I have an annoying situation where I'm forced to use the root user against my better judgement. Maybe that can mess up chromium certificate checks, which would be very disappointing. And it actually does, in fact I cannot load any https website on root in chromium. bummer.

[chrmarti]

This looks like a Chromium bug, it says the certificate is "valid", but it still doesn't trust it.

I don't have the trust section when I look at this in Chrome on Mac (Catalina), what do these options do?

[microdee]

well I can set them as "Always Trust" and then nothing changes. I agree this seems to be a deeper problem of chromium on the root user. However I can also see why Google would decide to just not trust anything on the root user of MacOS. I can try installing extensions on root from VSIX files maybe.