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

docs/client-agent: add warning about MacOS 15 #5543

Merged
merged 2 commits into from
Feb 11, 2025
+4 −0
Merged

docs/client-agent: add warning about MacOS 15 #5543

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
895e5b4
docs/client-agent: add warning about MacOS 15
johanbrandhorst Feb 11, 2025
5d3959c
Update website/content/docs/api-clients/client-agent.mdx
johanbrandhorst Feb 11, 2025
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
4 changes: 4 additions & 0 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 @@ -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.
johanbrandhorst marked this conversation as resolved.
Show resolved Hide resolved

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