# \[Solved\] Tinyproxy status page not working 2

**URL:** <https://forum.openwrt.org/t/solved-tinyproxy-status-page-not-working-2/170427>\
**Category:** Installing and Using OpenWrt\
**Created:** [September 1, 2023, 7:43pm UTC](https://forum.openwrt.org/t/solved-tinyproxy-status-page-not-working-2/170427 "2023-09-01T19:43:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![route66](https://forum.openwrt.org/letter_avatar/route66/32/5_5575768a8748004e209b776fc1b2916d.png) [@route66](https://forum.openwrt.org/u/route66)\
**Post date:** [September 1, 2023, 7:43pm UTC](https://forum.openwrt.org/t/solved-tinyproxy-status-page-not-working-2/170427/1 "2023-09-01T19:43:28Z")

</div>

With OpenWrt 22.03.5 on Netgear R7800, the status page shows this:

> Tinyproxy Status  
> Failed to retrieve statistics from url: [http://127.0.0.1:8888](http://127.0.0.1:8888/)

The issue is identical to the one reported in [OpenWrt forum thread](https://forum.openwrt.org/t/tinyproxy-status-page-not-working/19206) in 2018.

However, the 2018 solution (updating the whitelist filter file with 127.0.0.1 address) does not work.

TinyProxy config:

```plaintext
config tinyproxy
	option User 'nobody'
	option Group 'nogroup'
	option Port '8888'
	option Timeout '600'
	option DefaultErrorFile '/usr/share/tinyproxy/default.html'
	option StatFile '/usr/share/tinyproxy/stats.html'
	option LogFile '/var/log/tinyproxy.log'
	option LogLevel 'Info'
	option MaxClients '100'
	option MinSpareServers '5'
	option MaxSpareServers '20'
	option StartServers '10'
	option MaxRequestsPerChild '0'
	list ConnectPort '443'
	list ConnectPort '563'
	option enabled '1'
	option Listen '192.168.1.1'
	list Allow '127.0.0.1'
	list Allow 'localhost'
	list Allow '192.168.1.0/24'
	option FilterDefaultDeny '1'
	option Filter '/etc/tinyproxy/filter'

```

Whitelist filter:

```plaintext
^127\.0\.0\.1$
^localhost$
wikipedia\.org$

```

Any ideas for a possible fix?

---

<div class="post-metadata">

**Author:** ![pavelgl](https://forum.openwrt.org/user_avatar/forum.openwrt.org/pavelgl/32/33073_2.png) [@pavelgl](https://forum.openwrt.org/u/pavelgl)\
**Post date:** [September 2, 2023, 7:05am UTC](https://forum.openwrt.org/t/solved-tinyproxy-status-page-not-working-2/170427/2 "2023-09-02T07:05:54Z")

</div>

> [@route66](#):
>
> `option Listen '192.168.1.1'`

Currently, the service only listens on `192.168.1.1` .  
Comment out the option or change its value to `0.0.0.0` .

---

<div class="post-metadata">

**Author:** ![route66](https://forum.openwrt.org/letter_avatar/route66/32/5_5575768a8748004e209b776fc1b2916d.png) [@route66](https://forum.openwrt.org/u/route66)\
**Post date:** [September 2, 2023, 8:15am UTC](https://forum.openwrt.org/t/solved-tinyproxy-status-page-not-working-2/170427/3 "2023-09-02T08:15:46Z")

</div>

Thanks! This indeed brings back the stats page.  
Just for my understanding - why does it work? 🙂 My assumption was that the router's 192.168.1.1 is at the same time the localhost 127.0.0.1...

---

<div class="post-metadata">

**Author:** ![pavelgl](https://forum.openwrt.org/user_avatar/forum.openwrt.org/pavelgl/32/33073_2.png) [@pavelgl](https://forum.openwrt.org/u/pavelgl)\
**Post date:** [September 2, 2023, 10:15am UTC](https://forum.openwrt.org/t/solved-tinyproxy-status-page-not-working-2/170427/4 "2023-09-02T10:15:31Z")

</div>

> [@route66](#):
>
> My assumption was that the router's 192.168.1.1 is at the same time the localhost 127.0.0.1...

127.0.0.1 is a separate virtual loopback interface that is always up and running regardless of the state of the other interfaces in the system. It is used by the device to communicate with itself - mainly for diagnostics and troubleshooting or to access services running on the local machine.

If you want to access a service using the loopback interface, the service must listen on that interface.

In your case, you have restricted `tinyproxy` to only listen on the (physical) lan interface, so it was unreachable via the loopback interface.

AFAIK listing multiple listening interfaces is not supported by `tinyproxy`, so the only option is to allow the service to listen on all available interfaces

---

<div class="post-metadata">

**Author:** ![route66](https://forum.openwrt.org/letter_avatar/route66/32/5_5575768a8748004e209b776fc1b2916d.png) [@route66](https://forum.openwrt.org/u/route66)\
**Post date:** [September 2, 2023, 1:14pm UTC](https://forum.openwrt.org/t/solved-tinyproxy-status-page-not-working-2/170427/5 "2023-09-02T13:14:53Z")

</div>

Thanks a lot for explaining!

> [@pavelgl](#):
>
> AFAIK listing multiple listening interfaces is not supported by `tinyproxy`, so the only option is to allow the service to listen on all available interfaces

Indeed, only one listening interface is supported.

---

<div class="post-metadata">

**Author:** ![system](https://forum.openwrt.org/uploads/default/original/3X/7/4/740520c71f00039bbf001045c682f0ecb25e905a.png) [@system](https://forum.openwrt.org/u/system)\
**Post date:** [September 12, 2023, 1:15pm UTC](https://forum.openwrt.org/t/solved-tinyproxy-status-page-not-working-2/170427/6 "2023-09-12T13:15:49Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
