Closed DmytroKorniienko closed 1 year ago
Strange, I've checked what I've changed (https://github.com/lmagyar/homeassistant-addon-tailscale/commit/45419363f41befb1683e3f7a2a4bbd8c5a91ab3e), and based on your log, my script executes the same steps as the previous version, so my guess is that the problem is with the binaries (tailscale or base-image).
I see only one strange unrelated thing in the logs: https://network.ts.net
So please:
what is the output of this command, executed in the add-on's cli: /opt/tailscale status --self=true --peers=false --json | jq "{HostName: .Self.HostName, DNSName: .Self.DNSName, MagicDNSSuffix: .MagicDNSSuffix, CertDomains: .CertDomains}"
it should be something like this:
{
"HostName": "dev-homeassistant",
"DNSName": "dev-homeassistant-beta.tail6158.ts.net.",
"MagicDNSSuffix": "tail6158.ts.net",
"CertDomains": [
"dev-homeassistant-beta.tail6158.ts.net"
]
}
you can get into the add-on's container with something like docker exec -it addon_09716aab_tailscale /bin/bash
I've created a new beta version v0.11.1.12-rc02 of my fork, with the latest binaries (base-image v14.0.7), I don't think it will solve the CPU issue, but this is a first step to test, so please:
https://github.com/lmagyar/homeassistant-addon-tailscale-beta
tailscale2
interface, just to not completely mess up networking if accidentally started parallel with the non-beta versionIf the CPU issue doesn't solved, I will create a downgraded beta release (downgraded tailscale, then downgraded base-image versions, but with my latest script version), maybe we will see something. Eg. there is an issue with taildrop and network performance: https://github.com/hassio-addons/addon-tailscale/issues/168
I see only one strange unrelated thing in the logs: https://network.ts.net
I replaced some personal info for security reason. Thank you, I will test beta version and give you feedback soon.
Ah, OK. :) So the link that is shown in the log, as "Your Home Assistant instance is publicly available on the internet at https://network.ts.net" in reality is working? I was scared that something is really different on a Proxmox/HAOS installation.
Both version works and accessible from external, but beta without CPU overload:
...
2023/08/03 01:53:47 serve: creating a new proxy handler for http://127.0.0.1:8123
[01:53:48] INFO: Tailscale Funnel is enabled:
[01:53:48] INFO: Your Home Assistant instance is publicly available on the internet at
[01:53:48] INFO: https://host.nw.ts.net
s6-rc: info: service funnel successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023/08/03 01:53:48 Hostinfo.WireIngress changed to true
If any additional testing required please let me know.
Wow! This means the problem is with the v14.0.6 base image.
I've released v0.11.1.12 NON-beta version.
Please report back, if the new v0.11.1.12 NON-beta version works without extra CPU load.
I've released v0.11.1.12 NON-beta version.
I updated to v0.11.1.12 and nothing changes for me. Extra load was found again, so then I totally uninstalled main version and reinstalled it again. Add-on asked for autorization by url and then all extra CPU loads was fixed. So my best gues - this is not related with a binary or/and add-on and something at the cloud side. Thank you for your help.
Computers are 'a complete mystery'... :) Closing this issue for now, reopen it if you think it is relevant again.
After upgrede to 0.11.1.11 cpu utilization continuatelly height. Reverting to previous version solves issue, reinstall or/and reboot - not. Environment - Proxmox, HAOS. Addon configuration: exit node, funnel - all works, exept CPU issue. Nothing weird in the logs.
What I missed? Will be appreciated for your help. THanks for the great job!