Rook getting error 401 or start failures on most all addons

I’ve been super excited to join the community, but I’m not even out the gate and I need help. I want to be able to do more on my Pi 3 B+ than just Hass.io and the core addons (which looks AWESOME), so my research led me to believe installing Raspbian Lite and then adding Docker and Hassio was the best bet. It did install and fired up just fine, but most addons are failing to start and the ones that do just usually show a single line that has a 401…Unauthorized error.

Can somebody help me understand what I did wrong? I’ve looked at tweaking my configuration.yaml but nothing has helped yet.

I am running Hassio on Raspian Lite. What admins are failing?
There have been some recent changes affecting adding and the documentation met not be currently correct.

I’ve tried Logviewer, Configurator and I get 401. I ried installing Pihole and it never starts. That’s all I’ve tried so far because it appears to be a widespread issue on this install for some reason.

If those I am using Configurator what version of HA? I am currently on 0.91,4.
What is not working? If you go to the Hassio dashboard and click on Configurator there should be a link to open its web UI.

Same version, and when I click on Configurator in the sidebar I just get that 401 error. No idea why as it is a clean install.

OK, they changed that. Replace the iframe entry in your configuration.yaml with this.

panel_custom:
  - name: hassio-main
    sidebar_title: Configurator
    sidebar_icon: mdi:wrench
    js_url: /api/hassio/app/entrypoint.js
    url_path: configurator
    embed_iframe: true
    require_admin: true
    config:
      ingress: "core_configurator"

In 0.92.x they are supposed to have an addon option to add to the menu, I think. I had been waiting for 0.92.2 but I may try upgrading tonight.

Thank you for your continued assistance. I did add this to the file, and it did add a second Configurator entry (because apparently I’m on 92.1 and my memory stinks) which points to slightly different URL and entrypoint, but the result of each is still 401 Unauthorized.

I thought it might be because I hadn’t uncommented the http and base_URL lines in my configuration.yaml and setting the base_URL to the IP address (not using mDNS just yet), but commented or uncommented it doesn’t seem to help.

It appears to be some sort of issue with authentication on the API calls, I’m thinking, but I can’t seem to ID what is failing.

base_url is no longer required. IT may be optional with some addons.
They use something called Ingress.
I thought on 0.92 there was supposed to be a menu item, I assume under Hassio -> Dashboard-> Configurator, to add a menu item.

I did not notice a mention in the HA Release notes but Ingress was not mentioned until it got functional in 0.91.3.

The Configurator item is definitely there - but I get a 401 error even using that. To your comment, I guess that means there’s something wrong with the base setup - before I even begin considering the addons.

I think my config is the default for v 3.1 of the plugin. I see there is an update available.

Thank you very much for all your help! So I decided to do a fresh install again (which “failed”) and I was at my wits end until I stumbled across the solution. I’m “happy?” to report that it appears to work under Edge and Chrome. I was using Firefox and getting the 401 errors. The only correlation I can see is that after login, I get a blue popup at lower right that asks if I want to “save this login”. While I’m clearly logged into the front end, something is not getting passed properly. I found some older bugs that suggested this was fixed late last year, so I don’t know what’s up but it’s definitely consistently happened with every one of my installs.

Now that I am on Chrome - time to hopefully get this bad boy to do something :slight_smile:

Make sure your Chrome browser cache is cleared. I have seen things APPEAR to work in Chrome when it was using cached parts instead of the actual pages.

Working great so far! Thanks again!