TLS handshake error

[wolkenschieber]

When connecting an agent to portainer, the agent is constantly reporting TLS handshake errors:

portainer-agent has been recreated
portainer-agent  | 2024/03/03 12:09PM INF github.com/portainer/agent/cmd/agent/main.go:86 > agent running on Docker platform |
portainer-agent  | 2024/03/03 12:09PM INF github.com/portainer/agent/edge/registry/server.go:101 > starting registry credential server |
portainer-agent  | 2024/03/03 12:09PM INF github.com/portainer/agent/http/server.go:99 > starting Agent API server | api_version=2.19.4 server_addr=0.0.0.0 server_port=9001 use_tls=true
portainer-agent  | 2024/03/03 12:10:28 http: TLS handshake error from 192.168.178.47:56368: EOF
portainer-agent  | 2024/03/03 12:10:28 http: TLS handshake error from 192.168.178.47:56382: EOF
portainer-agent  | 2024/03/03 12:10:28 http: TLS handshake error from 192.168.178.47:56380: EOF
portainer-agent  | 2024/03/03 12:10:32 http: TLS handshake error from 192.168.178.47:42072: EOF
portainer-agent  | 2024/03/03 12:10:40 http: TLS handshake error from 192.168.178.47:33828: EOF
portainer-agent  | 2024/03/03 12:10:42 http: TLS handshake error from 192.168.178.47:33838: EOF
portainer-agent  | 2024/03/03 12:10:43 http: TLS handshake error from 192.168.178.47:33850: EOF

The agents image is portainer/agent:alpine, portainer's image is portainer/portainer-ee:latest.

[Wamy-Dev]

same issue for me

[daidaiwood]

I also encountered this problem.

[lessless]

same issue

[dierochade]

I get this error only when i want to open a terminal in the agent container via Portainer-GUI button....

[MNLierman]

Same issue here as well. I started on a new Portainer system and initially the Agent connected with the server fine for a while, and then I'm unsure what happened but it disconnected. Leading me to waste over 2 hours trying to troubleshoot ports and connections. The Portainer UI doesn't even state anything about TLS handshake, it simply says timeout occurred. After testing with netcat and determining that this wasn't a firewall issue, I happened across the logs which states unknown certificate.