Max retries exceeded with url /iscon/con/con/process (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 110] Connection timed out'))

General
1

Hi Everyone,

i’m seeing below error for docker containers can you please help to fix.

Failed in FTP Helper:HTTPConnectionPool(host=‘10.106.141.45’, port=28426): Max retries exceeded with url: /isconnector-prod/connectors/connection/process (Caused by NewConnectionError(‘: Failed to establish a new connection: [Errno 110] Connection timed out’))

2026-01-02 11:51:37.959 ERROR 268 — [Thread-1] com.iri.aa.aecp.node.apps.WebAppTask : Error while calling the healthcheck api for requestId 3052992 - org.springframework.web.client.ResourceAccessException: I/O error on GET request for “http://10.106.4.11:28411/isflowmanag/aecp/cluster/heartBeat/aa-is-prod-facuat/aa-is-prod-facuat-pys”: Connect to 10.106.4.11:28411 [/10.106.4.11] failed: connect timed out; nested exception is org.apache.http.conn.ConnectTimeoutException: Connect to 10.106.4.11:28411 [/10.106.4.11**] failed: connect timed out

following are version details **

CentOS Linux release 7.9.2009 (Core)
Docker version 26.1.4, build 5650f9b
Docker Compose version v2.21.0

1 Like
2

Why do you think this is Docker related? It’s a network issue. Is your target reachable?

To get support, you would need to provide more context.

3

yes my target ip & port is reachable , it’s intermittent issue seems some limit got reached & do we know the limit

4

The error is clear: the source can not connect to the target. You don’t explain what the source is, you don’t explain what the target is, not even if it’s an internal service. We don’t know if both are containers, we don’t know anything. How should we help?

5

Both are containers one is cluster another one is application, cluster containers calls app container’s API to check the status of cluster , below is the API which is being called from cluster container

http://10.106.3.13:29428/isflowmanagement-prd/aecp/cluster/heartBeat/aa-is-prod-facuata-pys-lg/aa-is-prod-facuata-pys-lg

6

What’s a cluster container? Have you tried the basic network checks, for example with ping?

Are those containers on different nodes? How are those containers connected, via a Docker Swarm network?

7

all basic check was done , ping , telnet , traceroute , please let me know if any kernel parameter we need to change.

containers are on different node , docker containers (VMs) are running on docker network & apps are running on host network on different nodes

8

Docker containers are not VMs. You need to ensure you publish ports, so other services can connect to them.

Make sure your target is listening on all IPs (0.0.0.0), not only on localhost (127.0.0.1).

9

it’s intermittent , not always , VM i mean to say OS is running as container , all ports are published & connecting from other severs via telnet as i mentioned above

10

If it doesn’t always happen, that also seems to point to a more general network issue. At least I don’t remember network issues caused by Docker CE intemittently. If it happens only from containers, you can check if MTU settings are correct and there is no big difference between the MTU of the docker networks and your LAN network. Running ip addr | grep -v 'lo:' | grep mtu can show your the MTU on the interfaces.

If you need to, you can change the mtu on Docker networks too.