---
title: "Discussion on \"Managing Multiple Services with Cloudflare Local Tunneling\" | Hashnode"
description: "Discussion on \"Managing Multiple Services with Cloudflare Local Tunneling\". Learn how to expose multiple local apps with a single Cloudflare Tunnel. Configure DNS, ingress rules, HTTPS, and secure access without port forwarding"
url: "https://hashnode.com/posts/managing-multiple-services-with-cloudflare-local-tunneling/6a26dee29d276e3a50a00a05"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Managing Multiple Services with Cloudflare Local Tunneling](https://rahulr.cc/blogs/managing-multiple-services-with-cloudflare-local-tunneling?utm_source=hashnode&utm_medium=feed)

Learn how to expose multiple local apps with a single Cloudflare Tunnel. Configure DNS, ingress rules, HTTPS, and secure access without port forwarding

Jun 8 · 6 min read · rahulr.cc  
Read the article

-   [#cloudflare](https://hashnode.com/tag/cloudflare)
-   [#devops](https://hashnode.com/tag/devops)
-   [#networking](https://hashnode.com/tag/networking)
-   [#selfhosting](https://hashnode.com/tag/selfhosting)
-   [#localtunnelling](https://hashnode.com/tag/localtunnelling)

## Written by

[Rahul Ravindran](https://hashnode.com/@imrhlrvndrn)

@imrhlrvndrn · Mumbai, India

  
[View profile](https://hashnode.com/@imrhlrvndrn)

## Responses 1

Markdown supported · ⌘↵ to post

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 5](https://hashnode.com/posts/managing-multiple-services-with-cloudflare-local-tunneling/6a26dee29d276e3a50a00a05/comment/6aebfcc7bfd08ebda4d31f7d)

A multi-service Cloudflare Tunnel stays boring when every public hostname maps to a stable Compose service name and internal port on the same user-defined network as cloudflared — never a host-published localhost that disappears the moment the connector itself runs in a container. Keep ingress rules hostname-shaped and ordered most-specific first, end with a catch-all that returns 404 so unknown names fail closed, and put Zero Trust Access in front of admin UIs before the app’s own login ever renders. Path-based splits under one hostname need the upstream to understand those prefixes; otherwise you get a silent 200 HTML shell that still cannot load its API.

After a config reload I check active connectors and tunnel availability first, curl each upstream by service name from inside the cloudflared network, then hit the same hostname through the public edge. A 502 with a healthy connector is almost always wrong port, wrong network membership, or a leftover ingress pointing at a renamed service. When you add a second connector for HA, every member must be able to reach every ingress backend it might receive — otherwise failover just moves the miss to a box that cannot see that service.
