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

500 Internal Privoxy Error when Privoxy enabled #8

Closed
arturhg opened this issue Oct 18, 2018 · 3 comments
Closed

500 Internal Privoxy Error when Privoxy enabled #8

arturhg opened this issue Oct 18, 2018 · 3 comments

Comments

@arturhg
Copy link

arturhg commented Oct 18, 2018

When Privoxy enabled sometimes this error appears as a response:

500 Internal Privoxy Error

Privoxy encountered an error while processing your request:

Could not load template file no-server-data or one of its included components.

Please contact your proxy administrator.

If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It's typically the Privoxy install directory, or /etc/privoxy/).

Steps to reproduce:

  1. docker run -d -p 8118:8118 -p 2090:2090 -e tors=25 -e privoxy=1 zeta0/alpine-tor
  2. Make a request with HTTP proxy
  3. Get error
@Otetz
Copy link
Contributor

Otetz commented Oct 18, 2018

Agreed, sometimes this happen.
I have workaround for python requests: https://github.com/Otetz/requests_proxy_adapter

@arturhg
Copy link
Author

arturhg commented Nov 12, 2018

@Otetz This is great!
But for fixing problem from the root, we can remove privoxy and use DeleGate instead.
Like this: DeleGate -> HaProxy -> Tors
Or there is a better solution?

@zet4
Copy link
Owner

zet4 commented Jan 31, 2019

#7 mostly covers this so I will close this for now

@zet4 zet4 closed this as completed Jan 31, 2019
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

3 participants