Upgraded to 0.74.0 & somthings not right

Hi Guys,

I upgraded to 0.74.0 today & I just can’t seem to get HA working right. I was running Hasbian on a RPi3B+, tried upgrading Hasbian & that didn’t go so well, then tried Hass.IO & its gone better.

I’ll list some of the issues I’m facing in the hope that someone can help:
The “Check Config” button just spins, never reports back if valid or invalid.
The Error log from the GUI is also the same, just spinning.
The Hassio “addons” page is blank.
No data is kept in the “Logbook” or the “History” tabs.
Can’t save new automation/scrips, the file is empty after saving.
I can’t seem to get access via HTTPS, HTTP works fine though.

Is there any way to way get things back up and running like normal?

The home-assistant.log does spit out a bit of info but of out of my depth & I’m not too sure what to do with it:
“2018-07-21 21:51:24 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2018-07-21 21:51:46 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/aiohttp/web_protocol.py”, line 378, in start
resp = await self._request_handler(request)
File “/usr/local/lib/python3.6/site-packages/aiohttp/web_app.py”, line 341, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.6/site-packages/aiohttp/web_middlewares.py”, line 88, in impl
return await handler(request)
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/http/static.py”, line 67, in staticresource_middleware
return await handler(request)
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py”, line 34, in real_ip_middleware
return await handler(request)
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/http/ban.py”, line 68, in ban_middleware
return await handler(request)
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/http/auth.py”, line 43, in auth_middleware
request.headers[HTTP_HEADER_HA_AUTH].encode(‘utf-8’))):
UnicodeEncodeError: ‘utf-8’ codec can’t encode character ‘\udca3’ in position 13: surrogates not allowed”

And to top it all off, I can’t seem to SSH into my Pi anymore, I get “ssh: connect to host port 22: Connection refused”.

Any help would be appreciated.

On the last point, i think you need to install an addon for ssh.

1 Like

What “didn’t go so well” with upgrading hassbian? Maybe that would be easier to sort out. Assuming you made a backup of your SD card… You did make a backup of your SD card, right? :thinking: :wink:

1 Like

Many thanks, @nickrout, I’ve kind of got access to SSH again(after a reflash of the SD card), but now can’t remember the correct password. At least I’m not getting the same “port 22: Connection refused” message as I was before, so that’s a step forward, thanks for your help.

Many thanks for your reply @finity, I did make a copy of my files before updating Hasbian. I had been getting a lot of errors in the log for a few days before I decided up upgrade. (one of the main reasons making me want to update) - when I first updated Hasbian I had most of the issues I listed above, spinning config wheel & unable to save new automations/scripts. (still have access via HTTPS though).

Did your hassbian work properly before the upgrade? What version were you running?

As an aside, I updated hassbian to 0,74 with no ill effect.

Yes, everything was fine. it was running great, then a few days ago I got a message on the GUI saying something like “couldn’t setup Switch component, same for MQTT, same for Tado” - so I kept an eye on the log for a few days, kept getting errors (but everything was working fine).
Decided up upgrade and well, now I can just turn stuff on/off & that’s about it.

I’m glad its gone well for you, I wonder if I have done something differently?

It’s a shame coz everything was going great - if I could just get the access via HTTPS, scrips & automation’s working I’d be fine. Just limited to basic on/off at the moment.

Interesting, could you tell me more about this error log? Is on your hassbian or hass.io?
What is your browser version? Do you have any other custom or 3rd party components not from homeassistant?

This error shows there are invalid char � in one of HTTP Request Header received by HA

By the way, this position suppose to be your api_password, so any special char used in your password?

Maybe you should just flash the last known good working copy of hassbian onto your SD card and boot it up. Then look at the logs to see how things are going. It might be easier to work forward from there. but take another backup of the SD card first…

What version of HA were you running before everything went to crap?

1 Like

I updated with the standard

sudo hassbian-config upgrade homeassistant
1 Like

Hi, @awarecan, many thanks for your reply.

(I did type a reply, but then reread yours) - and then removed the special characters from my password and “hey, presto” - the config button is working and all the data is back in the history tabs.

Looks like that has worked, I’ll try and give it a full test run tomorrow, but from the looks - this was the issue.

Great. Another reason we need to move to new auth system :laughing: