Cannot access Front End

I’m still trying to get out of the MQTT mess and can no longer access the HA front end on :8123.

I can access IDE and Tasmoadmin. Samba is also functioning.

I also have terminal access via SSH.

It seems that anything on port :8123, e.g. https://10.0.1.32:8123/config/core, refuses to connect, whilst http://10.0.1.32:8321/ide.html can be accessed OK.

http://10.0.1.32:8123/config/core doesn’t load either so it seems it’s not a security issue.

Where do I start the get the front end/home page back?

I’m sure this is a simple fix but just a bit beyond my means.

I’d really appreciate some help.

Are you running hassbian? Attempt one start and paste the log here from home assistant config folder.

This is by no means all of the log but I can’t post the whole thing due to character limits:

2018-11-07 14:52:42 WARNING (MainThread) [homeassistant.components.http] legacy_api_password support has been enabled. If you don’t require it, remove the ‘api_password’ from your http config.
2018-11-07 14:52:51 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=249 from 2018-11-07 06:01:19.967335)
2018-11-07 14:53:17 WARNING (MainThread) [homeassistant.setup] Setup of frontend is taking over 10 seconds.
2018-11-07 14:55:03 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:03 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:03 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:03 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:07 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:07 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:07 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:07 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:07 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:07 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:07 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:55:07 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)
2018-11-07 14:57:14 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.shutdown callback)
OSError: [Errno 107] Socket not connected

Here’s some more:

2018-11-07 14:57:38 WARNING (MainThread) [homeassistant.components.weather] Setup of platform darksky is taking over 10 seconds.
2018-11-07 14:57:38 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform template is taking over 10 seconds.
2018-11-07 14:57:38 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform time_date is taking over 10 seconds.
2018-11-07 14:57:38 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform template is taking over 10 seconds.
2018-11-07 14:57:38 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform systemmonitor is taking over 10 seconds.
2018-11-07 14:57:38 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform time_date is taking over 10 seconds.
2018-11-07 14:57:47 WARNING (MainThread) [hbmqtt.mqtt.protocol.handler] BrokerProtocolHandler Unhandled exception in reader coro: IncompleteReadError(‘0 bytes read on a total of 1 expected bytes’,)

And more. None of this makes much sense to me so I appreciate your help.

ConnectionResetError(104, ‘Connection reset by peer’))
2018-11-07 15:02:50 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/hbmqtt/broker.py”, line 343, in stream_connected
yield from self.client_connected(listener_name, StreamReaderAdapter(reader), StreamWriterAdapter(writer))
File “/usr/local/lib/python3.6/site-packages/hbmqtt/broker.py”, line 353, in client_connected
remote_address, remote_port = writer.get_peer_info()
File “/usr/local/lib/python3.6/site-packages/hbmqtt/adapters.py”, line 172, in get_peer_info
return extra_info[0], extra_info[1]
TypeError: ‘NoneType’ object is not subscriptable

can you post your full configuration.yaml?

put it inside

Three ` marks on this row
Config here
Three ` marks on this row

Or to pastebin instead. Remove personal info.

homeassistant:
  # Name of the location where Home Assistant is running
  name: Dryderdale Hall
  # Location required to calculate the time the sun rises and sets
  latitude:
  longitude: -
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 205
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: Europe/London
  customize: !include customize.yaml

mqtt:
  password: hello

hassio:

# Show links to resources in log and frontend
# introduction:

#auth_providers:
#  - type: homeassistant
# Uncomment next line if you want to enable legacy API password support
#  - type: legacy_api_password


# homekit:

# Enables the frontend
frontend:

weather:
  - platform: darksky
    api_key:

# Enables configuration UI
config:

notify:
  - name: Prowl
    platform: prowl
    api_key: !secret prowl_api
  - name: neil_prowl
    platform: prowl
    api_key: !secret neil_prowl_api
  - name: iPhone
    platform: ios
    target: !secret ios_ash_x_push_id
    

remote:
  - platform: harmony
    name: lounge
    host: 10.0.1.27

