Forum Discussion

jth's avatar
jth
Occasional Contributor
27 days ago

Repeated errors using git on CLI, VSCode

I am repeatedly having issues where I am getting SSH key errors and/or connections to github are timing out (perhaps connection throttling?) When issuing requests, I'm not always getting prompted or reprompted to approve my key with 1P. Restarting 1P seems to mostly consistently prompt for reauthorization, but it only hangs around for one or two connections before I go back to timeouts/lack of connection. How can I test/confirm whether this is comms issue between the ssh agent and 1P/IDE/CLI?

  • d47793's avatar
    d47793
    New Contributor

    I'm also having this problem since a few weeks. If I try to connect to a SSH host it is sometimes stuck at establishing the connection. Usually the next try works without any problems. This occurs with any host.
    I also suspect that this might be caused by some kind of throttling because it happens especially when doing Ansible deployments via SSH which connects to multiple hosts.

  • Hi jth - could you share a bit more info about what you are experiencing? The tools and workflows you are using. It sounds like you are using the 1Password CLI and are on Mac, but it would be helpful to know more info.

    Thanks!

    Phil

    • jth's avatar
      jth
      Occasional Contributor

      Just using Terminal and VS Code. Have op installed, have dev tools enabled, SSH keys stored in 1P, been getting inconsistent prompts to authorize via Touch ID (on a Mac, up to date with current OS release). Both 

      git push

      and

      git pull

      calls have been stalling, sitting for 15-30 seconds before failing with messages like the one I posted previously.

      • floris_1P's avatar
        floris_1P
        Icon for 1Password Team rank1Password Team

        It might be that the prompt got suppressed if the request came from an app that's running in the background. If that's the case, there will be a small dot in the 1Password menu bar icon, from where you can manually bring the prompt forward. Can you check if that's the case when you experience the stalling behavior again?