Skip to content

Added a new FAQ and updated an existing doc #887

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
bharathk08 merged 1 commit into from
Dec 19, 2025
Merged

Added a new FAQ and updated an existing doc #887

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
44 changes: 44 additions & 0 deletions ...apps/how-do-i-fix-the-try-again-error-when-opening-the-testsigma-desktop-app.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
---
title: "How Do I Fix the Try Again Error When Opening the Testsigma Desktop App?"
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."
order: 24.21
page_id: "how-do-i-fix-the-try-again-error-when-opening-the-testsigma-desktop-app"
warning: false
contextual_links:
- type: section
name: "Contents"
- type: link
name: "Steps to Resolve the Permission Issue"
url: "#steps-to-resolve-the-permission-issue"
---

---

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.

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.

![Try Again](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/chrome_138.1.png)
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Update image filenames to match Chrome 139+ documentation context.

The document discusses Chrome 139+ (lines 17–19), but both image filenames reference Chrome 138:

  • Line 21: chrome_138.1.png
  • Line 34: chrome_138.png

If these screenshots were taken from an older browser version, consider renaming them to chrome_139.1.png and chrome_139.png for consistency. If the filenames are intentional (e.g., due to S3 bucket constraints), update the surrounding text to clarify which browser version the screenshots represent.

Also applies to: 34-34

🤖 Prompt for AI Agents 
In
src/pages/docs/FAQs/web-apps/how-do-i-fix-the-try-again-error-when-opening-the-testsigma-desktop-app.md
around lines 21 and 34, the embedded screenshot filenames reference Chrome 138
while the text refers to Chrome 139+; update the assets and references so they
match: either rename the image files in S3 to chrome_139.1.png and
chrome_139.png and update the markdown links accordingly, or keep the existing
filenames but change the surrounding copy to explicitly state that the
screenshots are from Chrome 138 to avoid confusion.


This article discusses how to resolve the permission issue.

---

## **Steps to Resolve the Permission Issue**

1. In **Chrome**, click the **Site Information** icon in the address bar.

2. Ensure the following permissions are set to **Allow**:
- **Pop-ups and redirects**
- **Local network access**
![Permissions](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/faq/chrome_138.png)

3. If these permissions were previously denied, click **Reset permissions**.

4. Refresh the page.

5. Click **Open the desktop app** again in Testsigma.

6. When **Chrome** displays the permission prompt, click **Allow** or **Open** to proceed with launching the desktop application.

---
31 changes: 31 additions & 0 deletions src/pages/docs/testsigma-tunnel/setup-installation-docker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,8 @@ Setting up Testsigma Tunnel with Docker ensures secure and reliable connections
## **Setup Testsigma Tunnel Using Docker**
1. Create a **docker-compose.yml** file in your project directory with the following content:

US Region:

```yaml
services:
testsigma-tunnel:
Expand All @@ -45,6 +47,35 @@ Setting up Testsigma Tunnel with Docker ensures secure and reliable connections
- VERBOSE=true/false
```

IN Region:

```yaml
services:
testsigma-tunnel:
image: testsigmainc/testsigma-tunnel-in:<arm64/amd64>-latest
container_name: testsigma-tunnel
environment:
- KEY=<API_KEY>
- TUNNEL_NAME=<NAME_OF_TUNNEL>
- CONNECTIONS=<NUMBER>
- INACTIVE_TIMEOUT=<NUMBER in seconds>
- VERBOSE=true/false
```

EU Region:

```yaml
services:
testsigma-tunnel:
image: testsigmainc/testsigma-tunnel-eu:<arm64/amd64>-latest
container_name: testsigma-tunnel
environment:
- KEY=<API_KEY>
- TUNNEL_NAME=<NAME_OF_TUNNEL>
- CONNECTIONS=<NUMBER>
- INACTIVE_TIMEOUT=<NUMBER in seconds>
- VERBOSE=true/false
```
2. Replace the placeholder values in the **docker-compose.yml** file:
- **&lt;API\_KEY&gt;:** Your Testsigma authentication key.
- **&lt;NAME\_OF\_TUNNEL&gt;:** The name of your tunnel.
Expand Down