# HTTPS still work, Proof

**URL:** <https://forum.grin.mw/t/https-still-work-proof/8370>\
**Category:** Development and Technical Discussion\
**Created:** [February 5, 2021, 7:04pm UTC](https://forum.grin.mw/t/https-still-work-proof/8370 "2021-02-05T19:04:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![levus](https://avatars.discourse-cdn.com/v4/letter/l/fbc32d/32.png) [@levus](https://forum.grin.mw/u/levus)\
**Post date:** [February 5, 2021, 7:04pm UTC](https://forum.grin.mw/t/https-still-work-proof/8370/1 "2021-02-05T19:04:03Z")

</div>

> <https://twitter.com/MWgrin_fr/status/1357755070478245889>

Any idea?

---

<div class="post-metadata">

**Author:** ![kbs1](https://avatars.discourse-cdn.com/v4/letter/k/cdc98d/32.png) [@kbs1](https://forum.grin.mw/u/kbs1)\
**Post date:** [February 7, 2021, 3:18am UTC](https://forum.grin.mw/t/https-still-work-proof/8370/2 "2021-02-07T03:18:00Z")

</div>

HTTP(S) can still easily work if one uses any sort of “proxy” like `nginx` or `socat`. Grin will listen on `localhost` only, but it can’t stop other programs from listening on `0.0.0.0`, accepting all connections and forwarding that to `grin-wallet` over `localhost`.

---

<div class="post-metadata">

**Author:** ![Elephantul](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/elephantul/32/3910_2.png) [@Elephantul](https://forum.grin.mw/u/Elephantul)\
**Post date:** [February 7, 2021, 6:57am UTC](https://forum.grin.mw/t/https-still-work-proof/8370/3 "2021-02-07T06:57:42Z")

</div>

Grin act in misterious ways … is unstopable