Fix Docker networking between Node server and SearXNG#8
Draft
Fix Docker networking between Node server and SearXNG#8
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
…c, and Dockerfile - docker-compose.yml: Add Node.js server service with SEARXNG_URL=http://searxng:8080, shared macai-net bridge network, depends_on for startup ordering, and fix SEARXNG_BASE_URL to use internal Docker hostname - Dockerfile: Add multi-stage build for the Node.js server - server.js: Replace single 3s startup health check with 5-attempt retry loop (5s timeout each, 3s delay between) to handle Docker cold-start timing - README.md: Document Docker and host-mode usage, environment variables Co-authored-by: sriail <225764385+sriail@users.noreply.github.com>
Co-authored-by: sriail <225764385+sriail@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix SearXNG API endpoint configuration for Node.js server
Fix Docker networking between Node server and SearXNG
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Node server running in Docker cannot reach SearXNG via
localhost:8888—localhostresolves to the container itself, not the host. CausesECONNREFUSED,AbortError, and/healthztimeouts.Changes
docker-compose.yml: Addserverservice withSEARXNG_URL=http://searxng:8080(internal DNS + internal port), sharedmacai-netbridge network,depends_onordering. FixSEARXNG_BASE_URLto match.Dockerfile: New —node:20-alpinesingle-stage build for the server.server.js: Replace single 3s startup health check with 5-attempt retry loop (5s timeout, 3s backoff). Handles Docker cold-start race where SearXNG isn't ready yet. Breaks immediately on HTTP errors (reachable but unhealthy) vs retrying only on connection failures.README.md: Document both modes and env vars.Networking model
SEARXNG_URLhttp://searxng:8080http://localhost:88888888→8080The Compose file sets
SEARXNG_URLexplicitly for the container case; theserver.jsdefault (localhost:8888) covers host-mode with no config needed.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
searxng/home/REDACTED/work/_temp/ghcca-node/node/bin/node node -e import('./server.js').catch(() => {});(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.