mirror of
https://github.com/coollabsio/coolify-docs.git
synced 2026-06-19 07:35:55 +00:00
Andras Bacsai
a64450ae9d
Replace VitePress/Vue stack with Fumadocs MDX, TanStack Start, React 19, and Vite. Migrate all documentation content to MDX under content/docs/. Add full src/ app with React components, routing, search, and API page. Remove Korrektly integration from CI/CD workflows, Dockerfile, and env vars. Update build pipeline to output to .output/public instead of docs/.vitepress/dist.
47 lines
2.5 KiB
Plaintext
47 lines
2.5 KiB
Plaintext
---
|
||
title: "Cloudflare Tunnels"
|
||
description: "Connect Coolify resources securely without port forwarding using Cloudflare Tunnels for all resources, single apps, SSH access, or full HTTPS setups."
|
||
---
|
||
|
||
# Cloudflare Tunnels
|
||
|
||
[Cloudflare Tunnels](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/) allow you to securely expose your local server or applications to the internet without opening ports on your router.
|
||
|
||
This makes them a great option for hosting projects on devices like old laptops or Raspberry Pis.
|
||
|
||
## Why Use Cloudflare Tunnels?
|
||
|
||
- No need to open or forward ports on your device to the public internet.
|
||
- Simplifies routing and DNS configuration.
|
||
- Supports exposing a single application or multiple services.
|
||
- Hides your server's IP address by routing traffic through a Cloudflare Tunnel, showing only your domain.
|
||
- Works even if you have a dynamic IP (or) no public IP at all.
|
||
- Eliminates the hassle of managing and setting up SSL certificates.
|
||
|
||
## When Not to Use Cloudflare Tunnels?
|
||
|
||
- If you prefer direct access to your server without a proxy layer.
|
||
- If you're concerned about routing traffic through Cloudflare's servers.
|
||
- If you rely on additional firewall tools, as Cloudflare Tunnels bypass all firewall rules.
|
||
- If you need SSL certificates trusted by entities other than Cloudflare.
|
||
|
||
## Ways to Use Cloudflare Tunnels with Coolify
|
||
|
||
You can set up Cloudflare Tunnels with Coolify in several ways, depending on your needs. Below are the available options, each linked to a detailed guide for easy setup:
|
||
|
||
1. [All Resources](/integrations/cloudflare/tunnels/all-resource) -> Use a tunnel for all resources deployed through Coolify. This is the **easiest** and **most recommended** way for beginners.
|
||
|
||
2. [Single Resource](/integrations/cloudflare/tunnels/single-resource) -> Use a tunnel for a single resource deployed through Coolify.
|
||
|
||
3. [Server SSH Access](/integrations/cloudflare/tunnels/server-ssh) -> Securely connect your server to Coolify using a domain through Cloudflare Tunnel.
|
||
|
||
4. [Full HTTPS/TLS](/integrations/cloudflare/tunnels/full-tls) -> Setup always-on **HTTPS** for all domains and subdomains. Normally, Coolify uses **HTTP** while Cloudflare manages **HTTPS**. If certain apps require **HTTPS** directly on Coolify.
|
||
|
||
|
||
<Callout type="success" title="Tip:">
|
||
|
||
It’s highly recommended to go with the first option [All Resources](/integrations/cloudflare/tunnels/all-resource) if you're new to Coolify and Cloudflare Tunnels, as it’s much easier to set up and manage.
|
||
|
||
</Callout>
|
||
|