You removed the tunnel from HA, but in CloudFlared it still exists. Just in HA configuration select “show unused entries” and add different tunnel name. Like HA_new or whatever, only that is different name.
I saw update 4.1.1 is available, and that’s for 2023.4 compatibility.
Will it cause issues if I am still using 2023.3.6?
Cloudflared Add-on release v4.1.1 contains the cloudflared binary (which sets up the tunnel to Cloudflare) with version v2023.4.0.
You can consider this independent of the Home Assistant release. So it will work if you use HA with version 2023.3.6.
Hello all!
I have just moved form DuckDNS to this amazing Cloudflare Add-On! love it!
I have one challenge which I hope someone can help me here: I am trying to add an additional host to the configuration in order to access form “outside” a Ubuntu Machine in the same network via remote desktop.
what I have done so far:
- I have added the additional host in the configuration
additional_hosts:
- hostname: ubuntu.myDomain.com
service: http://192.168.1.50
- I have verified that the tunnel has the additional host in Cloudflare
- I have verified that Cloudflare has added an additional DNS entry (CNAM for “ubuntu”)
- I have activated GNOME remote desktop in Ubuntu
- I have tested the connection to the Ubuntu machine locally (RDP to 192.168.1.50)
If I try to access the same RDP from ubuntu.myDomain.com, nothing happen…
I know this is not really a Home assistant question, but for sure linked to the usage of the add-on…
anybody can help me?
Try googling cloudflare zero trust and rdp.
I looked a while back and it was doable but not like this. You need the warp client or the tunnel software on your endpoint
1 Like
@ finar I am looking to do similar and have found this guide. What I want to know if it is really free as stated in the guide. Also, there are extra steps require that this addon may be limited.
Hi. Creating the tunnel in the Cloudflare Zero Trust Dashboard is the right way to move forward, following our wiki.
There, you have many possibilities and I can confirm that everything you need to access your server via rdp as an example is free.
I would also recommend to configure the tunnel in the dashboard, as mentioned by @brenner-tobias.
If you want to stay with the configuration of the tunnel via the functionality in the add-on, have a look at this link. There you can find the supported ingress protocols (which are used in the additional_hosts).
For your example you could try
additional_hosts:
- hostname: ubuntu.myDomain.com
service: rdp://192.168.1.50:3389 # (change port accordingly)
A WARP configuration should not be necessary if the protocol is directly supported by the cloudflare ingress settings from the link above.
Agreed, thought there is one limitation as far as I know: you cannot simply access the RDP connection form your client but have to either run WARP or use cloudflared on the client as well. See detailed description and the two options here.
I myself have tried this multiple times, but since I do not want to use WARP or Cloudflared on the clients this is not feasible for me. So please let me know if you find / know another way 
Thanks for the clarification, I wasn’t aware of that. Admittedly, I’ve been away from Windows for a while. 
Thank you, I have now set the tunnel remotely in Cloudflare and it work perfectly… (I can access Home assistance and all seems to be ok…)
I have added one additional hosts in Zero Trust and I have noticed that in the DNS record, there is a warning on the certificate of the additional host…is it a problem and I need to fix it? or I can ignore it?
I have not run WARP nor used Cloudflare for RDP yet, therefore RDP is not working… I will report back once tried
thank you for now!
I was able to setup accessing my home network using this guide running Cloudflared tunnel on a different server. The guide states to have warp-routing enabled in a config.yml. Not sure if that is really needed.
tunnel: tunnel-home
credentials-file: /root/.cloudflared/YOUR-TUNNEL-UUID-HERE.json
warp-routing:
enabled: true
The next part is to create a route to your home network.
cloudflared tunnel route ip add 192.168.1.0/24 tunnel
How to create the ip route using the dashboard??
Update: I figured it out. You added your local network here.
Regarding the warning: This depends on the warning. If this is your root domain (e.g. example.com), this is probably regarding CNAME flattening, which is fine.
If this is another error, you have to check and see what is says. There is one thing that might be a problem: With the free versions, only SSL certificates for “simple” subdomains (e.g. “home.example.com”) are included. Multi-level-subdomains (e.g. my.home.example.com) do not work.
Looking for days to change my “unsecure” DuckDNS to a secure way to access my HomeAssist.
Now I read about the Rules from Cloudflare that we not allowed to stream on the connection.
I run 2 security camera’s (WebRTC-camera integration).
My question, how you guys handle it?
Can I stream the 2 camera’s another way?
have you ever gotten a solution for this? I am facing the same problem!
When I follow the official docs to setup google assistant and finally try to add it in the Google Home app, it finds the [test]Appname, but once selected it can not reach it.
Hi,
I have managed to configure the remote access on my domain, but I cannot make it work on a subdomain. I have:
- changed the External HA hostname to subdomain.
- removed entries from doamin DNS records
- restarted the plugin
- noticed there is a new CNAME entry for my subdomain in Cludflare DNS Records alnog with tunnel ID
Plugin logs look good - no errors.
When I open my subdomain I get " Not Found. The requested URL was not found on this server."
I have no idea how to fix it. Any help is appreciated.
Here are my logs
Easiest setup is through the zero trust dashboard. Add the subdomain to your tunnel there. Make sure you have no cnames in your dns records for it which are the same you are going to use with tunnels.
I had the same issue/error … tried to do it and re-doit 5 times, till I gave up…
then 2 days later, my google home speaker starter to work fine… curious I looked int o Google home app and magically, what was not recognized it is now there… I feel there have been some “dns refreshing” delay or some sort of it… anybody can share more light on this?
Waiting isn’t the solution up to now.
Since I can see the Home assistant in the Google Home app, except when select the [test]HomeAssistant it loads a page but quickly closes it and telling me it can’t connect.
Maybe it’s something in my network? Maybe it’s something in the HA config to allow cloudflare IP’s? I’m just not sure. The latter I doubt, since I can visit my HA when I am away through a browser or the app, so HA is not blocking any IP’s.
Hello!
Guys, sorry i asked here but i have no idea where to ask 
i asked everywhere
First of all i will show you my setup - LTE Internet with blocked ports, ddnat. I am using Cloudflare to get inside my network and it is working fine. Traccar web ui site is workign good, even gps tracking my phone by app on phone “traccar client” is working fine.
The problem is with GPS tracker - S20 Wanway tracker. Its comunicate by 5023 port which i created a tunnel but it is not working
This is part of log:
2023-04-22T12:59:58Z ERR error="Incoming request ended abruptly: context canceled" cfRay=7bbe0bd04eb5b14e-ATL event=1 ingressRule=4 originService=http://192.168.1.10:5023
2023-04-22T12:59:58Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=3 dest=https://traccardevices.domena.ga/ event=0 ip=198.41.192.27 type=http
2023-04-22T13:00:03Z ERR error="Incoming request ended abruptly: context canceled" cfRay=7bbe0c0c2edf452b-ATL event=1 ingressRule=4 originService=http://192.168.1.10:5023
2023-04-22T13:00:03Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=2 dest=http://traccardevices.domena.ga/ event=0 ip=198.41.200.113 type=http
2023-04-22T13:00:18Z ERR error="Incoming request ended abruptly: context canceled" cfRay=7bbe0c4cbce2addd-ATL event=1 ingressRule=4 originService=http://192.168.1.10:5023
2023-04-22T13:00:18Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=3 dest=https://traccardevices.domena.ga/ event=0 ip=198.41.192.27 type=http
2023-04-22T13:00:48Z ERR error="Incoming request ended abruptly: context canceled" cfRay=7bbe0d08b8c71f9d-ATL event=1 ingressRule=4 originService=http://192.168.1.10:5023
2023-04-22T13:00:48Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=1 dest=https://traccardevices.domena.ga/ event=0 ip=198.41.192.67 type=http
2023-04-22T13:03:00Z ERR error="Incoming request ended abruptly: context canceled" cfRay=7bbe0e090ea5e54a-DFW event=1 ingressRule=4 originService=http://192.168.1.10:5023
2023-04-22T13:03:00Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=3 dest=http://traccardevices.domena.ga/robots.txt event=0 ip=198.41.192.27 type=http
2023-04-22T13:03:00Z ERR error="Incoming request ended abruptly: context canceled" cfRay=7bbe0e0c888d3548-WAW event=1 ingressRule=4 originService=http://192.168.1.10:5023
2023-04-22T13:03:00Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=2 dest=http://traccardevices.domena.ga/ event=0 ip=198.41.200.113 type=http
Guys, so mby it will be easier if i wrote you down my goal.
I would like to use selfhosted traccar (by ha addon) with gps tracker who can comunicate through ddnat using cloudflare addon. Mby there is someone who did that.