projectdiscovery / projectdiscovery/interactsh-web

Environment Variables Not Being Applied in interactsh-web

Open
#172 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Bug
Dominant language
TypeScript
Stars
244
Forks
78
PR merge metrics
No merged PRs in 30d

Description

Issue: Environment Variables Not Auto-Applied in interactsh-web
Description

The environment variables provided to the interactsh-web container (e.g., REACT_APP_HOST, REACT_APP_TOKEN) are not automatically applied to the web interface. Despite being set via docker run as -e options, these variables are not used by the application, and the user is required to manually input them in the "Custom Host" section of the GUI.

Steps to Reproduce
  1. Run the interactsh-web Docker container with the following command:

    docker run -it -p 3000:3000 \
      -e REACT_APP_HOST="example.com" \
      -e REACT_APP_TOKEN="123456789abcdef123456789abcdef123456789abcdef123456789abcdef" \
      projectdiscovery/interactsh-web
    
  2. Open the web interface in your browser at http://localhost:3000.

  3. Attempt to use the application without entering any configuration manually.

Expected Behavior

The application should automatically use the provided environment variables:

  • REACT_APP_HOST="example.com"
  • REACT_APP_TOKEN="123456789abcdef123456789abcdef123456789abcdef123456789abcdef"

These values should be pre-filled or directly applied without the need for manual input in the "Custom Host" field in the GUI.

Actual Behavior

The application does not apply the provided environment variables. Instead:

  • The user is required to manually input the REACT_APP_HOST and REACT_APP_TOKEN values in the "Custom Host" section for the application to function correctly.
Environment
  • Docker Image: projectdiscovery/interactsh-web
  • Version: latest
  • Host System: Windows 11 (Docker Desktop)
  • Browser: Chrome

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 the Docker image startup or build configuration and the GUI's Custom Host flow, using the reproduction command and REACT_APP_HOST and REACT_APP_TOKEN values as the entry point. Done means those values are automatically pre-filled or applied when the container starts, without manual input in the interface.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, react, typescript
Domain
devops, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.