CLOSED - Http integration in configuration.yaml prevents HA UI to start

gerardsamara · January 14, 2021, 1:33pm

HI ,

I am running HA Supervised in a debian VM over Proxmox.
The Duckdns and Letsencrypt have been integrated successfully as per their logs.
The remote access from HA android app fails with ERR_SSL_PROTOCOL

A possible raison is that the http configuration mentionned in the Duckdnd addon documentation for Home Assistant Core is not setup because tis prevents HA to reboot.
As per the log , HA is running but sounds like the UI is not up.

Please any expert may look at this issue ?

Thank you

http part of Duckdns addon documentation
----------------------------------------

 Additionally, you'll need to configure the Home Assistant Core to pick up the SSL certificates. This is done by setting the following configuration for the [HTTP](https://www.home-assistant.io/integrations/http/) integration configuration in your `configuration.yaml` :

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

I have taken the Debian VM Syslog regarding the HA failing to stat when http configuration is in the configuration.yaml

Jan 14 13:15:26 Debian10-KVM dcc8141b0962[390]: NOCHANGE#033[0m
Jan 14 13:17:01 Debian10-KVM CRON[6610]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 14 13:19:46 Debian10-KVM 43242e55b673[390]: 
Jan 14 13:20:28 Debian10-KVM dcc8141b0962[390]: [13:20:28] INFO: #033[32mOK
Jan 14 13:20:28 Debian10-KVM dcc8141b0962[390]: 176.167.80.172
Jan 14 13:20:28 Debian10-KVM dcc8141b0962[390]: 
Jan 14 13:20:28 Debian10-KVM dcc8141b0962[390]: NOCHANGE#033[0m
Jan 14 13:21:20 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:21:20 INFO (SyncWorker_1) [supervisor.docker.interface] Restarting homeassistant/qemux86-64-homeassistant#033[0m
Jan 14 13:21:20 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:21:20 INFO (SyncWorker_1) [supervisor.docker.interface] Restarting homeassistant/qemux86-64-homeassistant#033[0m
Jan 14 13:21:20 Debian10-KVM f943196c16db[390]: [cont-finish.d] executing container finish scripts...
Jan 14 13:21:20 Debian10-KVM f943196c16db[390]: [cont-finish.d] done.
Jan 14 13:21:20 Debian10-KVM f943196c16db[390]: [s6-finish] waiting for services.
Jan 14 13:21:21 Debian10-KVM f943196c16db[390]: Client error on /homeassistant/restart request Server disconnected
Jan 14 13:21:21 Debian10-KVM 00e60774e4ef[390]: 1610626881: Socket error on client 3py2FV4Q1PzIv8v5VPogii, disconnecting.
Jan 14 13:21:21 Debian10-KVM f943196c16db[390]: s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
Jan 14 13:21:21 Debian10-KVM f943196c16db[390]: [s6-finish] sending all processes the TERM signal.
Jan 14 13:21:25 Debian10-KVM f943196c16db[390]: [s6-finish] sending all processes the KILL signal and exiting.
Jan 14 13:21:25 Debian10-KVM dockerd[390]: time="2021-01-14T13:21:25.232680167+01:00" level=info msg="ignoring event" container=f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jan 14 13:21:25 Debian10-KVM containerd[314]: time="2021-01-14T13:21:25.234388468+01:00" level=info msg="shim disconnected" id=f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e
Jan 14 13:21:25 Debian10-KVM containerd[314]: time="2021-01-14T13:21:25.360705205+01:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e pid=6711
Jan 14 13:21:25 Debian10-KVM systemd[1]: run-docker-runtime\x2drunc-moby-f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e-runc.ehwqAO.mount: Succeeded.
Jan 14 13:21:25 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:21:25 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready#033[0m
Jan 14 13:21:25 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:21:25 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready#033[0m
Jan 14 13:21:25 Debian10-KVM f943196c16db[390]: [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
Jan 14 13:21:25 Debian10-KVM f943196c16db[390]: [s6-init] ensuring user provided files have correct perms...exited 0.
Jan 14 13:21:25 Debian10-KVM f943196c16db[390]: [fix-attrs.d] applying ownership & permissions fixes...
Jan 14 13:21:25 Debian10-KVM f943196c16db[390]: [fix-attrs.d] done.
Jan 14 13:21:25 Debian10-KVM f943196c16db[390]: [cont-init.d] executing container initialization scripts...
Jan 14 13:21:25 Debian10-KVM f943196c16db[390]: [cont-init.d] udev.sh: executing... 
Jan 14 13:21:25 Debian10-KVM f943196c16db[390]: [12:21:25] INFO: #033[32mUpdate udev information#033[0m
Jan 14 13:21:26 Debian10-KVM systemd-udevd[6971]: Using default interface naming scheme 'v240'.
Jan 14 13:21:26 Debian10-KVM systemd-udevd[6949]: Using default interface naming scheme 'v240'.
Jan 14 13:21:26 Debian10-KVM systemd-udevd[6945]: Using default interface naming scheme 'v240'.
Jan 14 13:21:27 Debian10-KVM f943196c16db[390]: [cont-init.d] udev.sh: exited 0.
Jan 14 13:21:27 Debian10-KVM f943196c16db[390]: [cont-init.d] done.
Jan 14 13:21:27 Debian10-KVM f943196c16db[390]: [services.d] starting services
Jan 14 13:21:27 Debian10-KVM f943196c16db[390]: [services.d] done.
Jan 14 13:21:32 Debian10-KVM 00e60774e4ef[390]: 1610626892: New connection from 172.30.32.1 on port 1883.
Jan 14 13:21:32 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:21:32 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'xxxx_mosquitto'#033[0m
Jan 14 13:21:32 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:21:32 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'xxxx_mosquitto'#033[0m
Jan 14 13:21:33 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:21:33 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache#033[0m
Jan 14 13:21:33 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:21:33 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache#033[0m
Jan 14 13:21:33 Debian10-KVM 00e60774e4ef[390]: [INFO] found xxxxxx_mosquitto on Home Assistant
Jan 14 13:21:33 Debian10-KVM 00e60774e4ef[390]: 1610626893: New client connected from 172.30.32.1 as 5VTIMTBnnyn73YiWA367IJ (p2, c1, k60, u'xxxxxxx_mosquitto').
Jan 14 13:21:33 Debian10-KVM f943196c16db[390]: #033[32m2021-01-14 12:21:33 INFO (Thread-5) [homeassistant.components.mqtt] Connected to MQTT server core-mosquitto:1883 (0)#033[0m
Jan 14 13:21:34 Debian10-KVM f943196c16db[390]: #033[36m2021-01-14 12:21:34 DEBUG (MainThread) [homeassistant.components.onvif] Setting up the ONVIF device management service#033[0m
Jan 14 13:21:34 Debian10-KVM f943196c16db[390]: #033[36m2021-01-14 12:21:34 DEBUG (MainThread) [homeassistant.components.onvif] Retrieving current device date/time#033[0m
Jan 14 13:21:34 Debian10-KVM f943196c16db[390]: #033[36m2021-01-14 12:21:34 DEBUG (MainThread) [homeassistant.components.onvif] Device date/time: 2015-01-23 10:51:13+00:00 | System date/time: 2021-01-14 12:21:34.619427+00:00#033[0m
Jan 14 13:21:37 Debian10-KVM f943196c16db[390]: #033[31m2021-01-14 12:21:37 ERROR (MainThread) [homeassistant.components.camera] The onvif platform for the camera integration does not support platform setup. Please remove it from your config.#033[0m
Jan 14 13:21:38 Debian10-KVM f943196c16db[390]: #033[31m2021-01-14 12:21:38 ERROR (MainThread) [homeassistant.components.synology_dsm.config_flow] {'api': 'SYNO.API.Auth', 'code': 400, 'reason': 'Invalid credentials', 'details': 'Invalid password or not admin account: secrets ds418_username'}#033[0m
Jan 14 13:21:45 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:21:45 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance#033[0m
Jan 14 13:21:45 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:21:45 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance#033[0m
Jan 14 13:22:00 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:22:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize#033[0m
Jan 14 13:22:00 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:22:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize#033[0m
Jan 14 13:22:01 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:22:01 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode#033[0m
Jan 14 13:22:01 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:22:01 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode#033[0m
Jan 14 13:22:01 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:22:01 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running#033[0m
Jan 14 13:22:01 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:22:01 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running#033[0m
Jan 14 13:23:49 Debian10-KVM systemd[1]: Created slice User Slice of UID 1000.
Jan 14 13:23:49 Debian10-KVM systemd[1]: Starting User Runtime Directory /run/user/1000...
Jan 14 13:23:49 Debian10-KVM systemd[1]: Started User Runtime Directory /run/user/1000.
Jan 14 13:23:49 Debian10-KVM systemd[1]: Starting User Manager for UID 1000...
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Reached target Timers.
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Reached target Paths.
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Listening on GnuPG network certificate management daemon.
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Reached target Sockets.
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Reached target Basic System.
Jan 14 13:23:49 Debian10-KVM systemd[1]: Started User Manager for UID 1000.
Jan 14 13:23:49 Debian10-KVM systemd[1]: Started Session 2 of user gerardsamara.
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Reached target Default.
Jan 14 13:23:49 Debian10-KVM systemd[7279]: Startup finished in 88ms.
Jan 14 13:23:54 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:23:54 INFO (SyncWorker_0) [supervisor.docker.interface] Restarting homeassistant/qemux86-64-homeassistant#033[0m
Jan 14 13:23:54 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:23:54 INFO (SyncWorker_0) [supervisor.docker.interface] Restarting homeassistant/qemux86-64-homeassistant#033[0m
Jan 14 13:23:54 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:23:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str#033[0m
Jan 14 13:23:54 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:23:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str#033[0m
Jan 14 13:23:54 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:23:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed#033[0m
Jan 14 13:23:54 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:23:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed#033[0m
Jan 14 13:23:54 Debian10-KVM f943196c16db[390]: [cont-finish.d] executing container finish scripts...
Jan 14 13:23:54 Debian10-KVM f943196c16db[390]: [cont-finish.d] done.
Jan 14 13:23:54 Debian10-KVM f943196c16db[390]: [s6-finish] waiting for services.
Jan 14 13:23:55 Debian10-KVM f943196c16db[390]: Client error on /homeassistant/restart request Server disconnected
Jan 14 13:23:56 Debian10-KVM 00e60774e4ef[390]: 1610627036: Socket error on client 5VTIMTBnnyn73YiWA367IJ, disconnecting.
Jan 14 13:23:56 Debian10-KVM f943196c16db[390]: s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
Jan 14 13:23:56 Debian10-KVM f943196c16db[390]: [s6-finish] sending all processes the TERM signal.
Jan 14 13:23:59 Debian10-KVM f943196c16db[390]: [s6-finish] sending all processes the KILL signal and exiting.
Jan 14 13:24:00 Debian10-KVM dockerd[390]: time="2021-01-14T13:24:00.087717181+01:00" level=info msg="ignoring event" container=f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jan 14 13:24:00 Debian10-KVM containerd[314]: time="2021-01-14T13:24:00.089776246+01:00" level=info msg="shim disconnected" id=f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e
Jan 14 13:24:00 Debian10-KVM containerd[314]: time="2021-01-14T13:24:00.205773869+01:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e pid=7362
Jan 14 13:24:00 Debian10-KVM systemd[7279]: run-docker-runtime\x2drunc-moby-f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e-runc.LAbnj7.mount: Succeeded.
Jan 14 13:24:00 Debian10-KVM systemd[1]: run-docker-runtime\x2drunc-moby-f943196c16dbe8ed9359ef69a6c5dd86dd6342b39b2995bc8d68b7077a9ce43e-runc.LAbnj7.mount: Succeeded.
Jan 14 13:24:00 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:24:00 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready#033[0m
Jan 14 13:24:00 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:24:00 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready#033[0m
Jan 14 13:24:00 Debian10-KVM f943196c16db[390]: [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
Jan 14 13:24:00 Debian10-KVM f943196c16db[390]: [s6-init] ensuring user provided files have correct perms...exited 0.
Jan 14 13:24:00 Debian10-KVM f943196c16db[390]: [fix-attrs.d] applying ownership & permissions fixes...
Jan 14 13:24:00 Debian10-KVM f943196c16db[390]: [fix-attrs.d] done.
Jan 14 13:24:00 Debian10-KVM f943196c16db[390]: [cont-init.d] executing container initialization scripts...
Jan 14 13:24:00 Debian10-KVM f943196c16db[390]: [cont-init.d] udev.sh: executing... 
Jan 14 13:24:00 Debian10-KVM f943196c16db[390]: [12:24:00] INFO: #033[32mUpdate udev information#033[0m
Jan 14 13:24:00 Debian10-KVM systemd-udevd[7609]: Using default interface naming scheme 'v240'.
Jan 14 13:24:01 Debian10-KVM systemd-udevd[7608]: Using default interface naming scheme 'v240'.
Jan 14 13:24:01 Debian10-KVM systemd-udevd[7601]: Using default interface naming scheme 'v240'.
Jan 14 13:24:02 Debian10-KVM f943196c16db[390]: [cont-init.d] udev.sh: exited 0.
Jan 14 13:24:02 Debian10-KVM f943196c16db[390]: [cont-init.d] done.
Jan 14 13:24:02 Debian10-KVM f943196c16db[390]: [services.d] starting services
Jan 14 13:24:02 Debian10-KVM f943196c16db[390]: [services.d] done.
Jan 14 13:24:07 Debian10-KVM 00e60774e4ef[390]: 1610627047: New connection from 172.30.32.1 on port 1883.
Jan 14 13:24:07 Debian10-KVM 00e60774e4ef[390]: 1610627047: New client connected from 172.30.32.1 as 6Z65O69ySwKDDIeHbcqGep (p2, c1, k60, u'xxxxx_mosquitto').
Jan 14 13:24:07 Debian10-KVM f943196c16db[390]: #033[32m2021-01-14 12:24:07 INFO (Thread-5) [homeassistant.components.mqtt] Connected to MQTT server core-mosquitto:1883 (0)#033[0m
Jan 14 13:24:09 Debian10-KVM f943196c16db[390]: #033[36m2021-01-14 12:24:09 DEBUG (MainThread) [homeassistant.components.onvif] Setting up the ONVIF device management service#033[0m
Jan 14 13:24:09 Debian10-KVM f943196c16db[390]: #033[36m2021-01-14 12:24:09 DEBUG (MainThread) [homeassistant.components.onvif] Retrieving current device date/time#033[0m
Jan 14 13:24:09 Debian10-KVM f943196c16db[390]: #033[36m2021-01-14 12:24:09 DEBUG (MainThread) [homeassistant.components.onvif] Device date/time: 2015-01-23 10:53:48+00:00 | System date/time: 2021-01-14 12:24:09.305595+00:00#033[0m
Jan 14 13:24:11 Debian10-KVM f943196c16db[390]: #033[31m2021-01-14 12:24:11 ERROR (MainThread) [homeassistant.components.camera] The onvif platform for the camera integration does not support platform setup. Please remove it from your config.#033[0m
Jan 14 13:24:13 Debian10-KVM f943196c16db[390]: #033[31m2021-01-14 12:24:13 ERROR (MainThread) [homeassistant.components.synology_dsm.config_flow] {'api': 'SYNO.API.Auth', 'code': 400, 'reason': 'Invalid credentials', 'details': 'Invalid password or not admin account: secrets ds418_username'}#033[0m
Jan 14 13:24:19 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:24:19 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize#033[0m
Jan 14 13:24:19 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:24:19 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize#033[0m
Jan 14 13:24:19 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:24:19 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode#033[0m
Jan 14 13:24:19 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:24:19 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode#033[0m
Jan 14 13:24:19 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:24:19 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running#033[0m
Jan 14 13:24:19 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:24:19 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running#033[0m
Jan 14 13:24:20 Debian10-KVM 43242e55b673[390]: #033[32m21-01-14 12:24:20 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance#033[0m
Jan 14 13:24:20 Debian10-KVM hassio-supervisor[906]: #033[32m21-01-14 12:24:20 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance#033[0m
Jan 14 13:24:47 Debian10-KVM 43242e55b673[390]: 
Jan 14 13:25:02 Debian10-KVM 00e60774e4ef[390]: 1610627102: Saving in-memory database to /data/mosquitto.db.
Jan 14 13:25:29 Debian10-KVM dcc8141b0962[390]: [13:25:29] INFO: #033[32mOK
Jan 14 13:25:29 Debian10-KVM dcc8141b0962[390]: 176.167.80.172
Jan 14 13:25:29 Debian10-KVM dcc8141b0962[390]: 
Jan 14 13:25:29 Debian10-KVM dcc8141b0962[390]: NOCHANGE#033[0m
Jan 14 13:29:47 Debian10-KVM 43242e55b673[390]: 
Jan 14 13:30:30 Debian10-KVM dcc8141b0962[390]: [13:30:30] INFO: #033[32mOK
Jan 14 13:30:30 Debian10-KVM dcc8141b0962[390]: 176.167.80.172
Jan 14 13:30:30 Debian10-KVM dcc8141b0962[390]: 
Jan 14 13:30:30 Debian10-KVM dcc8141b0962[390]: NOCHANGE#033[0m
Jan 14 13:30:43 Debian10-KVM systemd[1]: session-2.scope: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[1]: Stopping User Manager for UID 1000...
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Stopped target Default.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Stopped target Basic System.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Stopped target Sockets.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: gpg-agent.socket: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Closed GnuPG cryptographic agent and passphrase cache.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: gpg-agent-extra.socket: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jan 14 13:30:53 Debian10-KVM systemd[7279]: gpg-agent-ssh.socket: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Stopped target Timers.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: dirmngr.socket: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Closed GnuPG network certificate management daemon.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: gpg-agent-browser.socket: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Stopped target Paths.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Reached target Shutdown.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: systemd-exit.service: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Started Exit the Session.
Jan 14 13:30:53 Debian10-KVM systemd[7279]: Reached target Exit the Session.
Jan 14 13:30:53 Debian10-KVM systemd[1]: [email protected]: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[1]: Stopped User Manager for UID 1000.
Jan 14 13:30:53 Debian10-KVM systemd[1]: Stopping User Runtime Directory /run/user/1000...
Jan 14 13:30:53 Debian10-KVM systemd[1]: run-user-1000.mount: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[1]: [email protected]: Succeeded.
Jan 14 13:30:53 Debian10-KVM systemd[1]: Stopped User Runtime Directory /run/user/1000.
Jan 14 13:30:53 Debian10-KVM systemd[1]: Removed slice User Slice of UID 1000.
Jan 14 13:31:00 Debian10-KVM systemd[1]: Created slice User Slice of UID 1000.
Jan 14 13:31:00 Debian10-KVM systemd[1]: Starting User Runtime Directory /run/user/1000...
Jan 14 13:31:00 Debian10-KVM systemd[1]: Started User Runtime Directory /run/user/1000.
Jan 14 13:31:00 Debian10-KVM systemd[1]: Starting User Manager for UID 1000...
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Reached target Paths.
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Reached target Timers.
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Listening on GnuPG network certificate management daemon.
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Reached target Sockets.
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Reached target Basic System.
Jan 14 13:31:00 Debian10-KVM systemd[1]: Started User Manager for UID 1000.
Jan 14 13:31:00 Debian10-KVM systemd[1]: Started Session 4 of user gerardsamara.
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Reached target Default.
Jan 14 13:31:00 Debian10-KVM systemd[7888]: Startup finished in 63ms.
Jan 14 13:34:47 Debian10-KVM 43242e55b673[390]: 
Jan 14 13:35:31 Debian10-KVM dcc8141b0962[390]: [13:35:31] INFO: #033[32mOK
Jan 14 13:35:31 Debian10-KVM dcc8141b0962[390]: 176.167.80.172
Jan 14 13:35:31 Debian10-KVM dcc8141b0962[390]: 
Jan 14 13:35:31 Debian10-KVM dcc8141b0962[390]: NOCHANGE#033[0m

As per the log , HA is running but sounds like the UI is not up.
Please any expert may look at this issue ?

Thank you

anon43302295 · January 14, 2021, 1:45pm

Like everyone else who makes this mistake, you have chosen to ignore the instructions that having set up SSL you now cannot login with http and must use https.

If you can tell me why you made this mistake and it’s a documentation issue somewhere I’ll try and correct it, but we get at least one person a month here with the same ‘problem’ and there doesn’t seem to be any obvious reason why.

gerardsamara · January 14, 2021, 3:24pm

@anon43302295 ,

I appreciate your constructive answer because this is not normal there are so many posts concerning SSL setup.

For this particular issue ( HA start fails if http setup in configuration.yaml with Duckdns+Letsencrypt addons installed) , i am following the Duckdns addon documentation

github.com

home-assistant/addons/blob/aa4f2d7f0f447c57b4cd4ebda24ebc738a3d3176/duckdns/DOCS.md

# Home Assistant Add-on: DuckDNS

## Installation

Follow these steps to get the add-on installed on your system:

1. Navigate in your Home Assistant frontend to **Supervisor** -> **Add-on Store**.
2. Find the "DuckDNS" add-on and click it.
3. Click on the "INSTALL" button.

## How to use

1. Visit [DuckDNS.org](https://www.duckdns.org/) and create an account by logging in through any of the available account services (Google, Github, Twitter, Persona, Reddit).
2. In the `Domains` section, type the name of the subdomain you wish to register and click `add domain`.
3. If registration was a success, the subdomain is listed in the `Domains` section along with `current ip` being the public IP address of the device you are currently using to access `duckdns.org`. The IP address will be updated by the DuckDNS add-on.
4. In the DuckDNS add-on configuration, perform the following:
    - Copy the DuckDNS token (listed at the top of the page where account details are displayed) from `duckdns.org` and paste into the `token` option.
    - Update the `domains` option with the full domain name you registered. E.g., `my-domain.duckdns.org`.

## Configuration

This file has been truncated. show original

anon43302295 · January 14, 2021, 3:39pm

Yes, but where did you get the idea to use that addon to achieve your goal of encrypted communication with your homeassistant? Encrypted communication requires the use of https.

The instructions you pasted are for configuring the addon, which are correct. They presume that you know why you’re doing it, otherwise all instructions for everything would be a thousand lines long.

gerardsamara · January 14, 2021, 5:17pm

Yes we have the opportunity to follow the existing documentation to setup remote access with https , this is anyway a good exercice.

What the documentation says about the use of Duckns and Letencrypt addon and https

1) From “Remote access page”

https://www.home-assistant.io/docs/configuration/remote/

propose Duckdns for a free dynnamic DDNS
then propose Letsencrypt https:

1a) https://www.home-assistant.io/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/

Or

1b) Installing TLS/SSL using Let's Encrypt

