4 >Troubleshooting</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy Frequently Asked Questions"
11 HREF="index.html"><LINK
14 HREF="misc.html"><LINK
16 TITLE="Contacting the developers, Bug Reporting and Feature Requests"
17 HREF="contact.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy Frequently Asked Questions</TH
74 >5. Troubleshooting</A
82 >5.1. I just upgraded and am getting <SPAN
84 >"connection refused"</SPAN
86 with every web page?</A
92 > is not running, or your
93 browser is configured for a different port than what
107 default. This has been changed to port 8118 now, due to a conflict
108 with NAS (Network Audio Service), which uses port 8000. If you haven't,
109 you need to change your browser to the new port number, or alternately
115 >"listen-address"</SPAN
132 >5.2. I just added a new rule, but the steenkin ad is
133 still getting through. How?</A
136 > If the ad had been displayed before you added its URL, it will probably be
137 held in the browser's cache for some time, so it will be displayed without
138 the need for any request to the server, and <SPAN
142 will not be in the picture. The best thing to do is try flushing the browser's
143 caches. And then try again.</P
145 > If this doesn't help, you probably have an error in the rule you
146 applied. Try pasting the full URL of the offending ad into <A
147 HREF="http://config.privoxy.org/show-url-info"
149 >http://config.privoxy.org/show-url-info</A
151 and see if any actions match your new rule.</P
159 >5.3. One of my favorite sites does not work with <SPAN
166 > First verify that it is indeed a <SPAN
173 > filtering and blocking.
181 >"Toggle Privoxy On or Off"</SPAN
182 >, then disable it. Now try that
183 page again. It's probably a good idea to flush the browser cache as well.</P
185 > If still a problem, go to <SPAN
187 >"Show which actions apply to a URL and
194 the full URL of the page in question into the prompt. See which actions are
195 being applied to the URL. Now, armed with this information, go to <SPAN
198 the actions list"</SPAN
199 >. Here you should see various sections that have
203 > features disabled for specific
204 sites. Most disabled <SPAN
211 sign) in front of them. Some aliases are used just to disable other actions,
218 >, and won't necessarily
225 > sign. Add your problem page
226 URL to one of these sections that looks like it is disabling the feature that
227 is causing the problem. Rember to flush your browser's caches when making
228 such changes! As a last resort, try <SPAN
232 disables most actions. Now re-try the page. There might be some trial and
233 error involved. This is discussed in a little more detail in the <A
234 HREF="../user-manual/appendix.html#ACTIONSANAT"
236 >user-manual appendix</A
239 > Alternately, if you are comfortable with a text editor, you can accomplish
240 the same thing by editing the appropriate <SPAN
251 >5.4. What time is it?</A
254 > Time for you to go!</P
307 >Contacting the developers, Bug Reporting and Feature Requests</TD