@brenner-tobias thank you for making this addon it’s pretty great and the documentation is excellent. I had Cloudflare already set up, just dropping in the addon and turning it on took 15 seconds and everything was working right out of the box.
Quick question, do I need to do something special to get subfolders to work?
i have all of the subfolders set up in NPM addon and they used to all work before I enabled the addon. Now I get 404 Not Found for all the subfolder locations.
Hello! The second day I can not figure out how to install remote access through this addon.
I got the domain name sample.tk
I registered on the cloudflare website.
Added a domain name to the site.
Set dns in freenom settings
Added repository https://github.com/brenner-tobias/ha-addon
Installed the addon in HA
Registered in its settings the address sample.tk
I run … but there is nothing in the logs.
Judging by the changed description at the beginning of this thread on the forum, now there is no link in the logs.
So what’s next? There is no external access. What are the next steps?
Thanks in advance for your help.
Judging by the changed description at the beginning of this thread on the forum, now there is no link in the logs.
Regarding the above I think you are referring to the strike through part. I think you misread that since its only referring to auto opening the link not being possible however it should still be in the logs.
So you start the add-on and there are no logs at all?
Hello
I have been using this addon from last month and so far it is great for my doubled NAT setup as my ISP do not support port forwarding
But from last 2 days I keep dropping the connection , sometimes it works and most of the time it does not .
This is my configuration file
Sorry the add-on stopped working. Looking at the logs, everything looks fine on the add-on / HA side (though you are running it in a “not supported environment”), so this feels like an issue with Cloudflared itself. We updated to 2022.9.0 three days ago, so maybe that is causing some problems. I suggest you try using the add-on version v2.0.15 and also raise this with Cloudflared.
Thanks for the suggestion , I tried the lower version on my server same thing is happening , it seems to me it is my ISP issue tried everything but nothing seemed to worked so far . After the cloudflared restart it works for few minutes after that start loosing connection.
In ipv6 I can forward port and access HA but not possible in ipv4 . I noticed that cloudflared start supporting ipv6 from version 2022.7.1 . I tested it in my server using --edge-ip-version 6 but not able to connect . I have not played it with much but I think i can get it working with ipv6
So finally I installed the tailscale on a vps then use my tailscale ip to tunnel via cloudflared. The problem I am facing is I can access my other hostnames but not able to access homeassistant. I am keep getting white screen on the webpage even though - service: http_404 is enabled . I have added my tailscale IP in trusted_proxies but it still not connecting . What could be the issue with it ?
Great add-on, thanks a lot for your work! I’ve been using cloudflared for some time running on a separate VM but this add-on allows me to streamline my systems and run it on HA.
I have a doubt about end-to-end encryption when using the tunnel which may seem stupid but reading through Cloudflare’s documentation I’m not sure if I got it right. I have a couple of applications, most served on https and one served on http. When connecting to the http one through the tunnel my browser dutifully informs me that it is not encrypted but according to the Cloudflare documentation one could infer that the traffic is encrypted end2end. I can and will secure said application but just out of curiosity wanted to confirm this point. Any clarification welcome.
can you please confirm or contradict that the add-on in not working with the newest Home Assistant?
I ask because I tried to make it work since several hours with no success.
Looking forward to read from you.
Thank you in forward!
Is anybody combining this with mTLS? Unless I’m misunderstanding, cloudflared enables the secure connection between Cloudflare and your local network (ie. Home Assistant) but it still allows anybody to access the tunnel using the public hostname, right?
Yes anyone can access the tunnel if they know your domain name. However in Cloudflare you can turn on Zero Trust which will put an authentication in place like GitHub or Google. User basically has to authenticate with a selected service and then you select who is allowed to get through
It really depends on the use-case that you want to solve here, so let me give you my thoughts:
My understanding is, that everything that you route into your Cloudflare Tunnel is always reachable via https from an end-users. Meaning: The connection from the client to the cloudflare reverse proxy is always https
The connection from the proxy to your service can be done via many different ways (see documentation here). So this means, you can route to a http site.
Now if you need to offer your site via http to the public using the Cloudflare proxy (which it looks like to me), I do not think this is working (plus I suggest to overthink why this is needed in the first place). If you only need to reach a service, that is internally available via http, that can be easily done.
Since this is a Cloudflare issue, I suggest to have a look at their documentation and raise the questions with them.
