Cloudlfare remote access suddenly stopped working! SRV Record couldn't resolve!

Configuration
1

Hello Guys,
In the past year, i setup a cloudflare tunnel to access my HA remotely as per [
Everything Smart Home] tutorial and everything was working like mint.

Recently without changing any configuration I started getting a cloudflared Error 1033 (Argo Tunnel error)

I am currently stuck with no reference found which help me go forward with my limited networking skills and would appreciate any support from your end.
Below is the cloudflared HA plugin log stating there is an issue in resolving SRV record

Add-on: Cloudflared
 Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
-----------------------------------------------------------
 Add-on version: 5.2.4
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.12.5
 Home Assistant Supervisor: 2024.12.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[21:53:18] INFO: Checking add-on config...
[21:53:18] INFO: Checking for existing certificate...
[21:53:18] INFO: Existing certificate found
[21:53:18] INFO: Checking for existing tunnel...
[21:53:18] INFO: Existing tunnel with ID fdbbf----------------------------- found
[21:53:18] INFO: Checking if existing tunnel matches name given in config
[21:53:20] INFO: Existing Cloudflare Tunnel name matches config, proceeding with existing tunnel file
[21:53:20] INFO: Creating config file...
[21:53:20] INFO: Validating config file...
Validating rules from /tmp/config.json
OK
[21:53:21] INFO: Creating DNS entry mydomain.com...
2024-12-26T18:53:24Z INF mydomain.com is already configured to route to your tunnel tunnelID=fdb--------------------------------------------
[21:53:24] INFO: Finished setting up the Cloudflare Tunnel
[21:53:24] INFO: Connecting Cloudflare Tunnel...
2024-12-26T18:53:25Z INF Starting tunnel tunnelID=fdb---------------------------------
2024-12-26T18:53:25Z INF Version 2024.12.2 (Checksum ---------------------------------)
2024-12-26T18:53:25Z INF GOOS: linux, GOVersion: go1.22.5, GoArch: arm64
2024-12-26T18:53:25Z INF Settings: map[config:/tmp/config.json cred-file:/data/tunnel.json credentials-file:/data/tunnel.json metrics:0.0.0.0:36500 no-autoupdate:true origincert:/data/cert.pem]
2024-12-26T18:53:25Z INF Generated Connector ID: --------------------------------------------
2024-12-26T18:53:25Z INF Initial protocol quic
2024-12-26T18:53:25Z INF ICMP proxy will use 172.30.33.3 as source for IPv4
2024-12-26T18:53:25Z INF ICMP proxy will use ::1 in zone lo as source for IPv6
2024-12-26T18:53:25Z INF ICMP proxy will use 172.30.33.3 as source for IPv4
2024-12-26T18:53:25Z INF ICMP proxy will use ::1 in zone lo as source for IPv6
2024-12-26T18:53:25Z INF Starting metrics server on [::]:36500/metrics
2024-12-26T18:53:25Z INF Tunnel server stopped
2024-12-26T18:53:25Z ERR Initiating shutdown error="Couldn't resolve SRV record &{region1.v2.argotunnel.com. 7844 1 1}: lookup region1.v2.argotunnel.com. on 127.0.0.11:53: no such host"
2024-12-26T18:53:26Z INF Metrics server stopped
Couldn't resolve SRV record &{region1.v2.argotunnel.com. 7844 1 1}: lookup region1.v2.argotunnel.com. on 127.0.0.11:53: no such host
[21:53:26] WARNING: cloudflared crashed, halting add-on
[21:53:26] INFO: cloudflared stopped, restarting...
2

Hello folks,

Everything went back to normal after a some fiddling and HA & plugin reboots.

Yet, i would like to know the possible reasons behind this issue… Anythoughts ?

3

I have the same problem. Has anyone encountered this and knows what causes this error? Previously, the error would disappear after a few hours, and I was able to connect. However, this time the issue has persisted for over 24 hours.

4

Hello Sebastian,

It happened another time, i fully restarted both router and home assistant … nothing happened… later that day I went into the plugin configuration and changed the log level to trace to see if i find any additional details… Suddenly everything was working fine like charm :slight_smile:

5

Hello, I have the same problem.
I uninstalled the plugin, restarted, deactivated, removed all config and redid it from scratch and nothing so far. Any effective solution?

1 Like
6

I have the same issue, and would also value some direction, also tried the same steps.

7

After restarting all my devices that manage internet connections, it apparently went back to normal.