2) from “Effortless encryption with Let’s Encrypt and DuckDNS” page

automatic generation and updating of Let’s Encrypt certificates for your DuckDNS domain
Use of https = OK
configuration of http in configuration.yaml = The problem described in this topic
Http challenge is setup in my system

For non hassio system https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt

3) from “HASS, DuckDNS and Let’s Encrypt” blog page

NOT DONE

Conclusion :In my HA supervised system , i have installed as per the documentation above :

Duckdns addon : point1a)
Letsencrypt addon + http challenge: point2)

But I stopped here ( https local+remote OK) , I haved not done point3) so my questions :

Let’s review and confirm that the documentation above is sufficient and correct for point 1) , 2), 3) , for the benefit of every new user ( and me for Supervised install)

Thank you

anon43302295 · January 14, 2021, 5:42pm

I actually wrote the original guide of 1b, so I know it’s in there, although I notice that it’s since been edited to suggest it’s not relevant to complete / supervised installations, which whilst it is technically correct it still contains a lot of information that is useful to know even if you can simplify it with an addon these days

gerardsamara · January 14, 2021, 8:37pm

I had a quick look before using it …
I see that there is no addon required at all .
I will let you know it goes in the guide topic

gerardsamara · January 23, 2021, 6:03pm

I tested again after my head rested during several days and it works with http integration enabled in configuration.yaml file.

I think I made mistakes somewhere when testing with http and not with https in local network as it should be ( https://192.168.1.x:8123 works )