Is it not possible to use a non-standard HTTP port on an iFrame card?

Configuration
1

I have a webpage running on my server on a non-standard port (lets say 11111), and I want that to be in an iFrame card. But I keep getting “www.hompeage.com:11111 denied connection”. (Or something to that effect, it’s in Norwegian). Does that mean that I can’t embed a webpage unless it is on port 80?

Edit: I have seen some posts about it, but they were mostly about port 3000 for some camera stuff and https, noen of which helps me.

2

If the main page is HTTPS, then the iFrame must also be HTTPS.

Is that your issue?

3

No, both are HTTP, not HTTPS. But maybe password may be the problem? The case is:

On my cabin’s Home Assistance instance on one non-standard port I want to have an iFrame that opens the house Home Assistant on another non-standard port.

But is it possible that the denial is not because of the port, but because it’s not possible to type in a password in an iFrame?

Edit: The reason is that I wanted to control something in the house from the cabin, and it seemed like the easiest way to do it, since I don’t have them linked with remote Home Assistant or something like that. I do have a link between the places in SoftEther, so maybe I should think about forwarding MQTT between the two servers instead?

Edit 2: I tried with another web service I have running, which needs a password, and that worked. So I’m still suspecting the non-standard port.

4

I believe you are correct. Not that it is non standard. But, it is not the same port as the original page. See here.

1 Like
5

Thanks, that explains it. Annoying, but I’ll have to find another way to do this, probably with MQTT forwarding.

Edit: Not necessary, actually. I already had a broker running on the server in the house that I don’t use anymore, but the cabin server had access to that over the SoftEther link. :grin: But I had to go via Node-RED, for some reason I don’t think Hass supports multiple MQTT brokers.