[Solved] How to use searxng with flowise using local-ai-package?

Local AI
1

Hello,

I’m trying to use searxng with flowise.

But maybe I use the wrong url in flowise: http://searxng:8080

Here the screenshot of the problem:

image
image1221×587 63.7 KB

It seems that searxng is not running well:

When I run sudo docker network inspect localai_default I can see ollama, n8n, but I can’t see searxng.

When I run

sudo docker logs searxng

SearXNG version 2025.5.10+e982b9f73
Create /etc/searxng/uwsgi.ini
cp: cannot create regular file '/etc/searxng/uwsgi.ini': Permission denied
sed: can't read /etc/searxng/uwsgi.ini: No such file or directory
Use existing /etc/searxng/settings.yml
Listen on [::]:8080
realpath() of /etc/searxng/uwsgi.ini failed: No such file or directory [core/utils.c line 3640]
SearXNG version 2025.5.10+e982b9f73
Create /etc/searxng/uwsgi.ini
cp: cannot create regular file '/etc/searxng/uwsgi.ini': Permission denied
sed: can't read /etc/searxng/uwsgi.ini: No such file or directory
Use existing /etc/searxng/settings.yml
Listen on [::]:8080

it seems there is problems.

With local-ai-package, have you got searxng that is working well?

Thanks :slight_smile:

2

Seems like a problem with your install, yes.

SearXNG is working, which I showed e.g. in this video:

1 Like
3

Thanks for your reply.

Thanks to your feedback I was able to better target the problem and the following actions were able to solve the problem:

sudo chmod -R 777 ./searxng

sudo docker stop searxng

sudo docker rm searxng

sudo docker compose -p localai --profile gpu-nvidia -f docker-compose. yml -f supabase/docker/docker-compose.yml down

sudo docker compose -p localai --profile gpu-nvidia -f docker-compose.yml -f supabase/docker/docker-compose.yml pull

sudo python3 start_services.py --profile gpu-nvidia

And now it works with http://searxng:8080

However, I don’t know if the above method is clean, and I don’t understand why I had to do this action when you didn’t have to. If you remember whether you had to change the rights on the folder, I’d be interested to know. Maybe it’s because I’m on debian and rights management is different. Do you think I should create a bug report or its not necessary?

In any case, thank you very much once again for your precious help!

4

Glad it works now for you. I dont think it should be necessary to change rights. If you watch my install video for the local package on a VPS Server with Ubuntu on it, it works fine. Dont think there is much difference to debian regarding this.

1 Like
5

Thank you very much for your reply and for this video which is great and super useful, I may try to apply it in the next few weeks, if you have an affiliate link for hetzner, don’t hesitate to pass it on to me if it helps.

1 Like
6

Thanks, no dont have affiliate for hetzner.