[Support] kilrah/searxng

[Kilrah]

[Template only, I am not the container author/maintainer]

 

Template: https://github.com/kilrah/unraid-docker-templates/blob/main/templates/searxng.xml

Source container: https://github.com/searxng/searxng

Registry: https://hub.docker.com/r/searxng/searxng

 

The official SearXNG container.

 

[Jaybau]

Is there a way to change the port?

[Kilrah]

Sure, as long as it's in the default bridged mode like any other container...

Edited February 15 by Kilrah

[Jaybau]

My configuration for this Docker (SearXNG) seems to be missing the "Container Port" that I see in other containers.

 

Another Docker has these options:

 

[Kilrah]

See above, you likely don't have Networking for that container set to bridge.

 

Edited February 15 by Kilrah

[EyeOfMaze]

Hello, thank you for this container. I cannot seem to get this to work with nginx proxy manager though. All my other containers are working fine except this one. I'm assuming there is something that needs to be changed in the docker to allow this to proxy correctly? Any idea of want needs to be done?

[Kilrah]

Nothing special here...

 

 

searxng on bridge, NPM on host

[EyeOfMaze]

I'm not sure what was wrong, I couldn't get this to work all day yesterday, woke up this morning and now it works. Thank you again.

[gilladur]

Am I the only one with internal server error since the update yesterday?

 

Traceback (most recent call last):
  File "/usr/local/searxng/searx/webapp.py", line 1398, in <module>
    redis_initialize()
  File "/usr/local/searxng/searx/redisdb.py", line 56, in initialize
    _CLIENT.ping()
  File "/usr/lib/python3.10/site-packages/redis/commands/core.py", line 1194, in ping
    return self.execute_command("PING", **kwargs)
  File "/usr/lib/python3.10/site-packages/redis/client.py", line 1255, in execute_command
    conn = self.connection or pool.get_connection(command_name, **options)
  File "/usr/lib/python3.10/site-packages/redis/connection.py", line 1441, in get_connection
    connection.connect()
  File "/usr/lib/python3.10/site-packages/redis/connection.py", line 698, in connect
    sock = self.retry.call_with_retry(
  File "/usr/lib/python3.10/site-packages/redis/retry.py", line 46, in call_with_retry
    return do()
  File "/usr/lib/python3.10/site-packages/redis/connection.py", line 699, in <lambda>
    lambda: self._connect(), lambda error: self.disconnect(error)
  File "/usr/lib/python3.10/site-packages/redis/connection.py", line 1171, in _connect
    sock.settimeout(self.socket_timeout)
AttributeError: 'UnixDomainSocketConnection' object has no attribute 'socket_timeout'
unable to load app 0 (mountpoint='') (callable not found or import error)
*** no app loaded. going in full dynamic mode ***
--- no python application found, check your startup logs for errors ---
[pid: 15|app: -1|req: -1/1] 192.168.178.162 () {36 vars in 1944 bytes} [Sat Mar 25 11:50:20 2023] GET / => generated 21 bytes in 0 msecs (HTTP/1.1 500) 3 headers in 102 bytes (0 switches on core 0)
--- no python application found, check your startup logs for errors ---
[pid: 49|app: -1|req: -1/2] 192.168.178.162 () {36 vars in 1942 bytes} [Sat Mar 25 11:50:20 2023] GET /favicon.ico => generated 21 bytes in 0 msecs (HTTP/1.1 500) 3 headers in 102 bytes (0 switches on core 0)

 

[Kilrah]

Looks like it broke indeed, I forced to tag 2023.3.22-38414355 and that's fine

[gilladur]

Thanks, that's working for me too. 

[diehardbattery]

3 hours ago, Kilrah said:

Looks like it broke indeed, I forced to tag 2023.3.22-38414355 and that's fine

I'm having this issue as well... however I don't know much about troubleshooting/fixing things like this.  Can you ELI5 what you did?  Thanks!

[gilladur]

The only thing you have to do is to add ":2023.3.22-38414355" like in the picture under repository - by that way this particular working build is used: 

Edited March 25 by gilladur

[diehardbattery]

9 minutes ago, gilladur said:

The only thing you have to do is to add ":2023.3.22-38414355" like in the picture under repository - by that way this particular working build is used: 

Thank you!

[Kilrah]

Latest seems to be fixed now, so probably best to remove the tag.

 

[aglyons]

Revisiting the port concerns.

 

What if you are not running the container in bridge mode? I have a dedicated IP assigned and the container is stuck at port 8080. Could this be down to the template config? I see that line 30 is setting 8080 hardcoded.

[Kilrah]

You can only map port in bridge mode, when on host or br0 the app's original port is always used. 

It's uncommon for dockerized apps to give a way to change it, especially for something simple like this where there is no reason not to run bridged.

[aglyons]

That would make sense in normal situations but Unraid's docker networking is a little.....unique from what I understand. The default bridge is hooked into the primary NIC of the server. If you want to run your docker containers on a secondary NIC -like me, you have to run that NIC in bridge with Vlans. Each container on that network gets its own IP on the host network. I've set up a number of other containers that use 8080 or the like but when you flip to the custom bridge network, it ignores the container default and uses the defined variable as the port. In my case, 80.

 

In this template, the reverse seems to be the case. Anything other than bridge forces the predefined container port and ignores the provided port variable.

 

This is the first time I've come across a container that acts like this.

[Kilrah]

7 minutes ago, aglyons said:

If you want to run your docker containers on a secondary NIC

Yeah definitely not the standard unraid scenario...

 

There's nothing special about this template though.

7 minutes ago, aglyons said:

Anything other than bridge forces the predefined container port and ignores the provided port variable.

That's standard behavior, weird that you'd have seen otherwise. Note that if you change the ports in the template while on bridge mode then change to something non-bridge the port remains where you had set it which means it's not the app's one anymore and it breaks until you go into the edit dialog and change it, that's everywhere on unraid.

 

Seeing the doc you might be able to change the app port by adding a BIND_ADDRESS variable to the template.

 

 

Edited May 26 by Kilrah

[aglyons]

@Kilrah

 

BINGO!

 

That fixed it. Running on port 80!

 

Thx very much for the tip!

Edited May 26 by aglyons