Infisical / Infisical/infisical

Infisical CLI can't resolve multicast DNS (mDNS) names

Open
#751 0 comments 0 reactions 0 assignees View on GitHub
🐞 bug 🪓 cli
Dominant language
TypeScript
Stars
29.3k
Forks
2.3k
Avg merge
1d 19h
Merged PRs (30d)
320

Description

### Describe the bug

When I use the Infisical CLI tool (Windows 11) to manage secrets on my Infisical server (Ubuntu Linux 23.04 Lunar Lobster), I get an error about name resolution. However, I can resolve the mDNS name of my Infisical server using other applications, like `ping` or Google Chrome web browser.

### To Reproduce
Steps to reproduce the behavior:
0. Deploy Infisical with Docker Compose, to Linux server
1. Install `avahi-daemon` package on Linux server `apt-get install avahi-daemon --yes`
2. Install Infisical CLI on Windows 11 client `scoop install infisical`
3. Run `infisical login` followed by `infisical init`

### Expected behavior
Infisical `init` command resolves mDNS server name

### Screenshots

![image](https://github.com/Infisical/infisical/assets/466713/2d4a9985-0c70-4faf-83ec-94ba92b25a87)

### Platform you are having the issue on: Windows 11 client

Contributor guide

Open the contributing guide

Research direction

Start at the Infisical CLI `init` command and reproduce the Windows 11 client setup against an Ubuntu server running Docker Compose and `avahi-daemon`. Compare the CLI's name-resolution behavior with `ping` or Chrome; done means `infisical init` resolves the server's mDNS name successfully.

Written by the indexing model from the issue text.

Assessment

Domain
cli, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.