http:
  # Secrets are defined in the file secrets.yaml
  api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  base_url: 10.0.1.32:8123
  #base_url: 
  #ssl_certificate: /ssl/fullchain.pem
  #ssl_key: /ssl/privkey.pem

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# device_tracker:
#   - platform: nmap_tracker
#     hosts:
#     - 10.0.1.63
#     - 10.0.1.50
#     - 10.0.1.141
#     home_interval: 10
#     exclude: 10.0.1.32

# Track the sun
sun:

# Google Calendar sensor integrsation
google:
  client_id: !secret google_client_id
  client_secret: !secret google_client_secret

# mqtt:
#   broker: core-mosquitto
#   username: !secret mqtt_username
#   password: !secret mqtt_password

ring:
  username: !secret ring_username
  password: !secret ring_password

# Text to speech
tts:
  - platform: google
  
panel_iframe:
  configurator:
    title: Configurator
    icon: mdi:wrench
    url: http://10.0.1.32:3218

  tasmoadmin:
    title: TasmoAdmin
    icon: mdi:lightbulb-on
    url: http://10.0.1.32:9541

  ide:
    title: IDE
    icon: mdi:code-braces
    url: http://10.0.1.32:8321

  mdiindex:
    title: MDI Icon Index
    icon: mdi:vector-square
    url: https://cdn.rawgit.com/james-fry/home-assistant-mdi/efd95d7a/home-assistant-mdi.html

# Cloud
cloud:
  google_actions:
    filter:
      include_entities:
        - script.lounge_tv_off
        - script.garage_door
      exclude_entities:
        - switch.garage_door_opener
      include_domains:
        - script

group: !include groups.yaml
alert: !include alerts.yaml
input_number: !include input_slider.yaml
#harmony_control: !include harmony_control.yaml
automation: !include automations.yaml
script: !include scripts.yaml
binary_sensor: !include binary_sensor.yaml
switch: !include switch.yaml
#arlo: !include arlo.yaml
sensor: !include sensor.yaml
input_boolean: !include booleans.yaml
input_select: !include input_select.yaml
ios: !include ios.yaml

Is that what you need?

Most of the warnings seem to relate to mqtt. Try removing that from the config.

Are you running hassbian? Remove also the http stuff.

These are just for sake of tests.

Thanks.

I’m not sure about hassabian. I just installed Hassio to an SD card and went from there.

I originally had Mosquitto MQTT but that was removed and I followed the instructions for the Integrated MQTT. And it worked.

I then installed the IDE update, restarted and lost access.

Aa okay, you’re on hassio. I haven’t familiarized myself with the special aspects for that. Hope someone else have more tips.

Thank you.

try removing mqtt from config.yaml. That’s what i did prior to reboot. Follow these steps if you can get your front-end backup. Have you got a backup you can recover from?

if you use themes then remove frontend: from your configuration.yaml. That caused an error after I upgraded to 0.81. Also remove the mqtt: from your configuration.yaml

I removed mqtt: from config.yaml and I’m back in! Phew!

However, when attempting to configure MQTT in Integrations I get ‘cannot connect to broker’.

What should I be entering here?
What user name and password?

I read this post but I’m not clear how to set the MQTT user and password in users.

I have three users there: me and two Homeassistant users (sys generated), that can’t be removed.

Screen2018-11-07_06-04-10_pm

If I create another ‘fictitious’ user, how does it link through to being the MQTT user and password?

All of my devices use my home assistant user name and password as the MQTT password (which previously matched the Mosquitto username and password) but that doesn’t work with configuring MQTT in Integrations.

Screen2018-11-07_06-20-34_pm

Almost there. I just need a final nudge in the right direction from you guys.

nah just put your user from the addon config in the integration mqtt menu. worked for me

You mean the Mosquitto addon config?

I thought MQTT was integrated and the addon wasn’t required now.

Yeah it works for me. Try it out. I still get “Socket error on client <unknown>, disconnecting” but I can switch stuff from the frontend like it used to be so I’m happy with that.

OK. Thanks.

I still get ‘cannot connect to broker’.

username and password should be in quotations “”

{
  "logins": [
    {"username": "local-user", "password": "mypw"}
  ],
  "anonymous": false,
  "customize": {
    "active": false,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

The Socket error on client <unknown>, disconnecting comes from devices where you have to set the new username and password because homeassistant as username isn’t allowed anymore. Just found that out