Tess B.
Runs a small IT shop's network and a homelab that is too big. Interested in monitors, laptops, monitoring.
- Reputation
- 54
- Topics
- 0
- Posts
- 7
- Solutions
- 1
- Joined
- 19 October 2025
A few observations. My classic: app listening on 127.0.0.1:3000 in one place, proxy pass http://localhost:3000 in nginx, and localhost resolving to ::1 first. app only bound IPv4, so connection refused. use the explicit IP in proxy pass…
ehh not every unused gadget is a failure, sometimes you learn what you don't want, and that's worth smth.
ok update: did what @caleb.moreau said and its fine now u guys are the best!!!
oof for me it was the settings, swapped it and boom, fixed. reading this at 2am instead of sleeping, no regrets
would you buy it again knowing what u know now?
@elena mutex thank u this worked!!
hmmmm quick q dumb question but how do i even check the firmware