Well it seems getting it to work via docker wasn’t that difficult. I have it working now. Thank you to everyone for your suggestions!
I always thought Docker was some incomprehensible techno-wizardry. Especially when it comes to its networking. Which is odd as I have no issue maintaining a bunch of VMs and LXCs in my homelab. Title changed to solved. Thanks again!
Curl works for google and also with bing. Just as pinging and wget. This instance is not public facing so it does not have an assigned domain. I’m trying to run it locally at the moment.
Apache logs (/var/log/apache2/error.log) does show up something interesting. Thought it might be Apache or UWSGI. UWSGI has issues with connecting to a socket it seems. x.x.x.x is my desktop IP.
[Mon May 11 19:44:53.702774 2026] [core:notice] [pid 1644:tid 1644] AH00094: Command line: '/usr/sbin/apache2'
[Mon May 11 19:45:55.440224 2026] [proxy:error] [pid 1957:tid 1961] (2)No such file or directory: AH02454: uwsgi: attempt to connect to Unix domain socket /usr/local/searxng/run/socket (uwsgi-uds-searxng:0) failed
[Mon May 11 19:45:55.440252 2026] [:error] [pid 1957:tid 1961] [client x.x.x.x:56586] AH10101: failed to make connection to backend: uwsgi-uds-searxng:0
[Mon May 11 19:46:20.548413 2026] [mpm_event:notice] [pid 1644:tid 1644] AH00493: SIGUSR1 received. Doing graceful restart
According to systemd, apache2 and uwsgi both run without error.
None of this runs in a docker so can’t look there. This is all on a LXC.
Nothing stands out.
It most likely is something with the application or apache. However I wouldn’t know where to look. A general google search has not led me anywhere useful. :(
Thanks for taking the time with your suggestion. Unfortunately, DNS does not seem to be an issue. Pinging works fine.
The below is from the container.
I was trying to install it standalone using their install script instructions. The ‘solution’ was to switch to using their docker instructions and run their docker instead.