| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| MoTekLab-Proxy-Suite-1.6.10.AppImage | 2026-05-09 | 166.6 MB | |
| MoTekLab-Proxy-Suite-1.6.10.tar.gz | 2026-05-09 | 152.1 MB | |
| MoTekLab-Proxy-Suite_1.6.10_amd64.deb | 2026-05-09 | 99.3 MB | |
| README.md | 2026-05-09 | 814 Bytes | |
| v1.6.10 source code.tar.gz | 2026-05-09 | 1.3 kB | |
| v1.6.10 source code.zip | 2026-05-09 | 2.0 kB | |
| Totals: 6 Items | 418.0 MB | 0 | |
[1.6.10] - 2026-05-09
Fixed
- SearXNG "403 Forbidden" from local Docker instance — the default SearXNG config has
searchdns: true, which does a DNS-based client IP check. Connections from Docker bridge IPs (172.17.x.x) fail this check, returning 403. Updated all Docker commands in Help docs and Settings description to include-e SEARXNG_DNS__SEARCH_DNS=false. Added a dedicated "Why does SearXNG return 403 Forbidden?" Q&A in all 3 languages (EN/AR/ARZ) that explains the root cause and fix. - SearXNG 403 log message now suggests the fix — when a SearXNG request returns 403, the "Blocked on SearXNG Discovery" log line now appends
| FIX: SearXNG needs searchdns=false. Add -e SEARXNG_DNS__SEARCH_DNS=false to your docker run command, so the user sees the solution directly in the log.