HADashboard (dash_password) directive causing "500 Internal Server Error"

Hi, my configuration is
HA Virtual Env on Google VM instance (ssl)
letsencrypt
duckdns
appdaemon on port 3030 (ssl)

every thing works as expected but it is impossible to
password protect the dashboard.
----------------my config file-----------
AppDaemon:
cert_verify: True
disable_apps: 0
logfile: STDOUT
errorfile: STDERR
threads: 10
api_port: 3030
api_key: !secret api_key
HASS:
ha_key: !secret home_assistant_key
ha_url: https://[redacted].duckdns.org
HADashboard:
dash_url: https://[redacted].duckdns.org:3030
dash_password: !secret dash_password
dash_dir: /home/homeassistant/conf/dashboards
dash_ssl_certificate: /etc/letsencrypt/live/[redacted].duckdns.org/fullchain.pem
dash_ssl_key: /etc/letsencrypt/live/[redacted].duckdns.org/privkey.pem
----------------my config file-----------

when I set value in <dash_password> I get
--------------------------------------------------error---------------
Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.5/dist-packages/aiohttp/web_protocol.py”, line 422, in start
resp = yield from self._request_handler(request)
File “/usr/local/lib/python3.5/dist-packages/aiohttp/web.py”, line 312, in _handle
[middleware for middleware in app.middlewares
AssertionError: Handler <function secure..wrapper at 0x7fb8432fb400> should return response instance, got <class ‘dict’> [middlewares []]
-------------------------------error------------------------------------------------

any input will be appreciated
THANKS FOR THE GREATE WORK

1 Like

its a known bug.
its on the todo list from Andrew.

untill its mentioned in a new release passwords wont work.

Thanks I’ll look for alternatives till then.
You saved me a lot of trial and error.

1 Like