Skip to content
← Back to activity

Solution skill

Cloudflare tunnel with ingress not working as expected (Cloudflare Zero Trust)

Version 3Sign in to save

Complete solution

Shows how to fix cloudflare tunnel with ingress not working as expected (Cloudflare Zero Trust). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Go to DNS settings of your cloudflare account and update the CNAME records for your hosts that you want routed through the tunnel so that the target points to newtunnelid.cfargotunnel.com. I also upgraded my cloudflared instance in the process.

When to use

You are seeing this: From the accepted Stack Overflow answer: OK, so after trying everything and (unsuccessfully) requesting support on Cloudflare community pages, I ended up solving the problem by simply deleting and creating the tunnel anew. Use this skill when you run into "Cloudflare tunnel with ingress not working as expected (Cloudflare Zero Trust)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

From the accepted Stack Overflow answer: OK, so after trying everything and (unsuccessfully) requesting support on Cloudflare community pages, I ended up solving the problem by simply deleting and creating the tunnel anew. I also upgraded my cloudflared instance in the process. So, the steps to delete and the create the tunnel again: cloudflared tunnel delete yourtunnelname then cloudflared tunnel create yourtunnelname then copy the new tunnel ID from the cli output in the terminal and complete the following steps: Find and open the config.yaml file in the .cloudflared folder on your root user and paste the new tunnel ID over where the old one was. Go to DNS settings of your cloudflare account and update the CNAME records for your hosts that you want routed through the tunnel so that the target points to newtunnelid.cfargotunnel.com . Then run the tunnel, and ingress starts working as expected.

Context: Problem: Accepted solution (score 5): OK, so after trying everything and (unsuccessfully) requesting support on Cloudflare community pages, I ended up solving the problem by simply deleting and creating the tunnel anew. I also upgraded my cloudflared instance in the process. So, the steps to delete and the create the tunnel again: cloudflared tunnel delete yourtunnelname then cloudflared tunnel create yourtunnelname then copy the new tunnel ID from the cli output in the terminal and complete the following steps: Find and open the config.yaml file in the .cloudflared folder on your root user and paste the new tunnel ID over where the old one was. Go to DNS settings of your cloudflare account and update the CNAME records for your hosts that you want routed through the tunnel so that the target points to newtunnelid.cfargotunnel.com . Then run the tunnel, and ingress starts working as expected.

Evidence

Source: Problem: Accepted solution (score 5): OK, so after trying everything and (unsuccessfully) requesting support on Cloudflare community pages, I ended up solving the problem by simply deleting and creating the tunnel anew. I also upgraded my cloudflared instance in the process. So, the steps to delete and the create the tunnel again: cloudflared tunnel delete yourtunnelname then cloudflared tunnel create yourtunnelname then copy the new tunnel ID from the cli output in the terminal and complete the following steps: Find and open the config.yaml file in the .cloudflared folder on your root user and paste the new tunnel ID over where the old one was. Go to DNS settings of your cloudflare account and update the CNAME records for your hosts that you want routed through the tunnel so that the target points to newtunnelid.cfargotunnel.com . Then run the tunnel, and ingress starts working as expected.

Verified resolution: From the accepted Stack Overflow answer: OK, so after trying everything and (unsuccessfully) requesting support on Cloudflare community pages, I ended up solving the problem by simply deleting and creating the tunnel anew. I also upgraded my cloudflared instance in the process. So, the steps to delete and the create the tunnel again: cloudflared tunnel delete yourtunnelname then cloudflared tunnel create yourtunnelname then copy the new tunnel ID from the cli output in the terminal and complete the following steps: Find and open the config.yaml file in the .cloudflared folder on your root user and paste the new tunnel ID over where the old one was. Go to DNS settings of your cloudflare account and update the CNAME records for your hosts that you want routed through the tunnel so that the target points to newtunnelid.cfargotunnel.com . Then run the tunnel, and ingress starts working as expected.

Source URL: https://stackoverflow.com/questions/76234465/cloudflare-tunnel-with-ingress-not-working-as-expected

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_PkXtRkivFeMC1cAniyB1TA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cloudflare tunnel with ingress not working as expected (Cloudflare Zero Trust) <span>— Vectle</span></a>