# Thinlinc listen address
**URL:** https://community.thinlinc.com/t/thinlinc-listen-address/631
**Category:** Community Support
**Created:** [15 June 2023 10:32 UTC](https://community.thinlinc.com/t/thinlinc-listen-address/631 "2023-06-15T10:32:44Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@penguin2020](https://community.thinlinc.com/u/penguin2020)
#### Post date: [15 June 2023 10:32 UTC](https://community.thinlinc.com/t/thinlinc-listen-address/631/1 "2023-06-15T10:32:44Z")
Hi guys,
First of all, great software, I’ve been using it for some while now without any real issues.
I’ve dug into the documentation and underlying code that comprises Thinlinc, but I can’t seem to identify any configuration that relates to the listen address; by default Thinlinc (webaccess at least) listens on 0.0.0.0 and I’m wondering if there’s a way to configure it to listen on 127.0.0.1 so it makes reverse proxying (e.g., nginx) easier without a firewall.
Thanks!
---
### Author:  [@martin](https://community.thinlinc.com/u/martin)
#### Post date: [16 June 2023 06:49 UTC](https://community.thinlinc.com/t/thinlinc-listen-address/631/2 "2023-06-16T06:49:12Z")
Hello @penguin2020
No, it’s not possible to configure webaccess to bind to anything other than 0.0.0.0.
Kind regards,
Martin
---
### Author:  [@penguin2020](https://community.thinlinc.com/u/penguin2020)
#### Post date: [16 June 2023 07:59 UTC](https://community.thinlinc.com/t/thinlinc-listen-address/631/3 "2023-06-16T07:59:43Z")
Hi @martin,
Thanks for replying to my question. I know it’s besides the scope of the question, but is there any technical reasoning for this? I know that instead of webaccess I can just use any of the deskop clients and have a thinlinc session via ssh which is quite secure, but I’m just curious since I really enjoy the HTML5 client.
Thanks!
---
### Author:  [@martin](https://community.thinlinc.com/u/martin)
#### Post date: [20 June 2023 06:53 UTC](https://community.thinlinc.com/t/thinlinc-listen-address/631/4 "2023-06-20T06:53:58Z")
Hello,
The reasoning behind not having it configurable is that it introduces unnecessary complexity. From an administrative perspective, it’s best configured with firewall policies.
Regards,
Martin