OpenWrt Forum Archive

Topic: Help setting up Privoxy

The content of this topic has been archived on 14 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I followed the instructions below to install Privoxy on my router:

http://wiki.openwrt.org/doc/howto/proxy.privoxy

The installation and configuration went fine. I only changed the listen address (192.168.1.1:8118), nothing else.

I can't log in to the Privoxy web interface using the above IP address. When I try I get the error "Invalid header received from client.". Also, if I add the proxy settings to my browser I am unable to bring up any web pages ("proxy not found" error). I don't have any other proxies or anything else for that matter running.

I verified that Privoxy is running with netstat......and now I'm officially out of ideas. I'm running Backfire final, if that matters at all.

Thoughts?

I had problems with Privoxy on Backfire. Privoxy would crash repeatedly. I'd recommend upgrading to Attitude Adjustment.

adam2104 wrote:

I had problems with Privoxy on Backfire. Privoxy would crash repeatedly. I'd recommend upgrading to Attitude Adjustment.

I was using AA before but I had issues with it random reboots and poor wireless throughput. Backfire has been rock solid for me.

See, the problem with that, is that you moved to an old version of software. Now, because of whatever reboot problems you had, you've now stuck on Backfire. Forever. It would be much better to move to a newer version, perhaps Trunk, to see if your reboot problems stop.

Privoxy doesn't run right on Backfire.

Stuck how? I could always update (again) to AA. Also, I'm aware that I could try trunk as well, but I admit that resolving complex issues (such as the reboots, poor wireless throughput, etc) are beyond my skillset. It was much less hassle for to just downgrade and be done with it (also, so the GF would stop complaining about the WiFi lol).

(Last edited by sirchuckoftron on 10 Mar 2013, 17:23)

It's a minor bug, disregard it. Privoxy for BF seems to be broken, but only for web access.

I've just wasted like 6 hours, but if you setup 80->8118 (or whatever your port is) and enable forwarded requests, it works.

Trying to GET into web access sends privoxy into infinite loop (or recursion), seems like it re-requests 192.168.1.1:8118.
If you don't go to web access and set it up using config, it works.

The discussion might have continued from here.