Skip to content

Update paths, buttons and peer list view #438

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

Merged
lixmal merged 1 commit into from
Oct 2, 2025
Merged

Update paths, buttons and peer list view #438

Show file tree
Hide file tree
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
Binary file modified public/docs-static/img/how-to-guides/browser-client/peer-list-view.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions src/pages/about-netbird/browser-client-architecture.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,10 +128,10 @@ This multi-layer approach ensures end-to-end encryption (WireGuard) while enabli

The Browser Client communicates with NetBird services through WebSocket proxies:

- **Management Server**: WebSocket to gRPC proxy at the `/ws-proxy` endpoint
- **Management Server**: WebSocket to gRPC proxy at the `/ws-proxy/management` endpoint
- Wraps gRPC stream bytes in a WebSocket connection
- Enables the browser to communicate with the gRPC-based management API
- **Signal Server**: WebSocket proxy at the `/ws-proxy` endpoint for the signaling protocol
- **Signal Server**: WebSocket proxy at the `/ws-proxy/signal` endpoint for the signaling protocol
- **Relay Servers**: WebSocket connections for WireGuard tunnel transport

These proxies run alongside the respective NetBird services and translate between browser-compatible WebSocket and internal gRPC protocols.
8 changes: 4 additions & 4 deletions src/pages/how-to/browser-client.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ The easiest way to connect is directly from the Peers dashboard:

1. Navigate to the **Peers** section in your NetBird dashboard
2. Find the peer you want to access
3. In the **Remote Access** section, click the **Launch Console** or **Remote Desktop** button
3. In the **Remote Access** section, click the **SSH** or **RDP** button

<p>
<img src="/docs-static/img/how-to-guides/browser-client/peer-list-view.png" alt="peer-list-view" className="imagewrapper-big"/>
Expand All @@ -43,7 +43,7 @@ The easiest way to connect is directly from the Peers dashboard:

When connecting via SSH:

1. Click the **Launch Console** button for your target peer
1. Click the **SSH** button for your target peer
2. A credentials modal will appear

<p>
Expand All @@ -64,9 +64,9 @@ When connecting via SSH:

### RDP Connection

For Remote Desktop access:
For RDP access:

1. Click the **Remote Desktop** button for your target machine
1. Click the **RDP** button for your target machine
2. A new window will open with a credentials modal - enter your RDP server credentials:

<p>
Expand Down