Comment

Comment on [beta] degoog - search engine aggregator

First of all, thanks a ton.

I have been using SearxNG for more than year, running it as docker container on my Homelab. It’s connected to internet via Mullvad VPN.

Lately, I have see both Google and Bing search engines are either not working or returning complete garbage results.

My firewall setup doesn’t allow any incoming connection to homelab, except from LAN. So, bot accessing my SearxNG instance might not be the issue.

With degoog installed in the same fashion (docker + VPN), google engine seems to be unblocked for me (so far).

Not sure why degoog is not getting rate limited like SearxNG on the same system and same VPN. But, at least I’m happy :)

source

Sort:hotnew top

fccview@lemmy.world ⁨1⁩ ⁨week⁩ ago
Aw thank you so much for giving it a try and leaving such a nice feedback ♥️ I am searching in a slightly different way than searxng, can’t promise it’ll work forever but for now it seems to be doing the trick ♥️ I have some more improvements to the search system coming with the next release as Bing does get blocked quite often for me.

P.s. have you been using any extensions? If so what’s your fave so far? Haha

source
- KarnaSubarna@lemmy.ml ⁨6⁩ ⁨days⁩ ago
  Ah! Forget about that part. The docker-compose file you provided on repo works for rootfull docker.
  
  For rootless docker, it works, but library import is not possible for file permission issue.
  
  I think I know how to solve it, I will give it a try over weekend, and will let you know.
  
  source
  - thestrike@lemmy.blahaj.zone ⁨5⁩ ⁨days⁩ ago
    I had the same problem so let me know if you find a solution! I just switched to running as root with podman
    
    source
    KarnaSubarna@lemmy.ml ⁨3⁩ ⁨days⁩ ago
    Note that I’m running it on a rootless docker instance, and NOT on Podman. So, the following solution might or might not work for you.
    
    services: degoog: image: ghcr.io/fccview/degoog:latest volumes: - ./.data:/app/data user: "0:0" ports: - "4444:4444" restart: unless-stopped
    
    Explanation: rootless docker works a bit different from rootful docker. user 1000 (which is you on your server/machine) will be mapped to a different UID (e.g. 32555). This is to ensure that any process in docker container can’t have access to folders/files that you have access to, in case it manages to break free of docker containerization.
    
    When you put user: “0:0” in a rootless docker container, it will assume your UID 1000 (which is you on your server/machine) inside docker container.
    
    While it solves the file permission issue, but it is NOT a recommended way.
    
    with user:1000:1000
    
    Image
    
    with user:0:0
    
    Image
    
    source
    -> View More Comments
  - fccview@lemmy.world ⁨6⁩ ⁨days⁩ ago
    Hey, not sure what you mean, it works perfectly fine as rootless. Are you using docker or podman? Someone else had this issue with podman and we couldn’t figure out why it was different for them.
    
    Everyone else is running this as user 1000, which is what the standard compose requires?
    
    source
    KarnaSubarna@lemmy.ml ⁨3⁩ ⁨days⁩ ago
    Please refer to this comment: lemmy.ml/comment/24567541
    
    If you need any further information, let me know.
    
    source