nothanks

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

nothanks's Achievements

Noob

Noob (1/14)

0

Reputation

  1. The Privoxy crashing seems to be resolved in the recent build, but now my logs are filled with this message every 15 minutes. Anyone else seeing this? Successfully assigned and bound incoming port
  2. Is there anything to be worried about with Privoxy constantly restarting? I "think" it's working, but logs clearly show its restarting every 30s even after this latest update.
  3. Is anyone else seeing privoxy restarting every 30s? Not sure where to troubleshoot, any help would be appreciated.
  4. I also found this in the logs: 2021-02-28 20:46:00.991 7f7e625b81c0 Fatal error: can't bind to INADDR_ANY:8118: There may be another Privoxy or some other proxy running on port 8118 Any ideas? This was working prior to the recent release and I see a few other people have reported the privoxy restarting issue as well.
  5. Do we have any solutions or ideas regarding privoxy constantly restarting? 2021-02-28 13:27:15,678 DEBG 'watchdog-script' stdout output: fo] Privoxy not running 2021-02-28 13:27:15,681 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-02-28 13:27:16,692 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-02-28 13:27:16,701 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-02-28 13:27:46,797 DEBG 'watchdog-script' stdout output: fo] Privoxy not running 2021-02-28 13:27:46,800 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-02-28 13:27:47,811 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-02-28 13:27:47,820 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118
  6. Any ideas on why privoxy keeps restarting with this update?