Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Privoxy no longer working? #78

Open
normanu opened this issue Jan 28, 2021 · 2 comments
Open

Privoxy no longer working? #78

normanu opened this issue Jan 28, 2021 · 2 comments

Comments

@normanu
Copy link

normanu commented Jan 28, 2021

Privoxy seems to be no longer reachable while the port seems open.
Maybe is firewall closed?

@rssnyder
Copy link

Same thing here. I see this in startup logs:

2021-02-21 19:47:27,710 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2021-02-21 19:47:28,717 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2021-02-21 19:47:28,723 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

But am unable to connect via firefox proxy settings or http(s)_proxy in linux.

$ nc 192.168.0.4 8118 -vvv
nc: connect to 192.168.0.4 port 8118 (tcp) failed: Connection timed out

@normanu
Copy link
Author

normanu commented Feb 22, 2021

@rssnyder with me it was not the container it was docker itself.
Somehow if containers start to quickly after each other you get a iptables reservation error.
You need to restart docker and start each container one by one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants