Orphaned tunnels

[jayscovill]

Seeing this in my console for my agents. They still seem to work but Resolve doesn't do anything. Should I be worried?

[ChrispyBacon-dev]

It seems to be a bug. Was it a migration from an existing tunnel? I have 3 agents up and running and one is orphaned as well so I'm seeing the same issue. It has something to do with the migration function. A plan a hotfix soon 👍

Cheers,
chris

[ChrispyBacon-dev]

I found the root cause. When Docker containers are with the old label "cloudflare.tunnel" running, this is currently not included in the migration logic. I will add a hotfix, but for an immediate fix on your side, check your Docker stacks/Compose files and change the "cloudflare.tunnel.hostname=.." labels to "dockflare.hostname=..." and so on. I had as well two older docker containers that are running static websites with the old cloudflare.tunnel labels after changing the labels to dockflare and retriggering the migration it got resolved.

[ChrispyBacon-dev]

With the latest hotfix, this issue is resolved. If you still see the tunnel orphaned after an update, trigger a migration; it will fix that (tested this).