privoxy won't start at boot
Bug #1870101 reported by
lvm
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
privoxy (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Privoxy fails to bind to network address at boot time with
Fatal error: can't bind to 192.168.1.3:8118: Cannot assign requested address
Subsequent manual start works.
Similar bug #427625 exists but it is marked as fixed - which is obviously not the case, and it also deals with inability to bind to localhost, not to an external host address which is a static address assigned via dhcp, so I am filing a new bug.
5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
privoxy address is configured as 'listen-address 192.168.1.3:8118'
To post a comment you must log in.
According to https:/ /www.freedeskto p.org/wiki/ Software/ systemd/ NetworkTarget/ it may be a good idea to change network. target system/ privoxy. service to network- online. target
After=
in the /lib/systemd/
After=
If you prefer an update safe mechanism, run
systemctl edit privoxy.service
and write
[Unit] online. target
After.network-
into it.
I'll create an update to the privoxy package to fix this, soon.