[Enhancement]: Cloudflared Portal: Management of CF Tunnel and tools to manage the domains with it

[rootacc3ss]

Request Type

New Feature

Description

This was my suggestion message via Coolify, I have never used Algora before, but I don't like fiat and avoid doxxing myself, so I will pay whichever user decides to add this functionality a cool penny in crypto because it's expansive. CLEAR IT WITH ME FIRST IF YOU WANT TO GET PAID! Anyways, here was my suggestion message:

I made the mistake of setting up Cloudflared for ALL resources following that and the HTTPS guide. I notice there's no way to keep the old HTTPS ACME challenge thing in Traefik nor is there an easy way to manage cloudflared tunnels and exclude resources from them. I purchased a WHOLE other dedicated IP to make dockers excluded from the Coolify network I have but I love Coolify so I'd like to be able to manage these services that CANNOT use Cloudflared under there!

The issue is that I'd follow the guide for Cloudflared tunneling specific resources but I need it for all of them minus maybe one or two...

And, while I'm at it, not just clustering support for docker but more load balancing and CDN based features would be killer.

I'll post this on the Github and see what people think, but management of the Cloudflared proxy is important, and maybe it should be even easier, especially when we have the Cloudflare API, to automatically configure new origin certs, public hostnames, etc

[djsisson]

@rootacc3ss use dns challenge or add the cf origin cert in order to use https through a tunnel, you dont need to exclude anything

if you have your wildcard going through cloudflared, then any domains you do not want to go through it, you just add the dns entries, named entries take precedence over a wild card.

you're sort of asking someone to reinvent the wheel, the cloudflared dashboard, and access dashboard, already manage all of this with great detail. down to limiting access to domains to individual users.

[rootacc3ss]

is there an easy way to do this for mail access, which is my purpose? MX and other mail traffic will not go through any server fully proxied thru a cloudflared tunnel.

My suggestion for load balancing and CDN features built in stands

Thanks for trying to help! LMK!

[djsisson]

the tunnel is primarily for http traffic, you can run other traffic through it like tcp, but it needs to go via cloudflared websocket first

so for mail traffic, this needs to be outside of the tunnel, i.e a direct domain with a port binding either direct from a container or via a tcp entrypoint in a proxy, you cant use a tunnel for this

im not sure what you mean by load balancing / cdn features?

load balancing is automatic when using a tunnel, you can have multiple tunnels all use the same id, then cloudflare will use the closest one to the source request, i.e to load balance you need multiple servers, coolify can already manage multiple servers.

for cdn, if you are using cloudflare just use their cache, or a worker with their r2 buckets

[rootacc3ss]

the tunnel is primarily for http traffic, you can run other traffic through it like tcp, but it needs to go via cloudflared websocket first

so for mail traffic, this needs to be outside of the tunnel, i.e a direct domain with a port binding either direct from a container or via a tcp entrypoint in a proxy, you cant use a tunnel for this

im not sure what you mean by load balancing / cdn features?

load balancing is automatic when using a tunnel, you can have multiple tunnels all use the same id, then cloudflare will use the closest one to the source request, i.e to load balance you need multiple servers, coolify can already manage multiple servers.

for cdn, if you are using cloudflare just use their cache, or a worker with their r2 buckets

There's got to be a more simple way to exclude resources from the tunnel entirely after the full tunnel is set up...

[djsisson]

whether a resources uses the tunnel or not, depends on what you set for the dns record, if you do not want something to use the tunnel, then don't point it to the argo tunnel proxy, and just create an A record or CNAME the same as you normally would