Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tinyproxy: Invalid config generation #25670

Open
h4ckee opened this issue Jan 3, 2025 · 0 comments
Open

Tinyproxy: Invalid config generation #25670

h4ckee opened this issue Jan 3, 2025 · 0 comments

Comments

@h4ckee
Copy link

h4ckee commented Jan 3, 2025

Maintainer: @\neheb
Environment: MediaTek MT7621 ver:1 eco:3, D-Link DIR-2660 A1, OpenWrt 23.05.5 r24106-10cc5fcd00 / LuCI openwrt-23.05 branch git-24.264.56413-c7a3562

Description:

Hi guys.
I'm using tinyproxy and noticed that when main config in /var/etc/tinyproxy.conf is being generated from /etc/config/tinyproxy it lacks http flag in this line:
upstream <ip_addr>:<port>
and hence tinyproxy fails to start

root@Router:/etc/config# /usr/bin/tinyproxy -d -c /var/etc/tinyproxy.conf
ERROR: Syntax error on line 25
Unable to parse config file. Not starting.
Should be upstream http <ip_addr>:<port> in order to work properly.
Tinyproxy also supports SOCKS4 and SOCKS5 so instead of http, socks{4,5} or none string could be placed there.

Also if I change upstream to Upstream in /etc/config/tinyproxy, final string in /var/etc/tinyproxy.conf is not generated at all.

Also following options are deprecated:
line 21: deprecated option FilterExtended, use FilterType

option MinSpareServers 5
option MaxSpareServers 20
option StartServers 10
option MaxRequestsPerChild 0


I've changed these lines in /etc/init.d/tinyproxy and everything works fine

        [ "$type" = "proxy" ] && [ -n "$via" ] && \
                echo "Upstream http $via$target"

But it should be fixed in the package itself.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant