iFrame blank when displaing http://<ipaddress LMS server>:9000/material

stephanvdplas

I have used the iFrame (as well as MMM-iFrame) module(s) for showing the material skin interface of the Lyrion Media Server, formerly know as SqueezeServer or Logitech Media Server.
But since the latest MMM update (2.28.0), the iFrame show completely blank.
There are no (mpm) log errors or warnings when restarting MM2. Other websites, e.g. nu.nl as well as http://<ipaddress LMS server>:9000 (so the standard skin) are working.
How can I troubleshoot this?

stephanvdplas

O, to add this probably important information: This issue only exists on the mirror (Rpi Electron app) itself, not when browsing from another device to http://<ip address mirror>:8080. In that case it works perfectly well.

sdetweil

@stephanvdplas this module runs all in browser, so no messages in the npm start console

open the developers window, ctrl-shift-i, select the console tab

add a unique part of the module name to the filter field.

my guess is a cors error, or a reject due to our UserAgent name

stephanvdplas

@sdetweil ok I’ll have to attach a kb and mouse to the pi then. Will try this tonight.

sdetweil

@stephanvdplas you can do debug from a different system if you configured MagicMirror config.js to allow remote system access

stephanvdplas

@stephanvdplas no errors at all! Only a deprecation warning but it is about a different module .

Please help me to further troubleshoot. All other web content I tried is working fine and the content I want to show is working fine when browsing the mirror in a different browser via http://<ip address mirror>:8080.

So it must be some strange thing in electron or jsnode.

stephanvdplas

@stephanvdplas in the network tab I see errors:

This Set-Cookie header didn’t specify a “SameSite” attribute and was defaulted to “SameSite=Lax”, and was blocked because it came from a cross-site response which was not the response to a top-level navigation. The Set-Cookie had to have been set with “SameSite=None to enable cross-site usage.”

sdetweil

@stephanvdplas said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:

Set-Cookie header didn’t specify a “SameSite” attribute and was defaulted to “SameSite=Lax”

Ok, I don’t KNOW for certain, but our cors proxy might work there

change the url in the iframe config to

http://localhost:MM_PORT/cors?

the rest like this

// the url 
url=http://www.test.com/path?param1=value1 // example
// if there are headers, skip if not 
&sendheaders=header1:value1,header2:value2&expectedheaders=header1,header2

make sure quotes around the url string

karsten13

@stephanvdplas

mm has a simple internal cors proxy you could try.

So instead using the <original-url> in the iframe you could try http://localhost:8080/cors?url=<original-url>.

E.g. if your <original-url> is https://example.com try http://localhost:8080/cors?url=https://example.com

karsten13

ups, sam was quicker …