Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docs/hyperexecute-bidi-testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ From the project root directory, execute the below CLI command in your terminal:

<div className="lambdatest__codeblock">
<CodeBlock className="language-bash">
{`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config hyperexecute.yaml`}
{`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config yaml/hyperexecute-linux.yaml`}
</CodeBlock>
</div>

Expand Down
4 changes: 3 additions & 1 deletion docs/network-whitelisting-and-tunnel-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,9 @@ import TabItem from '@theme/TabItem';
></script>
When testing private or restricted environments on LambdaTest, your team may need to configure network access controls. Depending on how your applications are hosted and secured, LambdaTest supports multiple approaches **Inbound Whitelisting, Dedicated Proxy, Outbound Whitelisting, STUN/TURN Whitelisting, and Tunnel configurations (including Site-to-Site tunnels)**.

This guide helps you decide which option to use for your infrastructure setup.
> These are Inbound and Outbound with respect to user's network.

This guide helps you decide which option to use for your infrastructure setup.

## 1. When Inbound Whitelisting Has to Be Done (Shared IP)
Inbound IP whitelisting allows LambdaTest cloud browsers and devices to directly access your IP-restricted web applications without using a tunnel.
Expand Down
Loading