My docker/podman container running recently started showing that seem
related to time out, to search engines.

Has anybody else encountered this? I've not changed anything -- so wondnering if something changed upstream.

Sorry!

No results were found. You can try to:

Refresh the page.
Search for another query or select another category (above).
Change the search engine used in the preferences: /preferences
Switch to another instance: https://searx.space

https://mynotes.ddns.net/share/vOh43L0OXYHE
===
Amessyroom
toolazy.synchro.net:2323 (telnet)
--- SBBSecho 3.24-Linux
* Origin: Too Lazy BBS - toolazy.synchro.net:2323 (1337:3/194)

On 12 May 2025, Errol Casey said the following...

My docker/podman container running recently started showing that seem related to time out, to search engines.

Has anybody else encountered this? I've not changed anything -- so wondnering if something changed upstream.

Sorry!

No results were found. You can try to:

Refresh the page.
Search for another query or select another category (above).
Change the search engine used in the preferences: /preferences
Switch to another instance: https://searx.space

https://mynotes.ddns.net/share/vOh43L0OXYHE

I haven't seen anything like that, mine has been running just fine. Did you update it recently? I update mine nightly so I always have the latest version available.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N // @meatlotion:erb.pw

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

... Press SPACEBAR once to abort, or twice to save changes

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

Re: Re: searxng
By: MeaTLoTioN to Errol Casey on Tue May 13 2025 06:20 pm

On 12 May 2025, Errol Casey said the following...

My docker/podman container running recently started showing that seem
related to time out, to search engines.

Has anybody else encountered this? I've not changed anything -- so
wondnering if something changed upstream.

Sorry!

No results were found. You can try to:

Refresh the page.
Search for another query or select another category (above). Change the
search engine used in the preferences: /preferences Switch to another
instance: https://searx.space

https://mynotes.ddns.net/share/vOh43L0OXYHE

I haven't seen anything like that, mine has been running just fine. Did you update it recently? I update mine nightly so I always have the latest version available.

when you say update, do you mean remove image and then redownload it each night ?

I had not tried that, but did and I'm still having same issue. Bizzare that it just suddenly started this week.
===
Amessyroom
toolazy.synchro.net:2323 (telnet)
--- SBBSecho 3.24-Linux
* Origin: Too Lazy BBS - toolazy.synchro.net:2323 (1337:3/194)

Re: Re: searxng
By: MeaTLoTioN to Errol Casey on Tue May 13 2025 06:20 pm

My docker/podman container running recently started showing that seem
related to time out, to search engines.

I haven't seen anything like that, mine has been running just fine. Did you update it recently? I update mine nightly so I always have the latest version available.

Got it working. After trying to update container image, edit settings.yml (increase time out),
and change DNS. None of which worked.

Patched up server and rebooted, and it is working again. argh!

I use podman vs docker since using a RHEL dervivative.

And there was a path for podman, so maybe there was something changed inbetween updates.

I normally try and update things weekly.

But don't know the real problem .... :-(
===
Amessyroom
toolazy.synchro.net:2323 (telnet)
--- SBBSecho 3.24-Linux
* Origin: Too Lazy BBS - toolazy.synchro.net:2323 (1337:3/194)

On 14 May 2025, Errol Casey said the following...

when you say update, do you mean remove image and then redownload it
each night ?

I had not tried that, but did and I'm still having same issue. Bizzare that it just suddenly started this week.

No, this is my update script;

#!/usr/bin/env bash
cd /usr/local/searxng-docker
git pull
docker-compose pull
docker-compose up -d

I run that at midnight every night.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N // @meatlotion:erb.pw

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

... Great minds think alike; small minds run together

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)