4 >Troubleshooting</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy Frequently Asked Questions"
10 HREF="index.html"><LINK
13 HREF="misc.html"><LINK
15 TITLE="Contacting the developers, Bug Reporting and Feature Requests"
16 HREF="contact.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy Frequently Asked Questions</TH
73 >5. Troubleshooting</A
81 >5.1. I just upgraded and am getting <SPAN
83 >"connection refused"</SPAN
85 with every web page?</A
91 > is not running, or your
92 browser is configured for a different port than what
106 default. This has been changed to port 8118 now, due to a conflict
107 with NAS (Network Audio Service), which uses port 8000. If you haven't,
108 you need to change your browser to the new port number, or alternately
114 >"listen-address"</SPAN
131 >5.2. I just added a new rule, but the steenkin ad is
132 still getting through. How?</A
135 > If the ad had been displayed before you added its URL, it will probably be
136 held in the browser's cache for some time, so it will be displayed without
137 the need for any request to the server, and <SPAN
141 will not be in the picture. The best thing to do is try flushing the browser's
142 caches. And then try again.</P
144 > If this doesn't help, you probably have an error in the rule you
145 applied. Try pasting the full URL of the offending ad into <A
146 HREF="http://config.privoxy.org/show-url-info"
148 >http://config.privoxy.org/show-url-info</A
150 and see if any actions match your new rule.</P
158 >5.3. One of my favorite sites does not work with <SPAN
165 > First verify that it is indeed a <SPAN
172 > filtering and blocking.
180 >"Toggle Privoxy On or Off"</SPAN
181 >, then disable it. Now try that
182 page again. It's probably a good idea to flush the browser cache as well.</P
184 > If still a problem, go to <SPAN
186 >"Show which actions apply to a URL and
193 the full URL of the page in question into the prompt. See which actions are
194 being applied to the URL. Now, armed with this information, go to <SPAN
197 the actions list"</SPAN
198 >. Here you should see various sections that have
202 > features disabled for specific
203 sites. Most disabled <SPAN
210 sign) in front of them. Some aliases are used just to disable other actions,
217 >, and won't necessarily
224 > sign. Add your problem page
225 URL to one of these sections that looks like it is disabling the feature that
226 is causing the problem. Rember to flush your browser's caches when making
227 such changes! As a last resort, try <SPAN
231 disables most actions. Now re-try the page. There might be some trial and
232 error involved. This is discussed in a little more detail in the <A
233 HREF="../user-manual/appendix.html#ACTIONSANAT"
235 >user-manual appendix</A
238 > Alternately, if you are comfortable with a text editor, you can accomplish
239 the same thing by editing the appropriate <SPAN
250 >5.4. Where can I get help? Report bugs? Feature Requests? Etc?</A
253 > Feedback is encouraged, whether good, bad or ugly. Please see the contact
255 HREF="../user-manual/contact.html"
267 >5.5. What time is it?</A
270 > Time for you to go!</P
323 >Contacting the developers, Bug Reporting and Feature Requests</TD