[Solved] PRIVOXY not working / being used

This forum is for all copfilter support related questions in English.
moshari_3
Posts: 152
Joined: 07 Apr 2010 03:43
Location: Australia

[Solved] PRIVOXY not working / being used

Post by moshari_3 » 18 Apr 2010 09:43

Hi guys,

Somehow I have managed to break Privoxy. When I click on the privoxy configuration link from the Copfilter HTTP Scanning page I get redirected to privoxy.org/config/ which basically says Privoxy is not being used.
I have read the links & the manuals but unfortunately it's either mostly over my head or did not seem appropriate. (LOL Like I can really tell)

Unfortunately I think I broke it a long time ago soon after initial installation but I didn't realize until the last couple of days it was more than just not being able to access the configuration page.
For example if I goto a virus infect page it does not get blocked but through another IPC set up the same way it does get blocked & redirects to the havp virus warning page.
Also on this non-functional IPC the URL filter will give me it's standard block page & not the havp page instead but on a working system it gives the havp server down generated page.

I forgot to mention that Adv-Proxy is running in transparent mode.

The current configuration is:
Linux Kernel = 2.4.36 - IPCop = 1.4.21 - Advanced Proxy = 3.0.5 - URL Filter = 1.9.3 - Copfilter = 0.84beta4 with Monit = 5.0.3 - P3scan = 2.3.2 - proxsmtpd = 1.8 (not used) - HAVP = 0.91
privoxy = 3.0.10 - frox = 0.7.18 - SpamAssasin = 3.2.5 - ClamAV = 0.96/10711 - F-PROT = 6.2.1.4252 - Renattach = 1.2.4 - Rules De Juor = 1.30

I'm sorry I don't know what other information I give to be more helpful.
As I stated in my previous post my skills are very limited with Linux so please be patient with me & as specific as possible on locations of info I need to collect.

A second question which is remotely related but is there a way to get URL filter to redirect blacklisted content to the havp blacklist bocked page when it is working properly instead of the server down page?
The option I have been using is to re-direct to an external hosted page that is a little more informative & accurate than server down.

Thank you in advance for any and all help.
Last edited by moshari_3 on 12 May 2010 14:12, edited 1 time in total.

FischerM
Site Admin
Posts: 545
Joined: 09 Dec 2009 19:24
Location: Rheinbach

Re: PRIVOXY not working / being used

Post by FischerM » 18 Apr 2010 13:15

Hi!

1. Please "Restart all services" and post output.

2. Please post contents of '/var/log/copfilter/default/opt/privoxy/var/log/privoxy/logfile' (last ~50 lines)

Regards
Matthias

moshari_3
Posts: 152
Joined: 07 Apr 2010 03:43
Location: Australia

Re: PRIVOXY not working / being used

Post by moshari_3 » 19 Apr 2010 09:48

Hi Matthias, I hope I'm doing this right.

Please note that I have PROXSMTP turned off as we use pop email only and that FROX is also turned off as it was interfering with SSH login & FTP to my external web host.

From Restart all services:
Copfilter log files:

Now restarting all services

Please wait upto 2 min for messages to appear...

Restarting p3scan..
sent a HUP signal to monit waiting 1 second(s) p3scan killed
waiting 1 second(s)
p3scan is not running
No firewall rules active, p3scan mail filtering not active
starting p3scan
POP3 Traffic Scanning enabled on GREEN: eth0
POP3 Traffic Scanning enabled on BLUE: eth1
waiting 1 second(s)
p3scan is running with PID 20270
Iptables firewall rules active:

Table: nat Chain: PREROUTING 0 0 REDIRECT tcp -- eth0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 redir ports 8110
Table: nat Chain: PREROUTING 0 0 REDIRECT tcp -- eth0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:995 redir ports 8110
Table: nat Chain: PREROUTING 0 0 REDIRECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 redir ports 8110
Table: nat Chain: PREROUTING 0 0 REDIRECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:995 redir ports 8110


Restarting proxmstpd..
proxsmtpd is not running
waiting 0 second(s)
removing firewall rules
proxsmtpd is not running
No firewall rules active, proxsmtp mail filtering not active

