Learn about Docker networks and how they connect containers.
Learn about Docker networks and how they connect containers.
Good evening. You're trying to configure Searxng with Docker, using a VM that manages reverse proxies and Let's Encrypt certificates. When it works locally, but fails when using URLs, you're getting a 503 error. Your docker-compose.yml seems correct, but here are some points to check:
- Ensure the virtual host is properly mapped to the correct port (8080) in your compose file.
- Confirm that the reverse proxy settings are correctly pointing to your VM's IP and the internal port.
- Verify that the Searxng image supports forwarding requests from the external URL to the local IP.
- Check firewall rules on both the VM and the host machine.
- Make sure the Let's Encrypt certificate is properly installed and accessible via the proxy.
- Test with a simple HTTP request first to isolate the issue.
Let me know if you need further assistance!
You're asking about adjusting how SearXNG connects to a service. The setup involves changing port settings in the docker-compose.yml file to use a URL instead of an IP address. This would allow Apache to reach port 8080 on the host, while SearXNG communicates via that URL. The current configuration lists port 80, which forwards to 8080 inside the container, causing a conflict since both try to use port 8080. Switching to "8080:8080" and updating Apache to listen at "127.0.0.1:8080" should resolve the issue.