Cloudflare Tunnel Rule not working without subdomain
C
Carlos Garrido Marín
I've been testing the native integration with Cloudflare tunnels in the new version 1.55.0, but there is a small bug.
Apparently, when you create a new "Cloudflare Tunnel Rule" in a domain you must always enter a subdomain, otherwise the response gives a 400 error.
Looking at the EasyPanel logs, it seems that the request made to Cloudflare is always sent "<subdomain>.<domain>", so if the subdomain is empty ".<domain>" is sent and the Cloudflare API responds with a 400.
Otherwise the integration works wonderfully well.
A
Andrei Canta
What if you put * for the subdomain?
C
Carlos Garrido Marín
Andrei Canta Thanks for your quick response.
Just * or @ doesn't work. Cloudflare even displays a warning that no changes will be made to the DNS records.
Attached screenshot
M
Mark Topper
Carlos Garrido Marín You can leave subdomain empty in Cloudflare.
C
Carlos Garrido Marín
Mark Topper If you manually change the rule in Cloudflare Tunnel when you save any changes to the tunnel rules in Easypanel, the changes you made manually are deleted and only the values in Easypanel prevail.
So when you update any Cloudflare Tunnel Rule, Easypanel deletes all the public hostname rules from the Cloudflare Tunnel and recreates them.