Thank you so much, sorry it’s taken so long to reply. I still haven’t had the time, but I will take a closer look when I get the chance.

Thank you so much, sorry it’s taken so long to reply. I still haven’t had the time, but I will take a closer look when I get the chance.

Thank you so much, sorry it’s taken so long to reply. I still haven’t had the time, but I will take a closer look when I get the chance.

Thank you so much, sorry it’s taken so long to reply. I still haven’t had the time, but I will take a closer look when I get the chance.

also I noticed that it doesn’t really protect our privacy if we simply host it on our laptop. and most indivious instance are barely usable (freetube always gives indivious API error) so I guess the best option now is to install some fingerprint blocker and view utb in browser

hosted it and when clicking on any video it returns Error: non 200 status code. Youtube API returned status code 400. It that caused by SABR? searched on google but doesn’t seem like other have this issue on indivious

I do have learnt a lot but I haven’t solved the problem 😱 🤓 🫠

SN_FR_@SN:~$ sudo docker exec -it searxng sh -c "id"
uid=0(root) gid=0(root) groups=0(root)

container is running as root, so there shouldn’t be any permission error?

u are right its not writable, the files are read only, that is wierd

I’m opening those files with windows but the user permission inside docker shouldn’t cause that problem.

I’m scratching my head nw

u are right its not writable, the files are read only, that is wierd

I think I do have permission to the directory?

~ # ls -la /etc/searxng
total 72
drwx------    1 1026     100             42 May 17 04:49 .
drwxr-xr-x    1 root     root           494 May 17 05:24 ..
----------    1 root     root         68667 May 17 04:49 settings.yml
----------    1 root     root          1223 May 17 04:49 uwsgi.ini

___

~ # ls /etc/searxng
settings.yml  uwsgi.ini
~ # cat settings.yml
cat: can't open 'settings.yml': No such file or directory
~ # cat /etc/searxng/settings.yml
general:
  # Debug mode, only for development. Is overwritten by ${SEARXNG_DEBUG}
  debug: false
  # displayed name
  instance_name: "searxng"
  # For example: https://example.com/privacy

I think I do have the permission?

I tried removing cap_drop (as instructed on https://github.com/searxng/searxng-docker/issues/115) but no luck, the permission error still exists. And also there occurs a new error no python application found

thank you!

thank you!

deleted by creator

deleted by creator

deleted by creator

deleted by creator

Listen on [::]:8080 doesn’t give 20054, could this be the reason?

Listen on [::]:8080

[uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini

open("/etc/searxng/uwsgi.ini"): Permission denied [core/io.c line 525]

SearXNG version 2025.5.16+1b08324

Use existing /etc/searxng/uwsgi.ini

Use existing /etc/searxng/settings.yml

Listen on [::]:8080

[uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini

open("/etc/searxng/uwsgi.ini"): Permission denied [core/io.c line 525]

SearXNG version 2025.5.16+1b08324

Use existing /etc/searxng/uwsgi.ini

Use existing /etc/searxng/settings.yml

Listen on [::]:8080

[uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini

open("/etc/searxng/uwsgi.ini"): Permission denied [core/io.c line 525]

sorry that is a typo in the post lol