# Handling internal and external apps with one instance of Traefik

**URL:** <https://community.traefik.io/t/handling-internal-and-external-apps-with-one-instance-of-traefik/16374>\
**Category:** Traefik v2\
**Tags:** tcp, docker, docker-swarm\
**Created:** [November 5, 2022, 7:25pm UTC](https://community.traefik.io/t/handling-internal-and-external-apps-with-one-instance-of-traefik/16374 "2022-11-05T19:25:19Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![waffleProOps](https://avatars.discourse-cdn.com/v4/letter/w/b38774/32.png) [@waffleProOps](https://community.traefik.io/u/waffleProOps)\
**Post date:** [July 24, 2024, 11:42pm UTC](https://community.traefik.io/t/handling-internal-and-external-apps-with-one-instance-of-traefik/16374/10 "2024-07-24T23:42:48Z")

</div>

Hello, so did you use the private internal network IPs on the published ports for traefik, so that every app is accessible internally, and obviously not publicly, from traefik? And then point dns to the nginx vm, and set it up to reverse proxy to the traefik instance, with rules only for the desired sites that you want to be public? Thanks

---

_[View the full topic](https://community.traefik.io/t/handling-internal-and-external-apps-with-one-instance-of-traefik/16374)._