PostHog / PostHog/HouseWatch

fist time running HouseWatch

Open
#80 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
631
Forks
45
PR merge metrics
No merged PRs in 30d

Description

Hi i was try to run docker compose -f docker-compose.dev.yml up -d to up a local housewatch but when i go to my localhost:8080 it :"This site can’t be reached" and my log get error in caddy {"level":"error","ts":1745485280.0292118,"logger":"http.log.error","msg":"dial tcp: lookup web on 127.0.0.11:53: server misbehaving","request":{"remote_ip":"172.18.0.1","remote_port":"49322","proto":"HTTP/1.1","method":"GET","host":"localhost:8080","uri":"/","headers":{"Accept-Encoding":["gzip, deflate, br, zstd"],"Cache-Control":["max-age=0"],"Accept-Language":["vi-VN,vi;q=0.9,en-US;q=0.8,en;q=0.7"],"Sec-Fetch-Mode":["navigate"],"Sec-Fetch-User":["?1"],"Sec-Fetch-Dest":["document"],"Sec-Ch-Ua":[""Chromium";v="134", "Not:A-Brand";v="24", "Google Chrome";v="134""],"Sec-Ch-Ua-Platform":[""Linux""],"Upgrade-Insecure-Requests":["1"],"User-Agent":["Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"],"Cookie":[],"Connection":["keep-alive"],"Sec-Ch-Ua-Mobile":["?0"],"Accept":["text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.7"],"Sec-Fetch-Site":["none"]}},"duration":0.000935551,"status":502,"err_id":"2b4a90ja0","err_trace":"reverseproxy.statusError (reverseproxy.go:1271)"}
it seem like my housewatch web it not up i try to docker ps -a
and print the log of housewatch web it said this "Serve the files from /frontend/build, don't run this container directly"
i have go to frontend and try to build it fist but nothing happen still the same error

Contributor guide

No contributing guide indexed for this repository

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 docker-compose.dev.yml and inspect the web service and Caddy configuration. Reproduce the issue with the documented compose command, then review the web container logs and the frontend directory, including the expected /frontend/build output. Done means the local stack starts successfully and localhost:8080 serves HouseWatch without the Caddy 502 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
build-system, 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.