Fig daemon doesn't start, fig doctor fails to fix.

[vlebourl]

Description:

Please include a detailed description of the issue (and an image or screen recording, if applicable)

fig daemon doesn't start after a fresh installation, nothing changed from default.

2022-03-14T14:42:41.400245Z  INFO fig::daemon: 434: Starting daemon...
2022-03-14T14:42:41.749061Z  WARN hyper_rustls::connector: 39: Could not load all certificates: Custom { kind: InvalidData, error: Custom { kind: InvalidData, error: BadDER } }
Could not connect to websocket

Caused by:
    0: TLS error: webpki error: UnsupportedCriticalExtension
    1: webpki error: UnsupportedCriticalExtension
    2: UnsupportedCriticalExtension

Details:

OS	Fig	Shell
macOS 10.15.7 (19H1715)	1.0.56	/bin/zsh

fig diagnostic

Fig Diagnostics

Fig details:

• Fig version: Version 1.0.56 (B403) [French - PC]
• Bundle path: /Applications/Fig.app
• Autocomplete: true
• Settings.json: true
• Accessibility: true
• Number of specs: 0
• Symlinked dotfiles: false
• Only insert on tab: false
• Keybindings path:
• Installation Script: true
• PseudoTerminal Path:
• SecureKeyboardInput: false
• SecureKeyboardProcess:

Hardware Info:

• Model Name: iMac Pro
• Model Identifier: iMacPro1,1
• Chip:
• Cores: 18
• Memory: 32 GB

OS Info:

• macOS 10.15.7 (19H1715)

Environment:

• User Shell: /bin/zsh
• Current Directory: /Users/vlb
• CLI Installed: true
• Executable Location: /Users/vlb/.local/bin/fig
• Current Window ID: 9136/% (com.googlecode.iterm2)
• Active Process: zsh (30914) - /dev/ttys007
• Environment Variables:
  • TERM=xterm-256color
  • FIG_INTEGRATION_VERSION=8
  • FIG_TERM=1
  • FIG_TERM_VERSION=4.2.0
  • FIG_CHECKED_PROMPTS=1

Integrations:

• SSH: false
• TMUX: false
• iTerm: installed!
• Hyper: application is not present.
• Visual Studio Code: installed!
• Docker: false

[grant0417]

Not too sure what the issue is here, looks like you have some issues with your certs, you might want to make an issue at webpki as that is the library that is unable to load your certs, might be an error there.

[sgruby]

Same issue here. I uninstalled, re-installed and am getting the same issue using Fish and macOS 12.3.

[mschrage]

@sgruby @vlebourl are either of you free to jump on a call to debug this? I'll be in this meeting room for the next hour or so.
https://us06web.zoom.us/j/84904904358?pwd=TU5aamI5T3hpRGthMjNNOW5CbE9RZz09

[grant0417]

I'm going to try to move from using webpki to webpki-roots, this should hopefully resolve the issue but will mean that the certs are built into the binary.

[grant0417]

This should be fixed on the stable build of Fig.

Run fig update or go into the Fig menu an click Check for Updates...

Also make sure to run fig doctor after you update to ensure Fig is working correctly.

[sgruby]

Just updated and still having the same problem.

[grant0417]

@sgruby, are you sure you are on B414 and it is the same error?

[sgruby]

Yup, B414!

[grant0417]

This is strange, are you on an older version of macos?

[sgruby]

Nope, 12.3 on an M1 MacBook Air.

[grant0417]

@sgruby, do you use a VPN?

[sgruby]

@grant0417 Nope. Just SSH connections to various hosts.

[grant0417]

Just to associate with another user's feedback here is what they said when they got the same webpki error.

Well, this is a custom VPN. You could think that it just like OpenVPN using TUN mode but hijacked all the connections like Proxifier do. The software name is ClashX Pro. You need to host server yourself. Software is open source on GitHub.

But since this VPN doesn't do any MiTM, just redirect connection to 198.18.0.1/16 and do a IP mapping. I'm really curious about how it is affecting TLS.

[sgruby]

I was running sshuttle that did something similar, but stopped it and reset PF using:

sudo pfctl -f /etc/pf.conf

I'm not even sure what the daemon is doing as other parts of fig seem to work fine.

[grant0417]

Did that fix the issue?

It is currently only used for syncing your settings, but will soon also sync dotfiles and plugins.

[sgruby]

Nope. Sorry.

[BrennerSpear]

I'm getting this issue too. I'm on 2.17.0

[raoulkent]

Getting this issue as well. Running fig 2.17.0 and MacOS 14.2.1

Edit: Resolved by following #2061 (comment)