Configurator stopped working after update to 1.0

HI,

I was using hass.io for sometime now and all was working well until today. I updated hass.io to the latest version (0.75.0) and also updated configurator and restarted the raspberry pi. Everything in running well except for configurator for which I get the following error in the logs.

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

My config is as follows.

{

“username”: “admin”,
“password”: “XXXXXXXXXX”,
“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”
}

I am using a duckdns address and it was also working fine until today. I also have node-red running with no such errors.

Any ideas guys??

1 Like

Looks like it cannot find your certificate file.

Is there anyway to fix this. node-red has the same parameters and it seems to work fine.

I’m having the same issue

Same problem here. Updated to 0.75.0 and then, updated cofigurator to 1.0. Same error log than in the first post.

That’s odd. Nothing changed regarding the location of the certificate. Please add the option "loglevel": "debug" to the config and restart the addon. On the bottom of the page then refresh the log and paste the output here (watch out for possibly sensitive information that should get redacted).

DEBUG:2018-08-04 15:15:35,800:__main__:Settings after looking at environment:
DEBUG:2018-08-04 15:15:35,801:__main__:{'VERIFY_HOSTNAME': '', 'SSL_CERTIFICATE':     'fullchain.pem', 'HASS_API_PASSWORD': 'XXXXXXXXXXXXXXXXX', 'DIRSFIRST': False,     'IGNORE_PATTERN': ['__pycache__'], 'ENFORCE_BASEPATH': False, 'HASS_API':     'http://hassio/homeassistant/api/', 'NOTIFY_SERVICE': 'persistent_notification.create', 'SSL_KEY':     'privkey.pem', 'PASSWORD': 'XXXXXXXX', 'USERNAME': 'admin', 'GIT': True, 'BANNED_IPS':     ['8.8.8.8'], 'IGNORE_SSL': False, 'BASEPATH': '/config', 'BANLIMIT': 0, 'ALLOWED_NETWORKS':     ['192.168.0.0/16', '172.30.0.0/16'], 'LOGLEVEL': 'debug'}
INFO:2018-08-04 15:15:37,208:__main__:Starting server 
DEBUG:2018-08-04 15:15:37,771:__main__:[]
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

This is the output I got. any hints on the problem??

Well, it tells me that the new way of providing the settings to the configurator actually works the way it should.
What you could try is changing the value of the option to the full path. I’m not a hassio user, so I’m not sure what the correct value is. I think it may be /ssl/fullchain.pem and /ssl/privkey.pem.

8 Likes

It works! Genious :wink:

yeah that worked for me too… thanks a lot. would never have figured that on my own.

1 Like

Same problem

JohnnyB, change the below text from your config from

“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,

to

  "certfile": "/ssl/fullchain.pem",
  "keyfile": "/ssl/privkey.pem",

Thats it…

1 Like

Hi,
Last night I downloaded the update and had the same problem as above, this morning I have tried again but now I can’t get passed my password screen in HA, I can get into the configuration.yami etc through Samba and have tried changing the password but this doesn’t work. Can anyone give me any ideas?

Have you enabled port forwarding

On my internet? I first thought that could be an issue, but if that wasn’t working would I even be able to get to the password page?

Are you accessing your front end for hassio from local ip address or from remote link.

from the duck.dns link

Did you try https://“youaddress”.duckdns.org:8123

Sorry, I should have been clearer, yes, it’s from that link that I get to the password page. But then when I enter the password it doesn’t let me in. The app has also stopped working. There is a section at the top of the settings page that says “myaddress.duckdns.org:8123 - 0.73.2 - HTTPS - Requir… " if that is anything to do with the issue.

Did you forget to put the s in https?