You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Strangely it seems like we forgot to set the axios timeout for Docker monitors. We can add a temporary fix, and/or wait after #2142 gets merged and we can add configurable timeout support for the Docker monitor as well.
We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.
🛡️ 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
The text was updated successfully, but these errors were encountered: