I followed the steps laid out in this guide and have a docker container for all services needed up and running, with the searxng container running on port 8080. I, however, am not sure how to actually access the search engine. I tried going to the server address in my web browser, including the port, but nothing shows up. I have another container running pihole, so i know i can access other containers web interfaces. Any help would be appreciated. Thanks in advance!

  • MaggiWuerze@feddit.deEnglish
    1·
    1 year ago

    Looking at the compose and .env file you have to just call the hostname of your machine on port 80:

    SEARXNG_HOSTNAME=${SEARXNG_HOSTNAME:-http://localhost:80}

    Since that is probably already taken you might have caddie not starting properly

  • ArbiterXero@lemmy.worldEnglish
    1·
    1 year ago

    What port did you expose it on through docker?

    Within docker, the server port is internal to docker (like a vm) and then there’s an external port that you map it to on the host…

    Can you give me the command you use to launch it?

    What is the error you get in the browser? Timeout? 500?

    • BarrymoreOPEnglish
      1·
      1 year ago

      Thanks so much for a quick reply, you’re awesome! I believe still 8080, i didn’t set a custom port anywhere, here is my docker ps

      nathan@pop-os /usr/local/searxng-docker$ sudo docker ps 1 ↵ CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 122541a0442e redis:alpine "docker-entrypoint.s…" 26 minutes ago Up 26 minutes 6379/tcp redis 8031ada30eea searxng/searxng:latest "/sbin/tini -- /usr/…" 26 minutes ago Up 26 minutes 127.0.0.1:8080->8080/tcp searxng cdf75064d7c7 pihole/pihole:latest "/s6-init" 17 hours ago Up 11 hours (healthy) 0.0.0.0:53->53/udp, :::53->53/udp, 0.0.0.0:53->53/tcp, :::53->53/tcp, 0.0.0.0:80->80/tcp, 0.0.0.0:67->67/udp, :::80->80/tcp, :::67->67/udp pihole

      To launch the container i used

      sudo docker-compose up -d

      And there really isn’t an error as i just don’t know how to actually access it

      • MangoPenguinEnglish
        3·
        1 year ago

        Are you accessing this via 127.0.0.1?

        If not you need to change it to 8080:8080 instead of 127.0.0.1:8080:8080

      • blah@lemmy.1204.orgEnglish
        1·
        1 year ago

        Where is this running on? If this is your own computer, http://127.0.0.1:8080 is how you access it. If it is another computer, remote or not, you need to change how you start the container to be able to access it.