You don’t need the workarounds mentioned previously. There’s just an extra necessary that’s not well documented.
See commit 62f2d11cab2399ad4.
The steps are:
- uncomment ETHERPAD_BASE_URL (and keep the default value
- uncomment PUBLIC_URL and set it to
https://host:port of the jitsi frontend (e.g.
If these two variables are properly defined, the frontend loads an iframe
from PUBLIC_URL/etherpad so there are no cross-origin policy violations
And nginx is configured to take all requests to /etherpad/ and proxy them
to ETHERPAD_BASE_URL, using the internal docker network (hence the
All these guides get this wrong in some way:
if you edit the .env file, remember you have to delete the configuration directory ~/.jitsi-meet-cfg (or under root homedir if you run with sudo) in order to regenerate the configuration files.