This repository has been archived by the owner on Sep 7, 2023. It is now read-only.
Internal Server Error after changing Engine preferences through web GUI #3523
Unanswered
js4github
asked this question in
Installation issue: custom
Replies: 2 comments 1 reply
-
Thanks, @unixfox for acting on this. I'll keep an eye on this - if there's anything I can provide just let me know. |
Beta Was this translation helpful? Give feedback.
0 replies
-
searx 0.18.0 is completely outdated, 1.1.0 came out almost one year ago: https://github.com/searx/searx/releases/tag/v1.1.0 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Solution: Increasing the uwsgi buffer-size to 5120 seems to have corrected the issue for me. Details and diffs are below.
Reference: FreedomBox forum support post
Reference: FreedomBox forum development post
Version of Searx, commit number if you are using on master branch and stipulate if you forked Searx
Web UI version info
Debian package info
Fork: I'm unsure if I'm using a fork
How did you install Searx?
Searx was installed using Debian / Freedombox automation
OS Info
FreedomBox Info
What happened?
After chaning the search engine options I would in some cases receive an Internal Server Error in the web UI which could only be resolved by deleting browser cookies which contained the new searx client options. Any favorable changes made up to this point are lost when the cookie set by searx is deleted.
How To Reproduce
As an alternative to steps 4-6 you may need to "Allow All" for each category of search engine, but just doing this with videos was reliable for me.
Expected behavior
I expected to be returned to the searx UI after saving preferences.
Screenshots & Logs
Screen capture of error
Error in /var/log/uwsgi/app/searx.log:
Additional context
I believe that the default uwsgi buffer size is set too small for some requests which searx generates. I have been able to resolve the problem in my own case by modifying /etc/uwsgi/apps-available/searx.ini adding a line:
I selected 5120 by adding 25% to the skipped request size. After making this change I have not encountered the problem again. I did not have success setting a larger UWSGI_BUFFER_SIZE=8192 environment variable in the uwsgi startup script.
In my own mind I have confirmed success by using the "Allow All" in every server engine category and successfully saving the change and retruning to the searx web UI to perform a successful search.
Diffs
Beta Was this translation helpful? Give feedback.
All reactions