Lazy fails to clone cmp-buffer, cmp-path and cmp-nvim-lsp.

[swyftycodes]

Lazy fails to clone cmp-buffer, cmp-path and cmp-nvim-lsp.

○ cmp-buffer ■ clone failed Cloning into '/home/username/.local/share/nvim/lazy/cmp-buffer'... fatal: unable to access 'https://github.com/hrsh7th/cmp-buffer.git/': Could not resolve host: github.com ○ cmp-nvim-lsp ■ clone failed Cloning into '/home/username/.local/share/nvim/lazy/cmp-nvim-lsp'... fatal: unable to access 'https://github.com/hrsh7th/cmp-nvim-lsp.git/': Could not resolve host: github.com ○ cmp-path ■ clone failed Cloning into '/home/username/.local/share/nvim/lazy/cmp-path'... fatal: unable to access 'https://github.com/hrsh7th/cmp-path.git/': Could not resolve host: github.com

cloning the repos using git clone https://github.com/hrsh7th/cmp-path.git/ works fine, what is the issue here?

[kingu218]

Try this>
1.Check your Internet connection: Make sure you are connected to the Internet and that your connection is functioning properly. Try accessing other websites to confirm that the connection is active.

2.Check network configuration: Ensure that your network configuration is set up correctly. This includes checking for any firewalls or proxy settings that may be blocking the connection to GitHub.

3.Check DNS settings: DNS resolution issues can occur due to incorrect DNS settings. You can try using public DNS servers, such as Google's (8.8.8.8 and 8.8.4.4), to see if this resolves the issue.

4.Check for issues with GitHub: Sometimes, GitHub may experience connection issues or be temporarily unavailable. You can check the status of GitHub on service monitoring websites to see if there are any reported problems.

5.After resolving the issue with connecting to GitHub, try cloning the repository again. If the problem persists, it may be helpful to restart your computer or contact your Internet service provider for assistance.