There are several possibilities:
Privoxy is installed correctly, has not crashed, and is indeed running. - Look at Privoxy's logs to see what they say.
logging, and look at the logs to see what they say.5.2. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?5.2. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?
More than likely this is a problem with your TCP/IP networking. ZoneAlarm has been reported to cause this symptom -- even if not running! The solution is @@ -160,10 +163,10 @@ CLASS="SECT2" >
If the ad had been displayed before you added its URL, it will probably be held in the browser's cache for some time, so it will be displayed without @@ -188,7 +191,8 @@ TARGET="_top" find the correct URL by looking at Privoxy's logs.
logs + (you may need to enable logging in the main config file if its disabled).Below is a slightly modified real-life log snippet that originates with one requested URL: 5.4. One of my favorite sites does not work with Privoxy. -What can I do?
First verify that it is indeed a http://config.privoxy.org/toggle, +> + (the toggle feature may need to be enabled in the main + config), and then shift-reloading the problem page (i.e. holding down the shift key while clicking reload. Alternatively, flush your browser's disk and memory caches).
5.5. After installing Privoxy, I have to log in -every time I start IE. What gives? This is a quirk that effects the installation of
5.6. I cannot connect to any FTP sites. Privoxy
- is blocking me. Microsoft Internet Explorer (in versions like 5.1) respects system-wide
network settings. In order to change the HTTP proxy, open System
@@ -523,17 +533,20 @@ CLASS="SECT2"
> Note: This ONLY applies to privoxy 3.0.6 and earlier.
+ Just dragging the Privoxy folder to the trash is
- not enough to delete it. Privoxy supplies an
@@ -541,11 +554,11 @@ CLASS="APPLICATION"
CLASS="APPLICATION"
>uninstall.command We believe this is due to an IPv6-related bug in OSX, but don't fully
+> We believe this is due to an IPv6-related bug in Mac OS X, but don't fully
understand the issue yet. In any case, changing the proxy setting to
5.10. I get a completely blank page at one site. "View Source"<html><body></body></html>5.7. In Mac OSX, I can't configure Microsoft Internet Explorer to use
- Privoxy as the HTTP proxy.
5.7. In Mac OS X, I can't configure Microsoft Internet Explorer to use
+ Privoxy as the HTTP proxy.5.8. In Mac OSX, I dragged the Privoxy folder to the trash in order to
- uninstall it. Now the finder tells me I don't have sufficient privileges to
- empty the trash.
5.8. In Mac OS X, I dragged the Privoxy folder to the trash in order to
+ uninstall it. Now the finder tells me I don't have sufficient privileges to
+ empty the trash.5.9. In Mac OSX Panther (10.3), images often fail to load and/or I
+NAME="MACOSXIMAGES"
+>5.9. In Mac OS X Panther (10.3), images often fail to load and/or I
experience random delays in page loading. I'm using
localhost as my browser's proxy setting.
as my browser's proxy setting.
Chances are that the site suffers from a bug in 5.11. My logs show many "Unable to get my own hostname" lines. -Why?
This can be caused by a problem with the local HOSTShosts
file. If this file has been changed from the original, try reverting it to
see if that helps. Make sure whatever name(s) are used for the local system,
that they resolve both ways. You should also be able to work around the problem with the
+ hostname option.
Port 8118 is 5.13. Pages with UTF-8 fonts are garbled.5.13. Pages with UTF-8 fonts are garbled. This is caused by the 5.14. Why are binary files (such as images) corrupted when Privoxy
- is used? This may also be caused by the "demoronizer" filter,
- in conjunction with a web server that is misreporting a file type. Binary
+ in conjunction with a web server that is misreporting the content type. Binary
files are exempted from Privoxy's5.15. What is the "demoronizer" and why is it there? and why is it there? The original demoronizer was a Perl script that cleaned up HTML pages which
were created with certain Microsoft products. MS has used proprietary extensions
@@ -831,7 +851,7 @@ CLASS="EMPHASIS"
>. On the other hand, if you use non-Microsoft products, and you occasionally
- notice wierd characters on pages, you might want to try it.
5.17. I am getting too many DNS errors like "404 No Such Domain". Why
- can't Privoxy do this better? There are potentially several factors here. First of all, the DNS resolution
is done by the underlying operating system -- not
@@ -899,18 +919,19 @@ CLASS="APPLICATION"
>Privoxy
In other cases, if Privoxy is being chained with another proxy, this - could complicate the issue, and cause undue +> is being chained + with another proxy, this could complicate the issue, and cause undue delays and timeouts. In the case of a "socks4a" which is reporting whatever problem occurred downstream, and not the root cause of the error.
In any case, newer versions include various improvements to help +> In any case, versions newer than 3.0.3 include various improvements to help Privoxy5.18. At one site Privoxy just hangs, and starts taking - all CPU. Why is this?
This is probably a manifestation of the Privoxy's page filtering mechanism is trying to match against absurdly long strings and this becomes - very CPU-intensive, taking a long, long time to complete. Until a better - solution comes along, disable filtering on these pages, particularly the -
Until a better solution comes along, disable filtering on these pages, + particularly the js-annoyances and and + unsolicited-popups - filters.
filters. If you run into this problem + with a recent Privoxy version, please send a problem report.This should not happen, and for the overwhelming number of users world-wide, it does not happen. I would suspect some inadvertent interaction of software components such as anti-virus software, spyware protectors, personal firewalls or similar components. Try disabling (or uninstalling) these one - at a time and see if that helps.
Privoxy version, please report the problem.It's probably due to compression. It is a common practice for web servers to send their content "uncompress" them. them. When compiled with zlib support + Privoxy does not (yet) - support compression. But we can force the web server to bend to our will ;-) - So for filtering, make sure you have can decompress content before filtering, otherwise you may want to enable +prevent-compression.
As of Privoxy 3.0.9, zlib support is enabled in the default builds.
Probably the browser is requesting ads through HTTPS and Privoxy - turned ON!
To work around the problem you can redirect those requests to an invalid + local address instead of blocking them. While the redirects aren't + encrypted either, many browsers don't care. They simply follow the + redirect, fail to reach a server and display an error message instead + of the ad.
To do that, enable logging to figure out which requests get blocked by + Privoxy and add the hosts (no path patterns) to a section like this:
{+redirect{http://127.0.0.1:0/} -block -limit-connect}
+.ivwbox.de:443/ |
Additionally you have to configure your browser to contact + "127.0.0.1:0" directly (instead of through Privoxy).
To add a proxy exception in Mozilla Firefox + open the "Preferences", click the "Settings" + button located on the "Network" tab in the "Advanced" + section, and add "127.0.0.1:0" in the "No Proxy for:" + field.
Please report the problem to the creator of your selinux policies.
The problem is that some selinux policy writers aren't familiar + with the application they are trying to "secure" and + thus create policies that make no sense.
In Privoxy's case the problem usually + is that the policy only allows outgoing connections for certain + destination ports (e.g. 80 and 443). While this may cover the + standard ports, websites occasionally use other ports as well. + This isn't a security problem and therefore Privoxy's + default configuration doesn't block these requests.
If you really want to block these ports (and don't be able + to load websites that don't use standard ports), you should + configure Privoxy to block these ports as well, so it doesn't + trigger the selinux warnings.
Probably you unintentionally compiled Privoxy without threading support + in which case requests have to be serialized and only one can be served + at the same time.
Check your "USE" flags and make sure they include + "threads". If they don't, add the flag and rebuild Privoxy.
If you compiled Privoxy with threading support (on POSIX-based systems), + the "Conditional #defines" section on http://config.privoxy.org/show-status + will list "FEATURE_PTHREAD" as "enabled".