You are not logged in.
Pages: 1
Since the latest upgrade, Privoxy is blocking my internet connection.
If I start Privoxy in a terminal, I get the error message
b74ca6c0 Fatal error: can't check configuration file '/home/myrlin/config': No such file or directory
If I create a folder "config" everything works. I guess a "." has been omitted in the source code, so that Privoxy is looking for the folder "config" rather than ".config".
Does anyone else have this problem?
Offline
I just upgraded and use privoxy with dansguardian and haven't seen any issues.
I get the following result from ps -ef | grep privoxy
/usr/sbin/privoxy --user root.root --pidfile /var/run/privoxy.pid /etc/privoxy/config
Offline
I use Privoxy with Firefox on both my desktop and my laptop.
I have just discovered that this problem only occurs on my laptop, which I have modified to use systemd.
There are no problems on my desktop (NOT modified to use systemd), so maybe the problem lies elsewhere?
I originally used the privoxy-systemd package from the AUR to provide the privoxy.service unit. I uninstalled this to enable the new version of privoxy (presumably including its own privoxy.service file) to install successfully. Perhaps something has broken in this process. I will completely uninstall privoxy, and re-install to see whether that makes any difference.
Offline
Further investigation indicates that the problem lies in the privoxy.service file.
This file, included in the latest version of the package fails:
[Unit]
Description=Privoxy Web Proxy With Advanced Filtering Capabilities
After=network.target
[Service]
Type=forking
PIDFile=/run/privoxy.pid
ExecStart=/usr/sbin/privoxy --pidfile /run/privoxy.pid --user privoxy.privoxy /etc/privoxy/config
[Install]
WantedBy=multi-user.target
Replacing it with this file from the AUR (privoxy-systemd) solves it:
[Unit]
Description=Privacy enhancing HTTP Proxy
[Service]
ExecStart=/usr/sbin/privoxy --no-daemon /etc/privoxy/config
StandardOutput=syslog
StandardError=syslog
[Install]
WantedBy=multi-user.target
I have checked that network.target is loaded and active, so that is not the cause.
Last edited by myrlin (2012-09-01 14:08:18)
Offline
Pages: 1