website/src/app/kb/use-cases/web-app-access/readme.mdx
import PlanBadge from "@/components/PlanBadge"; import SupportOptions from "@/components/SupportOptions"; import Alert from "@/components/DocsAlert"; import Link from "next/link"; import Image from "next/image";
<PlanBadge plans={["starter", "team", "enterprise"]}>
In this guide, we'll use Firezone to set up access to a private web application such as GitLab or Metabase. This is useful when you have a web app hosted behind a firewall that you want to keep secure, but still need to access it from external networks like the internet.
<Alert color="info"> This steps in this guide can be effectively applied to virtually any service, not just web applications. </Alert>Sites -> <site> and
click the Add Resource button.DNS as the Resource type.metabase.company.com. This address must be resolvable by all of the
Gateway(s) in your Site.TCP/80 and/or TCP/443 to
further limit access to this Resource to HTTP and/or HTTPS traffic only (Team
and Enterprise plans).Procurement team Metabase instance. This will be used to identify the
Resource in the Firezone admin portal.Policies tab, click the Add Policy button.You've now secured access to your private web app with Firezone. You can now test access from any signed-in Client by visiting the address you specified in Step (1):
<Link href="/images/kb/use-cases/web-app-access/step3.png" target="_blank" rel="nofollow" > <Image src="/images/kb/use-cases/web-app-access/step3.png" alt="Access the web app" width={1200} height={1200} /> </Link> <SupportOptions />