Yes, adding After=network-online.target to /lib/systemd/system/privoxy.service helped, and it is neater than the workaround I used - waiting until the address becomes available in privoxy.service. Thanks.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870101 Title: privoxy won't start at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/privoxy/+bug/1870101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
