使用GGR连接本地Selenoid时出现connection refused错误求助

Got it, let's figure out why GGR can't reach your Selenoid instance. That dial tcp 127.0.0.1:4445: connect: connection refused error is a classic Docker networking issue—here's how to fix it:

Why This Happens #

When your GGR container tries to hit http://localhost:4445, it's not pointing to your host machine. Each Docker container has its own isolated network stack, so localhost inside GGR refers only to the GGR container itself, not the host where Selenoid is mapped to port 4445.

Step-by-Step Troubleshooting & Fixes #

1. Check if GGR and Selenoid Share the Same Network

Docker containers can only communicate directly if they're on the same network. Let's verify:

• List all your Docker networks:

  docker network ls
  

• Check which network Selenoid is using:

  docker inspect selenoid | grep -A 10 "Networks"
  

• Do the same for GGR:

  docker inspect ggr | grep -A 10 "Networks"
  

If they're on different networks, connect GGR to Selenoid's network with:

docker network connect <name-of-selenoid-network> ggr

2. Update GGR's Quota Configuration to Use Selenoid's Container Address

Your GGR quota files (stored in /etc/grid-router/quota) are using the wrong address. Instead of localhost:4445, you need to use:

• Either the container name of Selenoid (selenoid) and its internal port (4444—not the host-mapped 4445), or
• The internal IP address of the Selenoid container (you can get this from the docker inspect selenoid output).

Here's an example of a corrected quota file (e.g., quota/selenoid-pool.yaml):

- name: "Main Selenoid Pool"
  url: "http://selenoid:4444/wd/hub"
  quota: 10  # Adjust this number based on how many concurrent sessions you need

3. Restart GGR to Apply the New Configuration

docker restart ggr

4. Verify Connectivity Inside the GGR Container

To make sure the fix works, hop into the GGR container and test access to Selenoid:

docker exec -it ggr bash
# First, ping Selenoid to confirm network connectivity
ping selenoid
# Then check if Selenoid's status endpoint is reachable
curl http://selenoid:4444/status

If both commands succeed, GGR should now be able to route traffic to Selenoid without issues.

Quick Reminder #

The port mapping 0.0.0.0:4445->4444/tcp on your Selenoid container is only for accessing Selenoid from your host machine or external devices. When containers talk to each other, they use the internal port (4444) directly.

内容的提问来源于stack exchange，提问作者pepe pepito