Refused to connect

[RizzleQ]

Been using this extension for months with no issue. Suddenly this started happening. Doesn't matter what URL I use (local hostname, IP address, internet domain HTTPS address), it's always refused. There's no failed login or any logs that I can see in Home Assistant that shows a problem. Any ideas where to start?

[DuDe-75]

Same here...I'm not entirely sure but I think it is because some updates in Home Assistant. At least I see this error since about the time Home Assistant had a Supervisor update (version 2023.08.3). I'm using Home Assistant on a Raspberry Pi 4.

I could be wrong tho, but it would be nice to have a fix on this one.

[RizzleQ]

Hmm, I don’t recall precisely when this started happening. Was probably around a week and a half ago, which does coincide with when I upgraded to supervisor 2023.08.3.

I wonder if any of the changes made to that version could have an affect:

https://github.com/home-assistant/supervisor/releases/tag/2023.08.3

[bokub]

Hello !

I have Home assistant 2023.8.4 installed on my Pi and I don't have this problem...

[RizzleQ]

That sounds like the previous stable version of Home Assistant Core from 2 weeks ago. I also recently upgraded my HA Core to 2023.9.0 if that somehow is related to this.

The latest version of Supervisor is 2023.09.0 which would be worth testing to see if it helps. It's not showing as an available update for me yet.

@bokub is there any troubleshooting I can do to narrow down what might be going on?

[bokub]

Oh I didn't look at the right version, my supervisor version is 2023.08.3, and I don't have the problem

[bokub]

@RizzleQ The extension is nothing more than a fancy <iframe src="YOUR_URL" />

Is your URL still responding if you copy-paste it into your browser address or if you call it using curl ?

If yes, maybe look at the response headers of your URL and check if there are new headers such as X-Frame-Options 🤷

[RizzleQ]

@bokub I did some digging and this problem is caused by this Breaking change in HA Core 2023.9.

If I disable use_x_frame_options by setting it to false in the http configuration, this problem is resolved :)

[RizzleQ]

Since this isn't a problem with this extension, I'll close this as resolved but @bokub you may want to let your users know about this change in HA so they can get this extension to work properly.

[bokub]

Thanks a lot @RizzleQ 👍

I'll keep the issue open until the README is up to date

[nomonkeynodeal]

Every time people in a thread come up with a solution for something and don't say what the solution is or how to access it, an angel dies.

Add to the configuration.yaml:

http:
  use_x_frame_options: false

[DuDe-75]

that is i right...and don't be alarmed when editing the config within Home Assitant using something like 'Studio Code Server', and you get a warning that "Propert use_x_frame_options is not allowed". Just check if it is added with the proper syntax (see the comment before this one), then restart Home assistant, and the extension will work ;)

Mine looks like this:

[SmartLiving-Rocks]

Hello!
It must be something else - in my case. I am on a Mac 10.14.6 and just tested the extension with another user profile, and it worked directly.

On my main profile, I have noticed the issue after I have changed my password. So I assume that there is something password related cached somewhere.
Of course, I have cleared the cache and deleted and reinstalled your browser extension!
Any ideas?

Thanks in advance