mitre-attack / mitre-attack/attack-workbench-frontend
[BUG] - Bad Gateway
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
Describe the bug
When deploying the containers you can see on the screen that an error occurs related to the 502 bad Gateway status code.
Expected behavior
Based on the fact that this tool can be used in productive environments and if one develops a DB with specific threat information, this can impact availability.
To Play
Steps to reproduce the behavior:
- cd /path/workbech
- sudo docker-compose up -d
Screenshots
Additional context
You are using the most recent version of Ubuntu Desktop.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the deployment with sudo docker-compose up -d on Ubuntu Desktop, then inspect the container output and logs around the 502 response. Done means the containers start successfully and the application is reachable without a Bad Gateway error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, docker, docker-compose, typescript, ubuntu
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100