[BUG] "Internal server error (500)" after 15 seconds

[eocula]

Describe the bug
Since some days, my whoogle does not work anymore: after 10-15 seconds, I get a "Internal server error (500)". As far as I know, nothing has changed on my installation

To Reproduce
Steps to reproduce the behavior:

1. Go to https://search..be.'
2. Enter a string to search for
3. Hit the return-key or click the Search-button
4. After 10-15 seconds, "Internal server error (500)" is shown, and the page with suggestions to use other searcvh-engines

Deployment Method

• Heroku (one-click deploy)
• [ x] Docker (on a Synology-NAS, latest DSM-version)
• run executable
• pip/pipx
• Other: [describe setup]

Version of Whoogle Search

• [x ] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc), so 1.2.2
• Version [version number]
• Not sure

Desktop (please complete the following information):

• OS: [e.g. iOS] WIN11
• Browser [e.g. chrome, safari] Edge
• Version [e.g. 22] Latest

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[Don-Swanson]

What is throwing the 500 error, Whoogle or Google?

Also, I know that Synology "Docker" is not real docker and often breaks things, have you tried a fresh deployment? (Possibly somewhere that has real docker)

[eocula]

when I search something with my self-hosted Whoogle, there is a delay of about 20 seconds and then it gives that error.

I have hosted this now for almost 3 years on my Synology-NAS, on a docker. I had never issues with the docker. But if you really think a fresh deployment would solve it, then I will do. Please let le know

And/or: is there another way to debug the issue I have?

[Don-Swanson]

Can you share the container logs when the 500 happens?

Also please include:
• Your Docker Compose config
• Synology model and DSM version
• Whether you’re using a VPN or reverse proxy
• Whether the 500 is from Whoogle (container logs) or an upstream response

There aren’t other reports of this, and I haven’t been able to reproduce it, so we’ll need more details.

Have you tried on another device? (I am a little biased against Synology, because of all the ones I owned in the past, they never lasted past 3 years before they started dying a slow death)

Have you recently updated anything? Have you tried an older version of Whoogle?

[eocula]

Hi, thanks for your reply. Here some answers

• My Synology is a DS920+, latest (DSM7) DSM-version
• Yes, I'm using a reverse proxy but the same error occurs when I run it locally (through 192.168.1.207:5105)

My whoogle is installed through a 'docker run'. Below the command

docker run -d --name=whoogle
-p 5105:5000
-v /volume2/docker/whoogle:/config
--security-opt=no-new-privileges
--restart always
benbusby/whoogle-search:latest

And attached the logfile, generated after a search which gave me the error

whoogle.csv

[Don-Swanson]

The log shows "httpx.ReadTimeout: The read operation timed out", which means it couldn't read the chunk of data before the timeout. Typically this is either a network issue or a performance issue on the device hosting the application.

1. Did this happen after an update or any recent changes?
2. Have you been able to replicate on another device? Maybe try temporarily running locally on your PC as a test.
3. Have you tried an older version of Whoogle?