Restarting spamd..
sent a HUP signal to monit waiting 1 second(s) spamd killed
waiting 2 second(s)
spamd is not running
changing trusted_networks parameter in local.cf to 192.xxx.xxx. 192.xxx.yyy. (NB: I have hiden the true IP's in this line)
changing required_hits parameter in local.cf to 9
not speeding up spam scan (improved recognition) by enabling razor,dcc,dns&rbl_checks
enabling rulesdujour
starting spamd
waiting 1 second(s)
spamd is running with PID 20430

Restarting clamd..
sent a HUP signal to monit waiting 1 second(s)
Waiting . clamd killed
clamd is not running
Clamav debug mode disabled
Blocking of encrypted archives is disabled

starting clamd
waiting 1 second(s)
clamd is running with PID 20470 20469 20468

Restarting havp..
reconfiguring squid in order to STOP using havp in /home/httpd/cgi-bin/proxy.cgi
reconfiguring squid in order to STOP using havp in /var/ipcop/proxy/squid.conf
reconfiguring squid..
sent a HUP signal to monit waiting 1 second(s) havp killed
waiting 2 second(s)
havp is not running
enabling clamav scanning in havp
not enabling avg scanning in havp
not enabling fprot scanning in havp
reconfiguring squid in order to use havp in /home/httpd/cgi-bin/proxy.cgi
reconfiguring squid in order to use havp in /var/ipcop/proxy/squid.conf
reconfiguring squid..
starting havp
Starting HAVP Version: 0.91 waiting 1 second(s)
havp is running with PID 20597 20596 20595 20594 ...

Restarting privoxy..
privoxy entries in /home/httpd/cgi-bin/proxy.cgi already removed
privoxy entries in /var/ipcop/proxy/squid.conf already removed
no configuration change, no squid reconfiguration required
sent a HUP signal to monit waiting 1 second(s) privoxy killed
waiting 1 second(s)
privoxy is not running
starting privoxy
waiting 1 second(s)
reconfiguring squid in order to use privoxy in /home/httpd/cgi-bin/proxy.cgi
reconfiguring squid in order to use privoxy in /var/ipcop/proxy/squid.conf
reconfiguring squid
privoxy is running with PID 20624


Restarting frox..
frox is not running
waiting 0 second(s)
frox is not running
No firewall rules active, frox ftp filtering not active

Restarting monit..
mo:2345:respawn:/var/log/copfilter/default/opt/monit/default/bin/monit -I -c /var/log/copfilter/default/opt/monit/etc/monitrc monit killed
waiting 3 second(s)
monit is not running
starting monit
waiting 3 second(s)
monit is running with PID 20741 20740 20738


Back to the copfilter configuration page

Last 50 lines of privoxy logfile:

Apr 18 19:39:48.569 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.569 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.570 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.570 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.570 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.571 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.571 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.573 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.575 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.575 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.576 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.576 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.576 Privoxy(00004000) Error: Action 'inspect-jpegs' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.576 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.576 Privoxy(00004000) Error: Action 'send-vanilla-wafer' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.576 Privoxy(00004000) Error: Action 'send-wafer' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.576 Privoxy(00004000) Error: Action 'treat-forbidden-connects-like-blocks' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.576 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 19:39:48.577 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.577 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.577 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.578 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 19:39:48.655 Privoxy(00004000) Info: Listening on port 8118 on all IP addresses
Apr 19 17:07:01.724 Privoxy(00004000) Info: exiting by signal 15 .. bye
Apr 19 17:07:02.766 Privoxy(00004000) Info: Privoxy version 3.0.10
Apr 19 17:07:02.766 Privoxy(00004000) Info: Program name: /var/log/copfilter/default/opt/privoxy/default/sbin/privoxy
Apr 19 17:07:02.766 Privoxy(00004000) Error: Action 'treat-forbidden-connects-like-blocks' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.769 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.769 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.769 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.770 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.770 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.770 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.771 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.773 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.774 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.775 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.775 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.775 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.776 Privoxy(00004000) Error: Action 'inspect-jpegs' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.776 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.776 Privoxy(00004000) Error: Action 'send-vanilla-wafer' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.776 Privoxy(00004000) Error: Action 'send-wafer' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.776 Privoxy(00004000) Error: Action 'treat-forbidden-connects-like-blocks' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.776 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 19 17:07:02.776 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.777 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.777 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.777 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 17:07:02.854 Privoxy(00004000) Info: Listening on port 8118 on all IP addresses

I hope this is what you wanted.

FischerM
Site Admin
Posts: 545
Joined: 09 Dec 2009 19:24
Location: Rheinbach

Re: PRIVOXY not working / being used

Post by FischerM » 19 Apr 2010 10:20

Hi!
moshari_3 wrote:I hope this is what you wanted.
Exactly. Great!

For now, the start sequences etc. are looking good.

1. Copfilter version? It ought to be 0.84beta4?
2. I would recommend to make an update of your privoxy installation.
3. The privoxy log indicates, that you're using some "incompatible" 'action'-files' in '/var/log/copfilter/0.84beta4/opt/privoxy/etc/'
For example:
Action 'kill-popups' is no longer valid in this Privoxy release.
4. What happens now, if you try to start the privoxy configuration page (HTTP Filter / privoxy configuration)?

Regards
Matthias

moshari_3
Posts: 152
Joined: 07 Apr 2010 03:43
Location: Australia

Re: PRIVOXY not working / being used

Post by moshari_3 » 19 Apr 2010 11:07

Sorry I took so long to reply I had a very early start today & fell asleep on the sofa.

I am currently running Copfilter 0.84beta4 installed I think on or around march 09.
I upgraded from Copfilter 0.84beta3a but I didn't uninstall first just ran install over the top.

The action files were installed along with the original install. I did try to make some minor additions or removals just a couple of url listings but didn't change any section titles at least I don't remember doing that.
Esentially I didn't really understand how they worked so left them alone.

Can I use Gedit to remove the bad references or get an up to date version of the action files or have I missed the point and should be modifying all these to suit my own purposes?

I have not made any changes, waiting for your advice.

I did look at the same log file from another IPC I remotely administer that does work & a restart looks the same in it's log.

Here is a copy from yesterday:

Apr 18 12:26:17.867 Privoxy(00004000) Info: exiting by signal 15 .. bye
Apr 18 12:26:18.924 Privoxy(00004000) Info: Privoxy version 3.0.10
Apr 18 12:26:18.924 Privoxy(00004000) Info: Program name: /var/log/copfilter/default/opt/privoxy/default/sbin/privoxy
Apr 18 12:26:18.925 Privoxy(00004000) Error: Action 'treat-forbidden-connects-like-blocks' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.929 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.929 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.929 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.930 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.930 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.931 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.931 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.934 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.937 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.938 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.938 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.938 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.939 Privoxy(00004000) Error: Action 'inspect-jpegs' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.939 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.939 Privoxy(00004000) Error: Action 'send-vanilla-wafer' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.939 Privoxy(00004000) Error: Action 'send-wafer' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.939 Privoxy(00004000) Error: Action 'treat-forbidden-connects-like-blocks' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.939 Privoxy(00004000) Error: Action 'kill-popups' is no longer valid in this Privoxy release. Ignored.
Apr 18 12:26:18.939 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.940 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.941 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:18.941 Privoxy(00004000) Error: block action without reason found. This may become a fatal error in future versions.
Apr 18 12:26:19.056 Privoxy(00004000) Info: Listening on port 8118 on all IP addresses

Thanks

moshari_3
Posts: 152
Joined: 07 Apr 2010 03:43
Location: Australia

Re: PRIVOXY not working / being used

Post by moshari_3 » 19 Apr 2010 11:38

Hi again Matthias.

A little more info inspired from reading a manual again.

I have URL-Filter installed using Adv-Proxy.
Both the working & not working systems are set for transparent proxy, not sure if that's important info or not.
Then from what I understand the http request is supposed to chain or link from adv-proxy over to the Privoxy & then out to the net?

All references I have read suggest that the chain or link between ADV-Proxy & Privoxy is not working anymore so Privoxy is being completely bypassed.
Unfortunately I have no idea how to check this further or test if this is true.

Considering that I have access to another IPC that does work but the log contains the same errors mine does would it be worth checking the chain or links between the 2 proxies.

Also if it is please tell how to check that out as I have no idea & am unable to find out how to do it so far.

Thanks.

FischerM
Site Admin
Posts: 545
Joined: 09 Dec 2009 19:24
Location: Rheinbach

Re: PRIVOXY not working / being used

Post by FischerM » 19 Apr 2010 12:00

Hi!

Copfilter version is ok.

Again: What happens now, if you try to start the privoxy configuration page (HTTP Filter / privoxy configuration)?

Besides, privoxy should be "up and running" - from my point of view.

Nevertheless, I would recommend you to update privoxy to v3.0.12.

This will also update the ''*.action'-files and the 'config'.

This (nonfatal!) error
Error: block action without reason found. This may become a fatal error in future versions.
will disappear, if you update the 'neilvandyke.action'-file, too. If yours is about 280KB, then its outdated...

Another alternative would be updating to test privoxy v3.0.16, which contains an updated 'neilvandyke.action'-file.
moshari_3 wrote:All references I have read suggest that the chain or link between ADV-Proxy & Privoxy is not working anymore so Privoxy is being completely bypassed.
Please check your privoxy-'config'-file for these lines:

Code: Select all

listen-address :8118
and change it to

Code: Select all

listen-address  127.0.0.1:8118
and change

Code: Select all

forward / :10080
to

Code: Select all

forward / 127.0.0.1:10080
And consider installing http://www.copfilter.org/wiki/doku.php? ... quid_cache too...

HTH
Matthias

moshari_3
Posts: 152
Joined: 07 Apr 2010 03:43
Location: Australia

Re: PRIVOXY not working / being used

Post by moshari_3 » 19 Apr 2010 12:36

Hi,
Sorry I missunderstood what you asked me last time.
With no changes yet and I try the link HTTP Filter / privoxy configuration I still get Privoxy is not being used.

I have now upgraded Privoxy to v3.0.12 then click full copfilter restart.
This is what I get this time:
Copfilter log files:

Now restarting all services

Please wait upto 2 min for messages to appear...

Restarting p3scan..
sent a HUP signal to monit waiting 1 second(s) p3scan killed
waiting 1 second(s)
p3scan is not running
No firewall rules active, p3scan mail filtering not active
starting p3scan
POP3 Traffic Scanning enabled on GREEN: eth0
POP3 Traffic Scanning enabled on BLUE: eth1
waiting 1 second(s)
p3scan is running with PID 25387
Iptables firewall rules active:

Table: nat Chain: PREROUTING 0 0 REDIRECT tcp -- eth0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 redir ports 8110
Table: nat Chain: PREROUTING 0 0 REDIRECT tcp -- eth0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:995 redir ports 8110
Table: nat Chain: PREROUTING 0 0 REDIRECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 redir ports 8110
Table: nat Chain: PREROUTING 0 0 REDIRECT tcp -- eth1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:995 redir ports 8110


Restarting proxmstpd..
proxsmtpd is not running
waiting 0 second(s)
removing firewall rules
proxsmtpd is not running
No firewall rules active, proxsmtp mail filtering not active

Restarting spamd..
sent a HUP signal to monit waiting 1 second(s) spamd killed
waiting 2 second(s)
spamd is not running
changing trusted_networks parameter in local.cf to 192.xxx.xxx. 192.xxx.yyy.
changing required_hits parameter in local.cf to 9
not speeding up spam scan (improved recognition) by enabling razor,dcc,dns&rbl_checks
enabling rulesdujour
starting spamd
waiting 1 second(s)
spamd is running with PID 25547

Restarting clamd..
sent a HUP signal to monit waiting 1 second(s)
Waiting . clamd killed
clamd is not running
Clamav debug mode disabled
Blocking of encrypted archives is disabled

starting clamd
waiting 1 second(s)
clamd is running with PID 25587 25586 25585

Restarting havp..
reconfiguring squid in order to STOP using havp in /home/httpd/cgi-bin/proxy.cgi
reconfiguring squid in order to STOP using havp in /var/ipcop/proxy/squid.conf
reconfiguring squid..
sent a HUP signal to monit waiting 1 second(s) havp killed
waiting 2 second(s)
havp is not running
enabling clamav scanning in havp
not enabling avg scanning in havp
not enabling fprot scanning in havp
reconfiguring squid in order to use havp in /home/httpd/cgi-bin/proxy.cgi
reconfiguring squid in order to use havp in /var/ipcop/proxy/squid.conf
reconfiguring squid..
starting havp
Starting HAVP Version: 0.91 waiting 1 second(s)
havp is running with PID 25714 25713 25712 25711 ...

Restarting privoxy..
privoxy entries in /home/httpd/cgi-bin/proxy.cgi already removed
privoxy entries in /var/ipcop/proxy/squid.conf already removed
no configuration change, no squid reconfiguration required
sent a HUP signal to monit waiting 1 second(s) privoxy killed
waiting 1 second(s)
privoxy is not running
starting privoxy
waiting 1 second(s)
reconfiguring squid in order to use privoxy in /home/httpd/cgi-bin/proxy.cgi
reconfiguring squid in order to use privoxy in /var/ipcop/proxy/squid.conf
reconfiguring squid
privoxy is running with PID 25741


Restarting frox..
frox is not running
waiting 0 second(s)
frox is not running
No firewall rules active, frox ftp filtering not active

Restarting monit..
mo:2345:respawn:/var/log/copfilter/default/opt/monit/default/bin/monit -I -c /var/log/copfilter/default/opt/monit/etc/monitrc monit killed
waiting 3 second(s)
monit is not running
starting monit
waiting 3 second(s)
monit is running with PID 25858 25857 25855


Back to the copfilter configuration page

The log file '/var/log/copfilter/default/opt/privoxy/var/log/privoxy/logfile' is as follows:
Apr 19 20:21:01.904 00004000 Info: exiting by signal 15 .. bye
Apr 19 20:21:02.947 00004000 Info: Privoxy version 3.0.12
Apr 19 20:21:02.947 00004000 Info: Program name: /var/log/copfilter/default/opt/privoxy/default/sbin/privoxy
Apr 19 20:21:02.947 00004000 Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 20:21:02.947 00004000 Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 20:21:02.947 00004000 Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 20:21:02.948 00004000 Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 20:21:02.948 00004000 Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 20:21:02.948 00004000 Error: block action without reason found. This may become a fatal error in future versions.
Apr 19 20:21:03.038 00004000 Info: Listening on port 8118 on all IP addresses

I am still getting Privoxy is not being used from the HTTP Filter / privoxy configuration link.

Sorry but where do I find the privoxy-'config' - file?

FischerM
Site Admin
Posts: 545
Joined: 09 Dec 2009 19:24
Location: Rheinbach

Re: PRIVOXY not working / being used

Post by FischerM » 19 Apr 2010 13:15

Hi!
moshari_3 wrote:Sorry but where do I find the privoxy-'config' - file?
Its in '/var/log/copfilter/default/opt/privoxy/etc/'.

1. Open PuTTY-Session to your Cop.

2. login as 'root'

3. Type

Code: Select all

cd /var/log/copfilter/default/opt/privoxy/etc/
[ENTER]

4. Type

Code: Select all

ls -l
[ENTER]

5. It should similar to this:

Code: Select all

root@DevelCop:/var/log/copfilter/default/opt/privoxy/etc # ls -l
total 304
-rw-rw---- 1 privoxy privoxy 53991 2010-04-12 16:27 config
-rw-rw---- 1 privoxy privoxy 53971 2010-04-12 18:50 config.new
-rw-rw---- 1 privoxy privoxy 72977 2010-04-12 18:50 default.action
-rw-rw---- 1 privoxy privoxy 37946 2010-04-12 18:50 default.filter
drwxr-xr-x 2 privoxy privoxy  4096 2010-04-12 18:51 init.d
-rw-rw---- 1 privoxy privoxy   762 2009-05-05 20:36 match-all.action
-rw-rw---- 1 privoxy privoxy   549 2010-04-12 18:50 match-all.action.new
-rw-r--r-- 1 privoxy privoxy 14213 2010-04-11 15:24 neilvandyke.action
-rw-rw---- 1 privoxy privoxy  2756 2009-03-20 10:45 standard.action
drwxr-xr-x 2 privoxy privoxy  4096 2010-04-12 18:51 templates
-rw-rw---- 1 privoxy privoxy  3863 2009-05-01 22:37 trust
-rw-rw---- 1 privoxy privoxy  3761 2010-04-12 18:50 trust.new
-rw-rw---- 1 privoxy privoxy  7188 2009-08-13 20:15 user.action
-rw-rw---- 1 privoxy privoxy  6425 2010-04-12 18:50 user.action.new
-rw-rw---- 1 privoxy privoxy  3334 2008-08-25 20:58 user.filter
-rw-rw---- 1 privoxy privoxy  3334 2010-04-12 18:50 user.filter.new
6. Type

Code: Select all

nano config
or use any Linux-capable editor (Vi, for example)

7. Change lines as mentioned in my previous posting.

8. Restart all Copfilter-services (from GUI).

9. Report...

HTH
Matthias

moshari_3
Posts: 152
Joined: 07 Apr 2010 03:43
Location: Australia

Re: PRIVOXY not working / being used

Post by moshari_3 » 19 Apr 2010 13:40

I'm sorry if I'm frustrating you with my lack of knowledge :oops: .
But I do really appreciate the help you are giving me.

Ok so here is where I am upto.
Since my last reply I have installed the "privoxy inactive after clearing cache" patch which initially didn't seem to do anything, however after clearing the cache I can now get the privoxy configuration page from http config privoxy link.

Almost good but a web page that I know going by the other IPC's I look after is infected with a virus still isn't blocked by my F/W.

I have edited the config file as recommend above & restarted Adv-Proxy, URLfilter & Copfilter but again the page is still not blocked by my F/W which is now after being able to get the Privoxy config page why I still not convinced that all is well.

The supposed virus that the other IPC is reporting is listed as ClamAV: Sanesecurity.Phishing.Cur.120.UNOFFICIAL (description)

Can I post a link to the suspect page?
Or is that considerd bad taste or etiquete?
It is a ebay page I might ad.

Post Reply