-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Etherpad is not working / Working configuration missing #6359
Comments
Please explain what problem you are referring to. Did you use the instructions mentioned in the wiki? |
I just configured the Etherpad integration. The wiki-article is confusing because the
and
update: there is a different nginx config suggested in the forums. |
I tried but Access-Control-Allow-Origin, Content-Security-Policy etc always prevent the pad from being shown in the iframe |
I managed to make one further step towards a working setup it seems by following But now I am stuck again with a new |
Thanks. Do you happen to know how to resolve this icon problem I am having? The NGINX configuration for jitsi includes a directive for /static and so does the one for etherpad. I can only assume that the two clash. Do you have a working setup for jits+etherpad+nginx and, if yes, would you mind posting your complete config? Thanks! |
A symbolic link can resolve this issue. Not the best fix, but it seems to do the trick. |
Great, thanks, will give it a try! EDIT: Fixed it for me |
Closing this as this is now fixed / not an issue with Jitsi Meet per se. |
Has anyone tried this con Secure rooms? |
Hi,
I've been trying for days to get Etherpad working, have been raking through tons of forums posts, and asked in multiple places. But I couldn't find a single fully working configuration that reliably solves the Access-Control-Allow-Origin, Content-Security-Policy, XFRAME, whatever combination of settings is causing this problem. And I don't seem to be alone judging from the tons of people having asked similar questions in the past.
I therefore consider this a documentation bug that needs fixing. I envision a working configuration for NGINX and Apache would help 99% of people out there.
The text was updated successfully, but these errors were encountered: