You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Start whoogle-search with options "--proxytype socks5 --proxyloc 127.0.0.1:8310" where there is a local socks5 proxy server running at 127.0.0.1 port 8310.
Perform search.
Receive Internal server error (500)
Deployment Method
pip/pipx
Version of Whoogle Search
Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
Desktop (please complete the following information):
OS: Debian Bookworm
Browser Chromium
Version 123.0.6312.122
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:
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.
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: