Replies: 5 comments
-
|
Definitively a networking issue on your side. SearXNG has always worked fine with images. |
Beta Was this translation helpful? Give feedback.
-
|
Loaded up a sample, https://searx2.headpat.exchange/search?q=gort on images loads slow and out of order, while https://searx.headpat.exchange/search?q=gort running directly from Hetzner works well and without issues, wierd.. |
Beta Was this translation helpful? Give feedback.
-
as written above https://github.com/searxng/searxng/issues/2700#issuecomment-1699866578 its an issue of your "security" (network) setup .. in the links you gave we can see that your setup blocks and slow down image request in your searx2 subdomain. This issue tracker is intended for SearXNG issues .. in that sense a wireguard setup is off-topic here --> I close this issue. |
Beta Was this translation helpful? Give feedback.
-
|
On searx2, on the right side, the result page should display the labels not P17, P2046 and P281. However, this is out of the scope of SearXNG. |
Beta Was this translation helpful? Give feedback.
-
|
Converting to a github discussion in case of further discussion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG
2023.8.30+7af66736cHow did you install SearXNG?
using searxng-docker
What happened?
So, for security i route all my services via a wireguard tunnel, i observed that while i do that, images in the image search behave wierdly and load out of order while some just wont load completely. I do have image proxy enabled in the searxng config.
My guess was a slow internet connection from the tunnel server, but after changing it from 1984.hosting to Hetzner, it keeps behaving the same. Now my domain (https://searx.headpat.exchange) runs from the Hetzner VPS without any tunneling going on, and all the images behave as expected, loading in order.
My home network has a Download speed of ~400 Mbit/s and an Upload of ~500 Mbit/s, the searx.space results show a
6.577Search response time as of 30/08/2023. When i was exposing services directly from my home IP, it worked properly without issues and additional delays.I'm not sure why that is happening, could the latency between me and Hetzner in germany (i live in a neighboring country) be so much that it just times out?
How To Reproduce
Use https://github.com/DigitallyRefined/docker-wireguard-tunnel and follow the instructions on setting up a simple wireguard tunnel, push ports of SearXNG through the tunnel and expose it on the server.
Expected behavior
Images loading properly, in order like in most instances
Screenshots & Logs
Logs look completely normal, nothing unusual
Additional context
settings.ymlBeta Was this translation helpful? Give feedback.
All reactions