Either There are several possibilities:
Privoxy is not running, or your - browser is configured for a different port than what - is not running. Solution: verify + that Privoxy is using.
is installed correctly, has not crashed, and is indeed running. + Turn on Privoxy's logging, and look at the logs to see what they say.The old Or your browser is configured for a different port than what + Privoxy (and also - is using. Solution: verify that Junkbuster) used port 8000 by - default. This has been changed to port 8118 now, due to a conflict - with NAS (Network Audio Service), which uses port 8000. If you haven't, - you need to change your browser to the new port number, or alternately - change the listen-addressPrivoxy - option in Privoxy's main configuration file.
listen-address).Or if using a forwarding rule, you have a configuration problem or a + problem with a host in the forwarding chain. Solution: temporarily alter your + configuration and take the forwarders out of the equation.
Or you have a firewall that is interfering and blocking you. Solution: + try disabling or removing the firewall as a simple test. +
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 + to either fight the ZA configuration, or uninstall ZoneAlarm, and then find + something better behaved in its place. Other personal firewall type products + may cause similar type problems if not configured correctly. +
Privoxy - will not be in the picture. The best thing to do is try flushing the browser's - caches. And then try again.
If this doesn't help, you probably have an error in the rule you applied. Try pasting the full URL of the offending ad into http://config.privoxy.org/show-url-info - and see if it really matches your new rule.
Privoxy's 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: www.example.com (name of site was changed + for this example, the number of requests is real). You can see in this the + complexity of what goes into making up this one "page". There + are eight different domains involved here, with thirty two separate URLs + requested in all, making up all manner of images, Shockwave Flash, + JavaScript, CSS stylesheets, scripts, and other related content. Some of this + content is obviously "good" or "bad", but not all. + Many of the more questionable looking requests, are going to outside domains + that seem to be identifying themselves with suspicious looking names, making + our job a little easier. Privoxy has "crunched" (meaning caught + and BLOCKED) quite a few items in this example, but perhaps missed a few as well.
Request: www.example.com/ +Request: www.example.com/favicon.ico +Request: img.example.com/main.css +Request: img.example.com/sr.js +Request: example.betamarker.com/example.html +Request: www.lik-sang.com/Banners/bestsellers/skyscraper.php?likref=BSellers +Request: img.example.com/pb.png +Request: www.google-analytics.com/urchin.js crunch! (Blocked) +Request: www.advertising-department.com/ats/switch.ps.php?26856 crunch! (Blocked) +Request: img.example.com/p.gif +Request: www.popuptraffic.com/assign.php?l=example&mode=behind crunch! (Blocked) +Request: www.popuptraffic.com/scripts/popup.php?hid=5c3cf&tmpl=PBa.tmpl crunch! (Blocked) +Request: www.popuptraffic.com/assign.php?l=example crunch! (Blocked) +Request: www.lik-sang.com/Banners/best_sellers/best_sellers.css +Request: www.adtrak.net/adx.js crunch! (Blocked) +Request: img.example.com/hbg.gif +Request: img.example.com/example.jpg +Request: img.example.com/mt.png +Request: img.example.com/mm.png +Request: img.example.com/mb.png +Request: www.popuptraffic.com/scripts/popup.php?hid=a71b91fa5&tmpl=Ua.tmp crunch! (Blocked) +Request: www.example.com/tracker.js +Request: www.lik-sang.com/Banners/best_sellers/lsi_head.gif +Request: www.adtrak.net/adjs.php?n=020548130&what=zone:61 crunch! (Blocked) +Request: www.adtrak.net/adjs.php?n=463594413&what=zone:58&source=Ua crunch! (Blocked) +Request: www.lik-sang.com/Banners/best_sellers/bottomani.swf +Request: mmm.elitemediagroup.net/install.php?allowpop=no&popupmincook=0&allowsp2=1 crunch! (Blocked) +Request: www.example.com/tracker.js?screen=1400x1050&win=962x693 +Request: www.adtrak.net/adlog.php?bannerid=1309&clientid=439&zoneid=61 crunch! (Blocked) +Request: 66.70.21.80/scripts/click.php?hid=5c3cf599a9efd0320d26&si +Request: 66.70.21.80/img/pixel.gif +Request: www.adtrak.net/adlog.php?bannerid=1309&clientid=439&zoneid=58&source=Ua&block=86400 crunch! (Blocked) +Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua |
Despite 12 out of 32 requests being blocked, the page looked, and seemed to + behave perfectly "normal" (minus some ads, of course).
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).
If still a problem, go to If the problem went away, we know we have a configuration related problem. + Now go to http://config.privoxy.org/show-url-info - and paste the full URL of the page in question into the prompt. See which actions - are being applied to the URL, and which matches in which actions files are - responsible for that. Now, armed with this information, go to required. + Now, armed with this information, go to + http://config.privoxy.org/show-status - and select the appropriate actions files for editing.
You can now either look for a section which disables the actions that you suspect to cause the problem and add a pattern for your site there, @@ -208,9 +347,9 @@ TARGET="_top" > Alternately, if you are comfortable with a text editor, you can accomplish the same thing by editing the appropriate actions file. Probably the easiest way to deal with such problems when editing by hand is to add your - site to a { fragile }{ fragile } section in user.action Troubleshooting actions is discussed in more detail in the user-manual appendixUser Manual appendix, + Troubleshooting: the Anatomy of an Action. There is also an actions tutorial.
+ with general configuration information and examples.As a last resort, you can always see if your browser has a setting that will + bypass the proxy setting for selective sites. Modern browsers can do this.
5.5. I cannot connect to any FTP sites. Privoxy - seems to be blocking me.5.6. I cannot connect to any FTP sites. Privoxy + is blocking me.
any protocol other than HTTP - or HTTPS.
Most browsers understand FTP as well as HTTP. If you connect to a site, with - a URL like ftp://ftp.example.comftp://ftp.example.com, your browser is making an FTP connection, and not a HTTP connection. So while your browser may speak FTP, "proxy" - setting, which will silently enable both HTTP and FTP - proxying! So it is possible to accidentally enable FTP proxying in these - cases. And of course, if this happens, HTTP and FTP proxying! So it is possible to + accidentally enable FTP proxying in these cases. And of course, if this + happens, Privoxy - will indeed cause problems since it does not know FTP. +> will indeed cause problems since + it does not know FTP. Newer version will give a sane error + message if a FTP connection is attempted. Just disable the FTP setting + and all will be well again.
Will Microsoft Internet Explorer (in versions like 5.1) respects system-wide
network settings. In order to change the HTTP proxy, open System
Preferences, and click on the Network icon. In the settings pane that
comes up, click on the Proxies tab. Ensure the "Web Proxy (HTTP)" checkbox
- is checked and enter 127.0.0.1127.0.0.1 in the entry field.
- Enter 81188118 in the Port field. The next time you start
IE, it should reflect these values.
Just dragging the Note: This ONLY applies to privoxy 3.0.6 and earlier.
+ Just dragging the Privoxy folder to the trash is
@@ -430,23 +571,23 @@ CLASS="SECT2"
> 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
- 127.0.0.1 instead of 127.0.0.1 instead of localhostlocalhost
works around the problem.
Chances are that the site suffers from a bug in
@@ -489,9 +627,9 @@ CLASS="APPLICATION"
To find out if this is in fact the source of the problem, try adding
- the site to a -prevent-compression-prevent-compression section in
More than likely this is a problem with the network stack. ZoneAlarm has
- been reported to cause this symptom -- even if not running. The solution is
- to either fight the ZA configuration, or uninstall ZoneAlarm, and then find
- something better behaved in its place. Other firewall type products may
- cause similar type problems if not configured correctly.
- 5.6. 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.7. In Mac OSX, I dragged the Privoxy folder to the trash in order to
+NAME="MACOSXUNINSTALL"
+>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.8. 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
- localhostlocalhost as my browser's proxy setting.
5.10. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?
"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's filtering - (unless the web server by mistake says the file is a plain text file). Either + (unless the web server by mistake says the file is something else). Either upgrade Privoxy.On the other hand, if you use non-Microsoft products, and you occasionally - notice wierd characters on pages, you might want to try it.
This filter was introduced with version 3.0.2 of Privoxy, - and was on by default in that version. It is off in all subsequent versions - (unless turned on by the user).
There are potentially several factors here. First of all, the DNS resolution + is done by the underlying operating system -- not + Privoxy itself. Privoxy + merely initiates the process and hands it off, and then later reports + whatever the outcome was. And tries to give a coherent message if there seems + to be a problem. In some cases, this might otherwise be mitigated by the + browser itself which might try some work-arounds and alternate approaches (e.g + adding "www." to the URL).
In other cases, if Privoxy is being chained + with another proxy, this could complicate the issue, and cause undue + delays and timeouts. In the case of a "socks4a" proxy, the socks + server handles all the DNS. Privoxy would just be + the "messenger" which is reporting whatever problem occurred + downstream, and not the root cause of the error.
In any case, versions newer than 3.0.3 include various improvements to help + Privoxy better handle these cases.
This is probably a manifestation of the "100% cpu" problem that + occurs on pages containing many (thousands upon thousands) of blank lines. The blank lines + are in the raw HTML source of the page, and the browser just ignores them. But the + pattern matching in 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 + js-annoyances and unsolicited-popups + filters.
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.
It's probably due to compression. It is a common practice for web servers to + send their content "compressed" in order to speed things up, and + then let the browser "uncompress" them. When compiled with zlib support + Privoxy can decompress content before filtering, otherwise you may want to enable +prevent-compression.