Closed tgrymatt closed 5 days ago
It looks like, that it is regarded to the master-branch and to the version 2.2.2. With Version 2.1.1 I don't have this problem.
It seems like this is related to the JavaScript change. Seems like it can't access the document when accessing from within an iframe. Do you have something like a docker compose where I could work on a fix? Haven't used Etherpad with Jitsi yet.
@SamTV12345 we installed Jitsi and Etherpad manually. But I have a docker, where I could deploy an Etherpad and try it with my test Jitsi. So if this helps you, contact me.
Hi, I have nearly the same problem. I get this massage: SecurityError: Blocked a frame with origin "https://app.example.org" from accessing a cross-origin frame. Protocols, domains, and ports must match. And this: SecurityError: Failed to read a named property 'document' from 'Window': Blocked a frame with origin "https://app.example.org" from accessing a cross-origin frame.
With Version 2.1.1 it works.
I have install it from git on a ubuntu 20.04 maschine.
Have same issue:
SecurityError: Failed to read a named property 'document' from 'Window': Blocked a frame with origin ......... accessing a cross-origin frame.
With version 2.1.1 everything works fine.
Is there a fix for this Problem?
Yep, same error on 2.2.4 whilst running with Odoo. Reading the pads works fine, but creating/editing doesn't.
The instances are on different subdomains, same TLD.
Also see #6618
@tgrymatt @ger82 @zib-ctrl @fmcsecurity Please try the latest develop image of Etherpad. I removed all cross origin iframe requests.
I'll close this for now. Someone already posted that it works now :)
Confirming it works for me to, just make sure you're on the 'develop' (not 'master') branch.
Is this the commit that fixes things: https://github.com/ether/etherpad-lite/commit/a61f634586017dcadffd859820b66cd5916cef3a ? We also run a jitsi meet server with embedded etherpad documents and are hitting a similar issue (the errors are actually more similar to those in https://github.com/ether/etherpad-lite/issues/6618). I'm wondering if we can cherry pick this specific fix onto 2.2.4 to minimize the delta between what we run and released code.
Or maybe a 2.2.5 release will be happening soon? It looks like there are a handful of other fixups on the develop branch currently.
I have installed etherpad-lite on a Debian 12 machine and configured an apache server. It is configured like this:
If I open https://etherpad.domain.tld on my computer everything is working fine. In the settings.json file I configured:
Now I installed Jitsi Meet on a different server to jitsi.domain.tld and I added the configuration for Etherpad to Jitsi:
etherpad_base: 'https://etherpad.domain.tld/p/',
If I am click on the Etherpad icon in a jitsi meeting, the website is showing me this error message:
But if I am using a different Etherpad which are public available like for example https://etherpad.bildung-rp.de it is working fine without any changed on the jitsi machine. (Sure, I changed the etherpad_base variable to https://etherpad.bildung-rp.de/p/)
Any ideas or hints?