Failed to read the 'localstorage' property from 'window': access is denied for this document

2020-06-25 14:18:41.422 severe: [61] org.jitsi.jibri.selenium.jibriselenium.run() an error occurred while joining the call: org.openqa.selenium.webdriverexception: : failed to read the ‘localstorage’ property from ‘window’: access is denied for this document.

Hi, I am new to the community and desperately desperate … I have this error that does not allow me to finalize the registration. As much as I have tried I have not obtained a different result, but above all I do not understand where the error or lack is … Do any of you know how to intervene?

Tomorrow I will insert the log files of the 4 services

hi , no I have no idea but you can see if you enter something wrong or somehting like that

If, as you say, I insert an error … a script in the final e.ah for example, it stops first … I guessed that the last step before recording calls it. From the web interface … meet … the initialization of the recording starts then stops due to an error. The files in the repository contain only the metadata.json.

I insert log files of the jitsi VM and the jibri VM[jicofo.log|attachment]jvb.log (3.1 MB) prosody.log (288.1 KB) browser.0.txt (212.9 KB) log.0.txt (86.8 KB) xorg.log (30.2 KB)jicofo.log (26.6 KB)

Hello,
is it possible that the problem in question depends on the access that iChromeDriver have from remote hosts? I also send you the STATUS of JIBRI

root@jbri:~# systemctl status jibri
● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-07-07 18:04:12 CEST; 51s ago
Process: 3289 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, status=0/SUCCESS)
Main PID: 3299 (java)
Tasks: 46
Memory: 236.3M
CPU: 9.123s
CGroup: /system.slice/jibri.service
└─3299 java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -jar /opt/jitsi/jibri/jibri.jar --config /etc/jitsi/jibri/config.json

Jul 07 18:04:13 jbri launch.sh[3299]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Jul 07 18:04:13 jbri launch.sh[3299]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Jul 07 18:04:37 jbri launch.sh[3299]: Starting ChromeDriver 83.0.4103.39 (ccbf011cb2d2b19b506d844400483861342c20cd-refs/branch-heads/4103@{#416}) on port 7281
Jul 07 18:04:37 jbri launch.sh[3299]: Only local connections are allowed.
Jul 07 18:04:37 jbri launch.sh[3299]: Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
Jul 07 18:04:37 jbri launch.sh[3299]: ChromeDriver was started successfully.
Jul 07 18:04:57 jbri launch.sh[3299]: Starting ChromeDriver 83.0.4103.39 (ccbf011cb2d2b19b506d844400483861342c20cd-refs/branch-heads/4103@{#416}) on port 14435
Jul 07 18:04:57 jbri launch.sh[3299]: Only local connections are allowed.
Jul 07 18:04:57 jbri launch.sh[3299]: Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
Jul 07 18:04:57 jbri launch.sh[3299]: ChromeDriver was started successfully.

Only local connections are allowed. is it possible ?

This error is due to chrome broswer launched by salenium is not having certificate to authenticate.
This issue can be solved by adding “–ignore-certificate-errors” in “/etc/jitsi/jibri/jibri.conf” under chrome{}.flags section.

chrome {
// The flags which will be passed to chromium when launching
flags = [

“–ignore-certificate-errors”

]
}
Restart jibri service.

i got this in there but now the recording and live streaming has a banner

chrome {
  // The flags which will be passed to chromium when launching
  flags = [
    "--use-fake-ui-for-media-stream",
    "--start-maximized",
    "--kiosk",
    "--enabled",
    "--disable-infobars",
    "--autoplay-policy=no-user-gesture-required”,
    "--ignore-certificate-errors”,
    "--disable-dev-shm-usage”,
    "--no-sandbox"
  ]
}

“Chrome is being controlled by automated test software”

You need to set Chrome managed policies. Check the guide - TUTORIAL - How to Install the NEW JIBRI

What are the policies that must be put in that file?