What is the best recommendation for overcoming an ETIMEDOUT false alarm for a docker? #1794

New issue

Open

opened 2026-02-28 02:32:51 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-28 02:32:51 -05:00

Owner

Originally created by @miguelarios on GitHub (Jan 17, 2023).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

I have a few dockers (not all) that are getting an ETIMEDOUT it is not regularly happening as in on a predictable standpoint so just curious if I should just extend the 60s to 120s or if there is something else.

I'm using docker-socket-proxy to proxy my docker socket inside Tailscale between my homelab in my LAN and a VPS where uptime kuma resides.

🐻 Uptime-Kuma Version

1.19.3

💻 Operating System and Arch

Debian 5.10.149

🌐 Browser

Firefox 108.1

🐋 Docker Version

Docker 20.10.22

🟩 NodeJS Version

No response

Originally created by @miguelarios on GitHub (Jan 17, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I have a few dockers (not all) that are getting an ETIMEDOUT it is not regularly happening as in on a predictable standpoint so just curious if I should just extend the 60s to 120s or if there is something else. I'm using docker-socket-proxy to proxy my docker socket inside Tailscale between my homelab in my LAN and a VPS where uptime kuma resides. ### 🐻 Uptime-Kuma Version 1.19.3 ### 💻 Operating System and Arch Debian 5.10.149 ### 🌐 Browser Firefox 108.1 ### 🐋 Docker Version Docker 20.10.22 ### 🟩 NodeJS Version _No response_