I can’t access it remotely on my phone outside of my house or in the house when I don’t connect to wifi. It’s been like this for me since yesterday. I think it happened after a version update for the addon but not sure.
About 10/11 months passed when everything was fine and suddenly it stopped working.
I tried to reset the system or the proxmox, but it didn’t help.
I also restarted the addon, reinstalled it, and reconfigure the tunnel.
What can I do?
Here addon log:
-----------------------------------------------------------
Add-on: Cloudflared
Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
-----------------------------------------------------------
Add-on version: 4.2.1
You are running the latest version of this add-on.
System: Home Assistant OS 10.3 (amd64 / qemux86-64)
Home Assistant Core: 2023.7.2
Home Assistant Supervisor: 2023.07.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[09:05:20] INFO: Checking add-on config...
[09:05:20] INFO: Checking for existing certificate...
[09:05:20] INFO: Existing certificate found
[09:05:20] INFO: Checking for existing tunnel...
[09:05:20] INFO: Existing tunnel with ID d05258aa-****-****-****-********* found
[09:05:20] INFO: Checking if existing tunnel matches name given in config
[09:05:21] INFO: Existing Cloudflare Tunnel name matches config, proceeding with existing tunnel file
[09:05:21] INFO: Creating config file...
[09:05:22] INFO: Validating config file...
Validating rules from /tmp/config.json
OK
[09:05:22] INFO: Creating DNS entry wi***b.ml...
2023-07-21T06:05:23Z INF wi***b.ml is already configured to route to your tunnel tunnelID=d05258aa-****-****-****-********
[09:05:23] INFO: Finished setting up the Cloudflare Tunnel
[09:05:23] INFO: Connecting Cloudflare Tunnel...
2023-07-21T06:05:23Z INF Starting tunnel tunnelID=d05258aa-****-****-****-********
2023-07-21T06:05:23Z INF Version 2023.7.1
2023-07-21T06:05:23Z INF GOOS: linux, GOVersion: go1.19.6, GoArch: amd64
2023-07-21T06:05:23Z INF Settings: map[config:/tmp/config.json cred-file:/data/tunnel.json credentials-file:/data/tunnel.json loglevel:info metrics:0.0.0.0:36500 no-autoupdate:true origincert:/data/cert.pem]
2023-07-21T06:05:23Z INF Generated Connector ID: 760c6c3b-****-****-****-********
2023-07-21T06:05:23Z INF Initial protocol quic
2023-07-21T06:05:23Z INF ICMP proxy will use 172.30.33.4 as source for IPv4
2023-07-21T06:05:23Z INF ICMP proxy will use :: as source for IPv6
2023-07-21T06:05:23Z INF Starting metrics server on [::]:36500/metrics
2023-07-21T06:05:24Z INF Registered tunnel connection connIndex=0 connection=125a2db3-05df-4c43-9404-5b7cd5d3ae9b event=0 ip=198.41.192.27 location=LHR protocol=quic
2023-07-21T06:05:25Z INF Registered tunnel connection connIndex=1 connection=fb4c431b-fa3d-4889-9f81-27ff2a7c0a63 event=0 ip=198.41.200.53 location=BRU protocol=quic
2023-07-21T06:05:26Z INF Registered tunnel connection connIndex=2 connection=4d6a160b-0ea4-4cce-bf2f-9dc91fb665a3 event=0 ip=198.41.192.167 location=FRA protocol=quic
2023-07-21T06:05:26Z WRN Failed to serve quic connection error="already connected to this server, trying another address" connIndex=3 event=0 ip=198.41.200.43
2023-07-21T06:05:26Z WRN Unable to establish connection. error="already connected to this server, trying another address" connIndex=3 event=0 ip=198.41.200.43
2023-07-21T06:05:26Z INF Retrying connection in up to 2s connIndex=3 event=0 ip=198.41.200.43
2023-07-21T06:05:28Z WRN Connection terminated error="already connected to this server, trying another address" connIndex=3
2023-07-21T06:05:48Z INF Registered tunnel connection connIndex=3 connection=3c2422e9-cd0a-41d7-9685-e14a875c3906 event=0 ip=198.41.200.113 location=BRU protocol=quic
If you still interested, in my case, the problem was with .ml domain from dot.tk site. Recently they kinda “banned” or just disable using it.
I’ve bought domain on OVH which was very cheap in annual pay and everything works flawlessly now.
I removed my .ml domain and setup my alternative .cf domain from freenom and now it works.
Ps
I did have to setup my paypal billing on cloudflare, to be able to access zero trust page (i did not have to do that last year when i made my original setup)
I did have to setup my paypal billing on cloudflare, to be able to access zero trust page (i did not have to do that last year when i made my original setup)
If you don’t feel comfortable adding your primary cc, you can get a prepaid cc and add that. I’ve done just that and it works.
I have succesfully configured this addon on my HA instance and it’s working fine for HA acces.
I now want to expose other service on a subdomain. This is also working upon a certain height.
I configured it in additional hosts with a service on my local network on port 3400 for example.
When I access the subdomain, I am redirect to another port on my server (port 2000 for example) to login first. But since port 2000 is not configured in additional hosts, this is giving a timeout. How do I solve this issue?
So basically: my subdomain (eg. testapp.mydomain.com) should be able to handle different ports (3400 & 2000), but it’s only configured in HA with 1 port.
Hi everyone, I ask for your help with a problem that has been affecting me for a few days with Cloudflared.
I have continuous disconnections, after a few minutes from starting the addon, I have a .com domain purchased directly from Cloudflare and the tunnel automatically configured by Cloudflared.
It always worked fine, but now it doesn’t anymore.
I hope someone can help me. Thank you
I am currently testing to use HomeAssistant as an application in Cloudflare Teams behind an additional layer of Authentication. So far, Google is not working, but GitHub is. I am investigating how this is working out and expanding the documentation accordingly.
Are there any news about this? I don’t use Google Assistant and want to add an additional layer of security to access my Home Assistant. Is this possible with the current version?
Yes. It works, but you have to reinstall the home assistant server in the android app in order to pass the authentication. Each time the session expires (I have 1 month configured in cloudflare) you have to remove the server from the app and add it again in order to reauthenticate.
You can use warp with zero trust and bypass access, but it is tricky cause sometimes it disconnects when you move in the city.
They are working in the possibility of using a bypass cloudflare token as a header in the android app, but still in development.