Skip to content

Commit 76c47e9

Browse files
authored
Added a new FAQ and updated an existing doc (#887) (#888)
2 parents f6fe322 + 3e070ed commit 76c47e9

File tree

2 files changed

+75
-0
lines changed

2 files changed

+75
-0
lines changed
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: "How Do I Fix the Try Again Error When Opening the Testsigma Desktop App?"
3+
metadesc: "Desktop app may fail to launch with a Try again error in Chrome 139+. This occurs when browser permission changes block pop-ups or local network access."
4+
order: 24.21
5+
page_id: "how-do-i-fix-the-try-again-error-when-opening-the-testsigma-desktop-app"
6+
warning: false
7+
contextual_links:
8+
- type: section
9+
name: "Contents"
10+
- type: link
11+
name: "Steps to Resolve the Permission Issue"
12+
url: "#steps-to-resolve-the-permission-issue"
13+
---
14+
15+
---
16+
17+
When you click Open the desktop app from the Testsigma web application, the desktop app may fail to launch and display a Try again error message in Chrome browser versions 139 and later.
18+
19+
This issue can occur due to Chrome browser permission restrictions. After a browser version update, the permissions required to open the desktop application (such as pop-ups or local network access) may be blocked, causing Chrome to prevent the request.
20+
21+
![Try Again](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/chrome_138.1.png)
22+
23+
This article discusses how to resolve the permission issue.
24+
25+
---
26+
27+
## **Steps to Resolve the Permission Issue**
28+
29+
1. In **Chrome**, click the **Site Information** icon in the address bar.
30+
31+
2. Ensure the following permissions are set to **Allow**:
32+
- **Pop-ups and redirects**
33+
- **Local network access**
34+
![Permissions](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/chrome_138.png)
35+
36+
3. If these permissions were previously denied, click **Reset permissions**.
37+
38+
4. Refresh the page.
39+
40+
5. Click **Open the desktop app** again in Testsigma.
41+
42+
6. When **Chrome** displays the permission prompt, click **Allow** or **Open** to proceed with launching the desktop application.
43+
44+
---

src/pages/docs/testsigma-tunnel/setup-installation-docker.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,8 @@ Setting up Testsigma Tunnel with Docker ensures secure and reliable connections
3232
## **Setup Testsigma Tunnel Using Docker**
3333
1. Create a **docker-compose.yml** file in your project directory with the following content:
3434

35+
US Region:
36+
3537
```yaml
3638
services:
3739
testsigma-tunnel:
@@ -45,6 +47,35 @@ Setting up Testsigma Tunnel with Docker ensures secure and reliable connections
4547
- VERBOSE=true/false
4648
```
4749
50+
IN Region:
51+
52+
```yaml
53+
services:
54+
testsigma-tunnel:
55+
image: testsigmainc/testsigma-tunnel-in:<arm64/amd64>-latest
56+
container_name: testsigma-tunnel
57+
environment:
58+
- KEY=<API_KEY>
59+
- TUNNEL_NAME=<NAME_OF_TUNNEL>
60+
- CONNECTIONS=<NUMBER>
61+
- INACTIVE_TIMEOUT=<NUMBER in seconds>
62+
- VERBOSE=true/false
63+
```
64+
65+
EU Region:
66+
67+
```yaml
68+
services:
69+
testsigma-tunnel:
70+
image: testsigmainc/testsigma-tunnel-eu:<arm64/amd64>-latest
71+
container_name: testsigma-tunnel
72+
environment:
73+
- KEY=<API_KEY>
74+
- TUNNEL_NAME=<NAME_OF_TUNNEL>
75+
- CONNECTIONS=<NUMBER>
76+
- INACTIVE_TIMEOUT=<NUMBER in seconds>
77+
- VERBOSE=true/false
78+
```
4879
2. Replace the placeholder values in the **docker-compose.yml** file:
4980
- **&lt;API\_KEY&gt;:** Your Testsigma authentication key.
5081
- **&lt;NAME\_OF\_TUNNEL&gt;:** The name of your tunnel.

0 commit comments

Comments
 (0)