addon-cloudflared: Domain is not a valid hostname
The problem
FATAL: 'xxxc is not a valid hostname. Please make sure not to include the protocol (e.g. ‘https://’) nor the port (e.g. ‘:8123’) and only use lowercase characters in the ‘external_hostname’. No change worked fine before the update.
What version of Cloudflared has the issue?
4.2.8
What was the last working version of Cloudflared?
4.2.7
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
external_hostname:
additional_hosts:
- hostname:
service: https://xxx.xxx.xxx.xxx:8123
tunnel_name: HomeAssist
Anything in the logs that might be useful for us?
-----------------------------------------------------------
Add-on: Cloudflared
Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
-----------------------------------------------------------
Add-on version: 4.2.8
You are running the latest version of this add-on.
System: Home Assistant OS 11.0 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.10.3
Home Assistant Supervisor: 2023.10.0
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[18:58:30] INFO: Checking add-on config...
[18:58:31] FATAL: ' is not a valid hostname. Please make sure not to include the protocol (e.g. 'https://') nor the port (e.g. ':8123') and only use lowercase characters in the 'external_hostname'.
s6-rc: warning: unable to start service init-cloudflared-config: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
Steps to reproduce the issue
No realy
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Reactions: 8
- Comments: 16 (3 by maintainers)
I have to be honest: no idea why this did not work. I checked with multiple domains, plus it was working for me in the Edge release with multiple subdomains, also no issues from other edge users for a day. Anyways, again sorry, will look into it in detail
Should be fixed in 4.2.9, please check and confirm
Same problem with domain …de
I have the same problem! I’m back to 4.2.7! FATAL: ‘Blub-Bla-Bla.com’ is not a valid hostname…