Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport: Fixes examples for alias_refresh_interval & dns_request_timeout… #5548

Merged
merged 1 commit into from
Feb 13, 2025
Merged

Backport: Fixes examples for alias_refresh_interval & dns_request_timeout… #5548

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions website/content/docs/api-clients/client-agent.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,14 +99,14 @@ The configuration file contains the following fields:

Example:
```hcl
alias_refresh_interval=60s
alias_refresh_interval="60s"
```

- `dns_request_timeout` - Specifies for how long the Client Agent DNS request handling, including any recursion, is allowed to run before it is canceled.

Example:
```hcl
dns_request_timeout=300s
dns_request_timeout="300s"
```

- `interface_to_use` - Specifies the interface to use instead of the default.
Expand Down Expand Up @@ -521,6 +521,10 @@ Follow the troubleshooting steps to understand why the Client Agent is not able
On MacOS versions 15.1 and 15.2, the firewall may incorrectly block the Client Agent from sending DNS responses. To resolve this issue,
upgrade to MacOS version 15.3 or later.

It may be neccessary to explicitly allow the `boundary-client-agent` process access to incoming network connections.

From the Firewall options in System Settings, toggle the `boundary-client-agent` to **Allow incoming connections**.

#### WARNING! Remote host indentification has changed! It is possible that someone is doing something nasty!

This error arises when you use an alias to connect to an SSH target after the first successful connection using that alias. The issue occurs because Boundary workers generate a new host key on every new SSH connection. You can safely ignore the warning using the `StrictHostKeyChecking=no` command line option:
Expand Down
Loading