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
Uptime Kuma was recently added axios-cached-dns-resolve and was released yesterday. Unfortunately, it seems that it is not working well in local environment like Tailscale/Wireguard. After changing back to the normal axios client without axios-cached-dns-resolve, it is back to normal.
Make a request using axios-cached-dns-resolve and using a url with custom domain such as http://my-server:8096
👀 Expected behavior
It should be working like a normal axios.
😓 Actual Behavior
In my case, it is connection timeout. Someone got ECONNREFUSED error.
Version
axios-cached-dns-resolve: 3.1.0
Node.js 16
The text was updated successfully, but these errors were encountered:
louislam
changed the title
[Transfer issues from Uptime Kuma] axios-cached-dns-resolve does not work well in some local environments like Tailscale/Wireguard.
[Transfer issues from Uptime Kuma] axios-cached-dns-resolve does not work well in some local networks like Tailscale/Wireguard.
Jun 23, 2022
Description
Uptime Kuma was recently added axios-cached-dns-resolve and was released yesterday. Unfortunately, it seems that it is not working well in local environment like Tailscale/Wireguard. After changing back to the normal axios client without axios-cached-dns-resolve, it is back to normal.
The code changes: louislam/uptime-kuma#1598
Related issues
It does not resolve local domain names correctly.
HTTP checks on non-standard ports reporting as down louislam/uptime-kuma#1821
It does not respect /etc/hosts
Latest release seems to not respect /etc/hosts louislam/uptime-kuma#1822
👟 Reproduction steps
👀 Expected behavior
It should be working like a normal axios.
😓 Actual Behavior
In my case, it is connection timeout. Someone got
ECONNREFUSED
error.Version
axios-cached-dns-resolve: 3.1.0
Node.js 16
The text was updated successfully, but these errors were encountered: