Why Does My MongoDB Connection Default to 127.0.0.1 Despite Setting a Custom Host?

If you're still seeing attempts to connect to 127.0.0.1 despite setting a different host, consider the following:

Docker Networking Considerations

• n8n Running in Docker
  If n8n is running in Docker on Linux, note that the container’s localhost isn’t the same as the host’s localhost. In that case, you need to set your base URL (in the Ollama credentials) to use an address like host.docker.internal (or the container name if both n8n and Ollama run in separate containers).

• Both Components in Docker
  When both n8n and Ollama are in separate Docker containers, use Docker networking. Configure Ollama to listen on all interfaces (binding to 0.0.0.0) and set the base URL to the Ollama container’s name (e.g., http://my-ollama:11434).

IPv6 vs. IPv4 Issues

• IPv6 Resolution
  If your system has IPv6 enabled, the alias localhost might resolve to ::1 instead. Although the error in your case shows 127.0.0.1, sometimes misconfigured networking can cause unexpected behavior. Using an explicit IP (like host.docker.internal on Docker or the proper container name) can help avoid this conflict.

Double-Check Your Credentials Configuration

• Confirm that the changes you made to the host in the Ollama credentials have been saved and are active.
• Ensure that no environment variable or default setting is overriding your host configuration.

By reviewing and adjusting these settings according to your hosting setup, the node should use the correct host rather than defaulting to 127.0.0.1.