| Next | 5. Troubleshooting5. Troubleshooting
# Make exceptions for ill-behaved sites:
+ #
+ {-prevent-compression}
+ .example.com |
If that works, you may also want to report the problem to the + site's webmasters, telling them to use zlib.output_compression + instead of ob_gzhandler in their PHP applications (workaround) + or upgrade to PHP 4.2.3 or later (fix). +
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 tries to get the hostname of the system + its running on from the IP address of the system interface it is bound to + (from the config file + listen-address setting). If the system cannot supply + this information, Privoxy logs this condition.
Typically, this would be considered a minor system configuration error. It is + not a fatal error to Privoxy however, but may + result in a much slower response from Privoxy on + some platforms due to DNS timeouts.
This can be caused by a problem with the local HOSTS + file. If this file has been changed from the original, try reverting it to + see if that helps. Make sure what ever name(s) are used for the local system, + that they resolve both ways.
Port 8118 is Privoxy's default TCP + "shop" and "listening" port. Typically this message would mean that there + is already one instance of Privoxy running, and + your system is actually trying to start a second + Privoxy on the same port, which will not work. + (You can have multiple instances but they must be assigned different ports.) + How and why this might happen varies from platform to platform, but you need + to check your installation and start-up procedures.
This is caused by the "fragile", and won't necessarily - use a "demoronizer" filter. You should either + upgrade Privoxy, or at least upgrade to the most + recent default.action file available from SourceForge. + Or you can simply disable the demoronizer filter.
This may also be caused by the "+" or "demoronizer" filter, + in conjunction with a web server that is misreporting a file type. Binary + files are exempted from Privoxy's filtering + (unless the web server by mistake says the file is something else). Either + upgrade Privoxy, or go to the most recent + default.action file available from SourceForge.
The original demoronizer was a Perl script that cleaned up HTML pages which + were created with certain Microsoft products. MS has used proprietary extensions + to standardized font encodings (ISO 8859-1), which has caused problems for pages + that are viewed with non-Microsoft products (and are expecting to see a + standard set of fonts). The demoronizer corrected these errors so the pages + displayed correctly. Privoxy borrowed from this + script, introducing a filter based on the original demoronizer, which in turn could + correct these errors on the fly.
But this is only needed in some situations, and will cause serious problems in some + other situations.
If you are using Microsoft products, you do not need it. If you need to view + pages with UTF-8 characters (such as Cyrillic or Chinese), then it will + cause corruption of the fonts, and thus should not be on.
On the other hand, if you use non-Microsoft products, and you occasionally + notice wierd characters on pages, you might want to try it.
Privoxy is attempting to disable malicious + user-manual appendix.
Javascript + in this case, with the unsolicited-popups + filter. Privoxy cannot tell very well + "good" code snippets from "bad" code snippets.Alternately, if you are comfortable with a text editor, you can accomplish - the same thing by editing the appropriate If you see this in HTML source, and the page displays without problems, then + this is good, and likely some pop-up window was disabled. If you see this + where it is causing a problem, such as a downloaded program source code file, + then you should set an exception for this site or page such that the + integrity of the page stays in tact by disabling all filtering.
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 "actions" file.
"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, v. 3.0.5 includes various improvements to help + Privoxy better handle these cases.
Feedback is encouraged, whether good, bad or ugly. Please see the contact - page in the user-manual for - details.
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.Time for you to go!
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.