pingdotgg / pingdotgg/t3code

[Bug]: Browser capture fails when adding an attachment from a page accessed through a VPS port tunnel

Open
#11,404 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Area

T3 Code built-in browser / attachment capture

Steps to reproduce
  1. Run a web page on a VPS.
  2. Tunnel the port from the VPS to the local machine.
  3. Open the page through the tunneled port in T3 Code's built-in browser.
  4. Try to capture the page to add it as an attachment.
Expected behavior

The page is captured and added as an attachment.

Actual behavior

T3 Code shows "Capture failed", and the capture cannot be added as an attachment.

Impact

Unable to add a browser capture as an attachment in this setup.

Environment

Page hosted on a VPS and accessed through a tunneled port in T3 Code's built-in browser. Exact T3 Code version, OS, and tunnel configuration have not been provided.

Related issue

Possibly related to #10366, which describes element-picker screenshot capture failures on a local page. This report involves a page accessed through a VPS port tunnel and the error "Capture failed"; it is not yet clear whether the underlying cause is the same.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with T3 Code's built-in browser attachment-capture flow and compare the behavior with related issue #10366. Reproduce the VPS port-tunnel setup, then verify that the page capture succeeds and is added as an attachment without showing "Capture failed".

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.