The installation for privoxy is missing the script privoxyd that should be in the /etc/init.d/ diectory; thus one is not able to modify the privoxy config.
The other problem is with the xfce installation after using xfce on 13.1 with xfwm4, openbox, icewm the cursor disappears from the desktop. This has happened at least 4 times and the only way that I have found to fix it is to reinstall with 12.3 and not use 13.1 at all.
“/etc/init.d” is a leftover from when we were using “sysvinit”. With the move to “systemd”, files in “/etc/init.d” are mostly unused relics.
You possibly need to edit the service definition for privoxy.
That happens to me on one box, with a Nvidia graphics card. Switching to the “nvidia” driver, instead of the “nouveau” driver, fixed it. The other option, at least in KDE, was to configure the power settings to never turn off the graphics. I’m not sure if there is a similar option for icewm or xfce.
Your problem might be different, but the chances are that it is related to the graphics driver.
As nrickert already mentioned, privoxy contains a native systemd unit file /usr/lib/systemd/system/privoxy.service.
To start privoxy on boot, enable that in YaST->System->Services Manager, or with:
sudo systemctl enable privoxy.service
AFAICS the configuration is read from /var/lib/privoxy/config (/etc/privoxy is a symlink to that), so just edit that.
hi all, i am facing the same problem, trying to start privoxy but am unsuccessful. if any of you how to install and use then please tell me simple steps… thanx alot…
well i have opensuse 13.1 and i install privoxy using zypper version privoxy-3.0.21-2.8.1.x86_64. the command “sudo systemctl status privoxy.service” gives me output
privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities
Loaded: loaded (/usr/lib/systemd/system/privoxy.service; disabled)
Active: inactive (dead)
while #privoxy /etc/privoxy/config does not give any reply…
i enabled and started privoxy from yast->service manager and then typed command
sudo systemctl status privoxy.service
the output is
linux-j9pv:~ # sudo systemctl status privoxy.service
privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities
Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled)
Active: active (running) since Sat 2014-03-15 16:05:57 PKT; 8min ago
Main PID: 12739 (privoxy)
CGroup: /system.slice/privoxy.service
└─12739 /usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config
Mar 15 16:05:57 linux-j9pv.site systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities.
Mar 15 16:13:56 linux-j9pv.site systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities.
Mar 15 16:14:02 linux-j9pv.site systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities.
but privoxy is not sending traffic through tor its giving same ip address with or without using privoxy…
but privoxy is not sending traffic through tor its giving same ip address with or without using privoxy…
Hm, I never used privoxy, so cannot really help you there.
Maybe you need to configure it first?
The configuration should be in /etc/privoxy.
From the included README file:
4. CONFIGURATION
See: 'config', 'default.action', 'user.action', 'default.filter', and
'user.filter'. 'user.action' and 'user.filter' are for personal and local
configuration preferences. These are all well commented. Most of the magic is
in '*.action' files. 'user.action' should be used for any actions
customizations. On Unix-like systems, these files are typically installed in /
etc/privoxy. On Windows, then wherever the executable itself is installed.
There are many significant changes and advances from earlier versions. The User
Manual has an explanation of all configuration options, and examples: http://
www.privoxy.org/user-manual/.
Be sure to set your browser(s) for HTTP/HTTPS Proxy at <IP>:<Port>, or whatever
you specify in the config file under 'listen-address'. DEFAULT is
127.0.0.1:8118. Note that Privoxy ONLY proxies HTTP (and HTTPS) traffic. Do not
try it with FTP or other protocols for the simple reason it does not work.
The actions list can be configured via the web interface accessed via http://
p.p/, as well other options.
AFAICS the default config tells privoxy to listen on port 8118, so you would have to tell your browser/the system to use the proxy at localhost:8118.
I am using OpenSuse 13.1 and I am trying to use privoxy, but it is not working for me. It was working on Opensuse 12.3 though before I updated to 13.1
This is the output to systemctl
sudo systemctl -l status privoxy.service
privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities
Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled)
Active: active (running) since lun 2014-06-23 16:17:38 CEST; 21min ago
Main PID: 773 (privoxy)
CGroup: /system.slice/privoxy.service
└─773 /usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config
jun 23 16:17:36 linux-diy5.site systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities...
jun 23 16:17:38 linux-diy5.site systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities.
Those directory listings don’t help either.
Of course those files should be present if you installed privoxy. And /etc/sysconfig/proxy should be there on any openSUSE installation.
Please guide me through next steps.
No I can’t. I never used privoxy myself.
But you have to configure privoxy itself (in /etc/privoxy), you have to tell your system to use the proxy either in YaST->Network Services->Proxy or in /etc/sysconfig/proxy.
I cannot give you more concrete hints, sorry.
And again, are you using NetworkManager? There seems to be a problem when using privoxy together with NetworkManager. See the bug report for a workaround.
I have deleted previous installation of privoxy, and I have done a new installation.
After that, privoxy was working perfect.
However, after I had done the new installation I reboot the system. Then, privoxy stopped working again. So I don’t think it is anything to do with Networkmanager as previously suggested.
This is again the output to systemctl -l status privoxy.service
systemctl -l status privoxy.service
privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities
Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled)
Active: active (running) since sáb 2014-08-23 16:47:42 CEST; 6min ago
Process: 1481 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 801 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, status=0/SUCCESS)
Process: 743 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exited, status=0/SUCCESS)
Process: 730 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=exited, status=0/SUCCESS)
Main PID: 802 (privoxy)
CGroup: /system.slice/privoxy.service
└─802 /usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config
ago 23 16:47:40 linux-diy5 systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities...
ago 23 16:47:42 linux-diy5.site systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities.
ago 23 16:48:08 linux-diy5.site systemd[1]: Reloading Privoxy Web Proxy With Advanced Filtering Capabilities.
ago 23 16:48:08 linux-diy5.site systemd[1]: Reloaded Privoxy Web Proxy With Advanced Filtering Capabilities.
ago 23 16:49:35 linux-diy5.site systemd[1]: Started Privoxy Web Proxy With Advanced Filtering Capabilities.
Sorry I don’t have any. As I mentioned in this thread already, I never used privoxy myself.
According to your systemctl output it is running/active.
Or have you started it manually?
Does it work if you restart it?
systemctl restart privoxy
Normally such problems won’t get fixed magically by uninstalling/installing it.
But that could cause to service to restart.
If it works after the service is restarted, then my guess would be that it likely starts too soon during boot (i.e. when the network connection is not up yet) or something like that.
Which could be caused by the fact that you are using NetworkManager. Normally NetworkManager returns that it is successfully started immediately, before the network is up.
You might try to set NM_ONLINE_TIMEOUT to a value different than ‘0’ (the default) to make NetworkManager wait for the connection. If you’re using a wireless connection, you have to mark it as “system connection” or “shared with other users” then as well, otherwise it will only be established when you login, i.e. much too late.
But again, I never used privoxy, so don’t know whether the network connection has to be established already when it starts. This is just an assumption.