Skip to content

named tunnel is unreliable when multiple sites are exposed #225

Description

@iamphonghg

Expected Behavior

all enabled sites should remain reachable through the same named tunnel at the same time.

Actual Behavior

after removing and re-enabling an exposed site, cloudflare sometimes returns 502 for both sites. sometimes only one site works. i cannot make both public sites work reliably at the same time.

i uninstalled yerd and reinstalled 2.0.4 stable, but the same behavior persisted.

Steps to Reproduce the Problem

  1. run yerd with two or more linked and secured sites.
  2. expose them through one named tunnel.
  3. remove one exposed site and enable it again.
  4. open both public hostnames.
  5. repeat the remove and enable steps.

sometimes both sites return 502 and sometimes only one works.

Where did it happen?

Desktop app (GUI)

Platform

macOS

Version

2.1.0-rc.1 (latest pre-release initially used); 2.0.4 stable after uninstall and reinstall

GUI Logs

yerd gui showed the tunnel as running, but there was no useful gui error.

Daemon Logs

no yerdd logs available.

related cloudflared trace captured while reproducing the 502:
cloudflared 2026.8.2 on macos arm64.
unable to reach the origin service:
dial tcp 127.0.0.1:8443: connect: operation timed out

yerd status at the time:
https 443 -> 8443 (redirected)
port_redirect: true

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions