# \[Request\] Allow non-HTTPS url's in Frame widget

**URL:** <https://community.homey.app/t/request-allow-non-https-urls-in-frame-widget/117420>\
**Category:** Dashboards\
**Created:** [October 5, 2024, 9:18am UTC](https://community.homey.app/t/request-allow-non-https-urls-in-frame-widget/117420 "2024-10-05T09:18:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 5, 2024, 9:18am UTC](https://community.homey.app/t/request-allow-non-https-urls-in-frame-widget/117420/1 "2024-10-05T09:18:56Z")

</div>

Using an `http://` URL in the Frame widget throws an error:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/9/2947aeb5d7652650ed7218a74cc0c5dd06afb9ca.png)

**EDIT** :

It looks like there’s something else going on.

When I use `http://` combined with a local IP address, it works. If I use `http://` combined with a local _hostname_ (most services in my local network have their own hostname in the `.lan` TLD), it fails with the above mentioned error.

---

<div class="post-metadata">

**Author:** ![Eilev](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eilev/32/114058_2.png) [@Eilev](https://community.homey.app/u/Eilev)\
**Post date:** [October 5, 2024, 9:41am UTC](https://community.homey.app/t/request-allow-non-https-urls-in-frame-widget/117420/2 "2024-10-05T09:41:45Z")

</div>

I guess this is the reason why I cant access the endpoints opened through the Local Api app (http), which I use on a page shown in Frame

---

<div class="post-metadata">

**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\
**Post date:** [October 5, 2024, 5:11pm UTC](https://community.homey.app/t/request-allow-non-https-urls-in-frame-widget/117420/3 "2024-10-05T17:11:58Z")

</div>

Hey @robertklep ,

Running Android, Homey app v9.0.0.1566

Great finding. But I can not reproduce it. When i enter my HTTP with hostname for Grafana server, it works just fine. It works with Ip-adress also, but that was not the issue. I am also entering the port number, do you?

I only got a HTTP server, so I do not have any more HTTP adresses to try out locally.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 6, 2024, 5:35am UTC](https://community.homey.app/t/request-allow-non-https-urls-in-frame-widget/117420/4 "2024-10-06T05:35:16Z")

</div>

> [@Marius\_Stensrod](#):
>
> It works with Ip-adress also, but that was not the issue. I am also entering the port number, do you?

I don’t need a specific port number, it’s running on port 80.

It seems to be specific to my `.lan` TLD, when I use (for instance) `.local` it does work. So perhaps it’s a local issue, although I’m not sure what it could be. I have two very different servers that both provide services on the `.lan` TLD, and for both it doesn’t work.

In any case, I’ll chalk it up to being a local issue 🤷🏼‍♂️