Issue with Configurator showing in Haas.IO

It’s an SSL error.

I get it if I try http rather than https

Change to https and you will get in even with your IP address instead of the domain. Then you might have to go to advanced and tell chrome to ignore the ssl error and then you can fix it.

Hi, I’m new on this.
Already I can open my hassio on my domain.duckdns.org, I left hassio ip as static, I open the DMZ (using the hassio ip) and portforward 8123-> 443 and 3218 -> 3128 but still I can’t open the configurator on my domain (use https:domain.duckdns.org:3218) but nothing happen just the error ERR_EMPTY_RESPONSE.
I don’t know what to do :frowning:

please, I ask for your help.

Check your port forwards 3218 is not 3128

Sorry, my mistake, was 3128 -> 3218. But the configurator finally works, the issue was I have “0.0.0.0/0” and others ip in my allowed ip but when i left just 0.0.0.0/0 the configurator back to normal.

Thanks for the help!

Hi Everyone!

When I open the Configurator in HA, I just get another new page of HA. It’s like it direct to the wrong URL.
Has it anything to do with the SSL?

I have done it exaclty like you have described it erlier in this post.

If I don’t forward 3218 it just trying to Connect a few minutes then I get a Connection error. But when I Forward Port 3218 i just get this strange symptom.

Any ideas?

Could you please post the related config?

Sure!

This is how it looks in the Configurator Add-on:

{
“username”: “XXXXX”,
“password”: “XXXXX”,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“ssl”: true,
“allowed_networks”: [
“0.0.0.0/0”
],
“banned_ips”: [
“8.8.8.8”
],
“banlimit”: 0,
“ignore_pattern”: [
pycache
],
“dirsfirst”: false,
“enforce_basepath”: false
}

And this is how the Configuraton.yaml looks like:

Configurator

panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: https://XXXXXX.duckdns.org:3218

Any problems here?

I’ve also tried with the ip 192.168.1.0/24 but still no different.

Looking good actually. I’d ask if you are sure you’re really forwarding 3218 to 3218. But that would be too obvious.

Yes. I’ve Forwarded port 3218 in my Gateway. So that shuoldn’t be the problem. But when I look in the Configurator Add-On Log it looks like this:

INFO:2018-07-21 20:15:08,027:main:Starting server
INFO:2018-07-21 20:15:08,034:main:Listening on: https://0.0.0.0:3218
INFO:2018-07-21 20:15:56,759:main:Requesting authorization
INFO:2018-07-21 20:15:56,760:main:1XX.1XX.XX.XX - “GET / HTTP/1.1” 401 -
INFO:2018-07-21 20:16:00,654:main:Requesting authorization
INFO:2018-07-21 20:16:00,655:main:1XX.1XX.XX.XX - “GET /api/websocket?latest HTTP/1.1” 401 -

I’ve tried Google this shit but can’t get any answers. Do you get anything out of this? It feels like the HTTP part is a bit off…

The logs look like the forwarding is somehow messed up. The configurator is receiving requests that are intended for Home Assistant. And as you state, trying to open it brings up Home Assistant. I don’t know what’s happening there, but this is definitely not normal. Do you use any kind of reverse proxy in front? And have you restarted your router? Maybe clearing the NAT table (a restart would do that) can fix the issue.

SOLVED!

I tried to log in to HA from another computer and then the Configurator was working fine!!?
I even tried different browsers with the same result

The problem seemed to be in the browser (Chrome).
I uninstalled Chrome and Installed it again and then it just worked!

I have no idea what caused the problem.

But now it’s working fine!

Thanks for your time and tips!

1 Like

Hello,

I have followed the thread above and opened the port 3218, changed the configuration of the configuration add-on and the configuration.yaml as done above.

In the config file the url is https://hassio.local:3218.
As allowed networks I have 0.0.0.0/0 in both the add-on configuration and in configuration.yaml.

I come to the configurator page but it is blank. I get no error message and the add-on log only states:

INFO:2018-09-10 13:08:53,074:main:Starting server
INFO:2018-09-10 13:08:53,083:main:Listening on: https://0.0.0.0:3218

It doesn’t matter if I try from my Mac (Safari) or from my iPad within the app.

What can I have done wrong.

Hi again,

The configurator appeared on the Mac when I change from https://hassio.local:3218 to the relevant ip-adress https: x.x.x.x:3218.

I still cannot get in from my iPad. When reaching it from the Mac I came first to a login page. The login page is not show in my iPad.

I’m having the same problem with trying to get a link to the configurator in the side-bar. Per the Home Assistant documentation, I added the following code to the end of my configuration.yaml file. A tab for the configurator shows up in the sidebar along with the wrench icon but when I click on the tab, nothing happens. I’ve replaced the reference to “hassio.local” with the static IP address assigned to my Rasp. Pi but no luck. I’ve replaced the url with the one which is shown in the new tab window. That worked once then I got a “401: Unauthorzed” message. Suggestions:

panel_iframe:
configurator:
title: Configurator
icon: mdi:wrench
url: http://hassio.local:3218

I’m have the exact same problem as pcushing.
I followed the documentation and the menu entry is created. But when i click on it it just says connection refused.
I tried to modify the config of the Configurator in the add-on menu, but all my settings are restored to default when I restart it?

Any help would be appreciated!

The side panel configuration has changed for addons using the new ingress method. This configuration will work.

panel_custom:
  - name: hassio-main
    sidebar_title: Configurator
    sidebar_icon: hass:settings
    js_url: /api/hassio/app/entrypoint.js
    url_path: configurator
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
4 Likes

The following instructions work using panel iframe:

  1. In configurator press the cog. (assuming ýou can access it from the add-on page pressing web ui)
  2. Choose new tab.
  3. Copy the url in the new tab and paste that url in your panel iframe config.

No need to have any port open.

Thanks. Worked nicely. Was even able to switch the icon from the gear (“sidebar_icon: hass:settings”) to the wrench (“sidebar_icon: mdi:wrench”).

I had previously been able to make that approach work but (1) was troubled by the very specific resulting url (“http://hassio.local:8123/api/hassio_ingress/M45sD0qxqeJB7ODkM59vvvwelDm1FP7pHbkP6ghH7X/”) and (2) started getting “401: Unauthorized” messages.

In any event, was able to get it to work thanks to the new ingress method.

Thanks.

THNX David that solved it!!

1 Like