Frontend: Unable to access Hass.io menu

[talondnb]

Home Assistant release with the issue:

Home Assistant 0.70
Hassio 105

Browser and Operating System:
Home Assistant iOS App, iOS11

Description of problem:
Unable to access Hass.io menu

[pdmay01]

I can confirm this as well. For me it also will not work on the app or a browser on iOS. However, it does work (very slow to come up) on a Windows machine only with Chrome browser)

[talondnb]

Same here, Chrome browser on Mac OS also works fine.

This issue was initially reported on the iOS app github but was closed and advised to report here.

[balloob]

Errors in the log? (see dev tool -> "i" icon)

[stephenhouser]

Same problem on macOS FireFox 60.0.1 (64-bit). Multiple machines tested.

No apparently relevant errors in the log for my system. The most recent messages were 12 hours ago (trying to access the screen on 2018-06-01 11:03

2018-05-31 20:19:16 WARNING (MainThread) [rflink.protocol] dropping invalid data: 20;66;Slave;Debug=40 00 20 00 08 8260; 2018-05-31 20:27:29 ERROR (MainThread) [homeassistant.components.updater] Could not contact Home Assistant Update to check for updates

[stephenyeargin]

I can confirm this as well with 0.70.1 (hassio version 1.3.0) across Chrome, Firefox and Safari for Mac. There is nothing in the console.log that indicates there was a JavaScript issue. I had not seen this issue in 0.69.

[Phontana]

I did get an error in the console. See the related issue.

[tatunts]

Hello everyone! Me too. Blank page when trying to open Hass.io tab on all iOS devices. Happening since version 69. Thanks!

[Tomfr06]

Same issue HA 0.70.1. Hass.io Supervisor 105
Does not work with iOS app 1.1.1. Safari 11.1.1, Mac Firefox 60.0.1.
Does work with Mac Chrome 67.0.3396.62
(using SSL).

[ghost]

Same issue here.. HA 0.70.1 Firefox 60.0.1 & Firefox Nightly 62.x
Some log but no error or what so ever..

1. Open http://192.168.178.xxx:8123/ (working fine)
2. got into options (working fine)
3. got into hass.io panel (blank page with sidebar)

2018-06-02 20:25:02 INFO (MainThread) [homeassistant.components.http.view] Serving / to 192.168.178.xxx (auth: False)

2018-06-02 20:25:02 INFO (MainThread) [homeassistant.components.http.view] Serving /api/websocket to 192.168.178.xxx (auth: False)

2018-06-02 20:25:05 INFO (MainThread) [homeassistant.components.http.view] Serving /api/websocket to 192.168.178.xxx (auth: False)

2018-06-02 20:25:05 INFO (MainThread) [homeassistant.components.http.view] Serving /api/themes to 192.168.178.xxx (auth: True)

2018-06-02 20:25:05 INFO (MainThread) [homeassistant.components.http.view] Serving /api/translations/de to 192.168.178.xxx (auth: True)

2018-06-02 20:25:09 INFO (MainThread) [homeassistant.components.http.view] Serving /api/cloud/account to 192.168.178.xxx (auth: True)

2018-06-02 20:25:12 INFO (MainThread) [homeassistant.components.http.view] Serving /api/hassio/app-es5/index.html to 192.168.178.xxx (auth: False)

I get "Serving /api/hassio/app-es5/index.html to 192.168.178.xxx (auth: False)" when I click hass.io in sidebar.. auth:False seems somehow supics

[luxus]

i can confirm the issue with ios on ipad on iphone
chrome on windows works fine ..

[PierreScerri]

Have had this issue some time ago, version sixty-something.
Blank page on iOS 10 on iPad, iOS 11 on iPhone, Safari on MacOS High Sierra using the app, local network and duckdns.
Works with Chrome on the Mac and Windows.

[briancline]

I can't get this panel to work on any desktop browser. Just installed hass for the first time about an hour ago using the official hassio_install bash script, so I assume it's using the latest version of everything in the hass universe (the About page reports 0.70.1). I've seen no other issues yet, just this.

It does load from:

• [Mobile] Android 7.0
  
  
  
  • 🆗 Chrome 67.0.3396.68
  
  

It does not load under any of these browser/OS combos. Privacy mode does not make any difference (in my case, no third-party extensions can run under this mode).

• [Desktop] Windows 10
  
  
  
  • ❌ Chrome 66.0.3359.181
  
  
  • ❌ Firefox 59.0.3
  
  
  • ❌ Waterfox 56.2.0
  
  
  • ❌ Edge 41.16299.371.0
  
  
• [Desktop] Ubuntu 17.10 (Xubuntu)
  
  
  
  • ❌ Chrome 66.0.3359.181
  
  
  • ❌ Firefox 60.0.1
  
  
  • ❌ Waterfox 56.2.0
  
  
• [Laptop] Mac OS X
  
  
  
  • ❌ Chrome 66.0.3359.139
  
  
  • ❌ Firefox 58.0.2
  
  
  • ❌ Waterfox 56.1.0
  
  

[eemi]

I'm having the same issue. This is the error that the Safari console is logging, it only happens when accessing the Hass.io section:

Failed to load resource: http://192.168.2.10:8123/static/webcomponents-bundle.js.map the server responded with a status of 404 (Not Found)

[talondnb]

Issue remains on 0.70.1.

[JCrankWV]

Also another I cannot access the Hass.io menu with Safarii o OS 11 or MacOS High Sierra. I can access it on chrome on Mac.

version 0.70.1

[godinperson]

Can't access it from desktop or phone, even with Chrome. Guess we'll need a manual modification in order to update in the future

[cogneato]

Loading failed for the <script> with source “http://192.168.1.137:8123/frontend_es5/custom-elements-es5-adapter.js”. is what I see in Firefox console when trying the hassio panel

[GercoK]

I have the same problem. Cannot access hassio panel from my Mac using chrome or safari.
Also not from my iPhone.
How to update ?
I'm running hassio 69.1

[balloob]

hmm, weird that that file is gone. Let me see what's going on.

[PierreScerri]

Same here. Running Hassio 70.1

I can access the Hassio.io tab on Chrome using https://hassio.local:8123 or https://xxxxxxx.duckdns.org:8123 on my Mac but not with Safari.

The IOS app also gives a blank tab. Safari & Chrome can only access on the duckdns url not the local one.

I also have similar behaviour with the SonWEB add-on.

[c727]

Update Hassio supervisor to 107 (or wait 8 hours for auto update) and Home Assistant to 0.71

[kwatkins]

Saw this when I upgraded to 0.71, wasn't there before. I am going through nginx. Just saw this on
https://www.home-assistant.io/docs/ecosystem/nginx/
"You will at least need nginx >= 1.3.13, as WebSocket support is required for the reverse proxy."

Will try that.

And kick myself for upgrading, I didn't need too! Assuming regressing tests will keep bugs at bay is wishful thinking.