Yes i had verified that before, SSL is true on mine. everything seemed correct. but the response failed.
I found the solution from the below, thanks
@ThatEricGuy In the old Configurator version, it was acceptable to leave allowed_networks empty and instead set and pass a value for sesame. That doesn’t seem to work with version 1.0. I found that I have to add my network to allowed_networks in order to get Configurator working again.
Are there any instructions from the developers that updated this? Maybe I’m missing something. Thank you all for the suggestions, maybe I need to read a little more on how this all works.
Daniel…THANK YOU…!!! Your da man…!
I have created an issue for the problems (and solutions) you guys have discovered: https://github.com/danielperna84/hass-configurator/issues/107
I will take care of those, although by using the workaround mentioned here everybody who upgrades and fixes the problem won’t need to have the bug fixed eventually. So I’ll probably end up just fixing the default value for new installations.
@ThatEricGuy
Thanks for discovering that. I’ll add an issue for that.
@mufidsyed
That looks like you have SSL disabled, but are accessing the configurator with https://....
@Chris8837
I am the developer. One of the problems is that while changing the way options are passend to the configurator I forgot that /ssl/ should always be prepended to the certificates path. The problem now is, that if I restore the old implementation, I would again break the configurator for those who now have fixed their issue by adding the ssl-part manually. Did you add the /ssl part so it now says /ssl/fullchain.pem (and the same for the key)? And as alos pointed out in this thread, there seems to be a problem when the list of allowed networks is empty.
Yes I added the SSL and I have copied it to this thread below. I don’t know what it means by allowed networks is empty. I have HA on 192.168.1.20. Is this what I put in there? What is the 16? Sorry I’m very new to all of this.
{
"username": "XXXXXXXX",
"password": "XXXXXXXX",
"ssl": true,
"certfile": "/ssl/fullchain.pem",
"keyfile": "/ssl/privkey.pem",
"allowed_networks": [
"192.168.0.0/16",
"172.30.0.0/16"
],
"banned_ips": [
"8.8.8.8"
],
"banlimit": 0,
"ignore_pattern": [
"__pycache__"
],
"dirsfirst": false,
"enforce_basepath": false,
"notify_service": "persistent_notification.create"
}192.168.0.0/16 will cover your IP address 192.168.1.20
A new version of configurator has come. once updated for anyone who added /ssl/ to the script will have to remove it for it to work.
salve a tutti io sono nuovo del gruppo mi sono avvicinato oggi a home assistant con varie guide sono riuscito ad installarlo,ma mi sono bloccato al configuratore non riesco a farlo partire:gioia::gioia::gioia::gioia: ecco come è la configurazione
{
“username”: “domo”,
“password”: “1234”,
“ssl”: false,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“allowed_networks”: [
“192.168.0.0/16”,
“172.30.0.0/16”
],
“banned_ips”: [
“8.8.8.8”
],
“banlimit”: 0,
“ignore_pattern”: [
“pycache”
],
“dirsfirst”: false,
“enforce_basepath”: false,
“notify_service”: “persistent_notification.create”
}
Log:
Traceback (most recent call last):
File “/configurator.py”, line 4841, in
main(sys.argv[1:])
File “/configurator.py”, line 4776, in main
load_settings(None)
File “/configurator.py”, line 3510, in load_settings
if PASSWORD and PASSWORD.startswith("{sha256}"):
AttributeError: ‘int’ object has no attribute ‘startswith’
scusate ma vi devo chiedere aiuto non riesco a farlo funzionare vi ringrazio anticipatamente
It would be nice if you would write in english here. But by looking at the error message the problem can be identified: add at least one character (a-z) to your password. Passwords that are only numeric are broken with the current release of the configurator.
ok I’ll try to write in english thank you very much
I’m having the same issue. I’ve tried the suggestions here. My issue is the URL from the “Configurator” option in the left menu takes me “https://hassio.local/configurator”. However, nothing appears. But if I manually put in “http://hassio.local:3218” everything works fine (notice not https. Instead, it’s http).
I’ve made changes to both config.yaml and the Configurator in the config directory. Both have the following values (again, not https):
panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: http://hassio.local:3218
I do have DuckDNS installed.
If hassio is run with SSL, the configurator has to be as well. Browsers don’t allow to display unencryptet http-content in a https-webapp. So set up SSL for the configurator and change the link for the panel back to https as soon as it’s working.
Thanks for the reply. But I think it is. Here’s the “Config” from inside the Configurator add-on:
{
“username”: “xxxxx”,
“password”: “xxxxxx”,
“ssl”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“allowed_networks”: [
“192.168.0.0/16”,
“172.30.0.0/16”
],
“banned_ips”: [
“8.8.8.8”
],
“banlimit”: 0,
“ignore_pattern”: [
“pycache”
],
“dirsfirst”: false,
“enforce_basepath”: false,
“notify_service”: “persistent_notification.create”
}
My local network is in the 192.168.x.x range. In config.yaml and Configurator files in my config directory, the values are:
panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: https://hassio.local:3218
So I’m not sure what else to change.
If this is working, then SSL is not working. I don’t know why, but if the configurator succeeds in loading the certificate, it can not handle plain http requests. So in some way your SSL configuration is not functional. Only if you manage to access the configurator with httpS, it will be embeddable in the hassio gui.
I have read the above but my Configurator still does not work…here is my config
“username”: “admin”,
“password”: “xxxxxxxxxx”,
“ssl”: false,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“allowed_networks”: [
“192.168.0.0/16”,
“172.30.0.0/16”
],
“banned_ips”: [
“8.8.8.8”
],
“banlimit”: 4,
“ignore_pattern”: [
“pycache”
],
“dirsfirst”: false,
“enforce_basepath”: false,
“notify_service”: “persistent_notification.create”
}
When I select configurator from the left panel…the right is blank…no way to select files.
Help. Tx. Fred J.
Do you access hassio via http or https? If you have configured hassio with SSL (and thereby access it with https), then the configurator has to be configured with SSL as well.
And what happens if you browse directly to the URL you have set for the panel_iframe?
Hi Daniel, I am accessing it on my local network, so I did not think I needed to include the SSL? I can access it by going direct to http://192.168.1.20:3218/ if I am logged into HA from 192.168.1.20:8123. I do have Duckdns set up…if I access HA from Duckdns, I can not open the URL directly. I did try changing my config to SSL true…but that did no work either. Here is the config.
panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: http://192.168.1.20:3218/
Thanks, Fred J.
In case this helps someone else, I’m running Home Assistant 0.88.1 and Configurator v2.
I was successfully using:
“certfile”: “/ssl/fullchain.pem”,
“keyfile”: “/ssl/privkey.pem”,
But after a power cycle of the HomeAssistant server, configurator broke, and the log was giving that same:
Traceback (most recent call last): File "/configurator.py", line 4841, in <module> main(sys.argv[1:]) File "/configurator.py", line 4831, in main server_side=True) File "/usr/local/lib/python3.6/ssl.py", line 1149, in wrap_socket ciphers=ciphers) File "/usr/local/lib/python3.6/ssl.py", line 747, in __init__ self._context.load_cert_chain(certfile, keyfile) FileNotFoundError: [Errno 2] No such file or directory
I ended up clicking the “Reset to Defaults” button under the Config box. I re-entered my credentials in the config, but I left the cert settings as:
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
For some reason, this is now acceptable, and configurator is running exactly as it ought to, presenting the valid SSL cert when I connect to it. I don’t know the reason for this, but it’s working now. Hope this helps someone else.
Those two options have changed a while ago. It is always expected, that the certificate and key are located within the /ssl directory. So the path got hardcoded internally. This way users only have to enter different filenames in case they don’t match the defaults.
That makes perfect sense; it’s just odd that “/ssl/certname” was working before and broke after a reboot, not after something like an update where you would expect it to break. 