-
|
Version of SearXNG, commit number if you are using on master branch and stipulate if you forked SearXNG The latest build by the Installation Script How did you install SearXNG? By the Installation Script What happened? After finishing the installation, including the SearXNG uWSGI instance, and everything was launched, the port listening didn't work! Background: I was using nginx stream to proxy TCP traffic at port 443 to backend servers (SearXNG is one of them), however I always got a nginx 111 unknown upstream error. I have no idea why it didn't work until I used How To Reproduce set a port in settings.yml, launch SearXNG uWSGI instance server. Expected behavior the port is listened. Screenshots & Logs Additional context I'm a noob so if I made some stupid mistake please forgive me :( |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Figured it out. uWSGI running nicely doesn't mean searxng is daemonised...I'm stupid. |
Beta Was this translation helpful? Give feedback.
Figured it out. uWSGI running nicely doesn't mean searxng is daemonised...I'm stupid.
Have to configure systemd to daemonise searxng.