-
-
Notifications
You must be signed in to change notification settings - Fork 897
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
[BUG] socks5 proxy config gives Internal server error 500 #1138
Comments
I looked into this some more, and it appears that without manually installing PySocks, the socks5 proxy won't work. I had originally installed whoogle-search with pipx, and there's no way to manually install PySocks through pipx. After setting up a virtual environment and manually installing whoogle-search and PySocks, I was able to get it to work. I see a lot of requirements in requirements.txt (including PySocks) that don't get installed automatically as a dependency. It still seems to work without those, though (as far as I can tell), except in the case of PySocks. |
Also, in case anybody is trying to get socks5 to work, there's 2 different socks5 settings for WHOOGLE_PROXY_TYPE: socks5 socks5 is similar to "curl --socks5" and socks5h is similar to "curl --socks5-hostname". socks5 = Local DNS resolution This is important sometimes, for example, if the remote proxy is IPv4 only and the DNS resolution is local, it may lookup an IPv6 for google and fail. |
Describe the bug
When configured to use a socks5 proxy, the result is an "Internal server error (500)".
To Reproduce
Steps to reproduce the behavior:
Deployment Method
Version of Whoogle Search
Desktop (please complete the following information):
Additional context
whoogle-search is using nginx as a reverse proxy. Other startup parameters:
whoogle-search --port 6000 --host 127.0.0.1 --https-only
I've tried with and without --https-only (makes no difference to the error).
I've tried with --debug but it doesn't give any helpful clue, just a POST for the search and a GET with status 500.
The text was updated successfully, but these errors were encountered: