OWASP / OWASP/crAPI

localhost:8888 is unreachable

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

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
1.6k
Forks
645
Avg merge
37m
Merged PRs (30d)
1

Description

I can't reach localhost:8888 but I can reach localhost:8025. what is the solution to this problem?

Also when I checked the health of the containers, I am seeing that crapi identity is exited 1 minute ago
Is there anyone who experienced this trouble?

I checked the crapi-identity container's logs and the first issue is PostgreSQL FATAL: database "crapi" does not exist.
In addition: I have got 3 containers that are alive.

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 crapi-identity container health status and its logs, focusing on the PostgreSQL error that the "crapi" database does not exist. Compare the containers that are alive with the unreachable localhost:8888 and reachable localhost:8025 endpoints. Done means the cause of the exited container and the endpoint failure is identified and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql
Domain
databases, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.