Etherpad Lite problems on Moodle 3.9.3

Etherpad Lite problems on Moodle 3.9.3

by Stefan Ostner -
Number of replies: 2


Hello,

we‘re trying to install the current version of the Etherpad Lite plugin on a Moodle 3.9.3 server. We‘ve already taken into account that Etherpad Lite 1.8.6 doesn‘t seem to work with Moodle, so we‘re running 1.8.5 on our system.

We have Etherpad running at etherpad.mydomain.tld:9001, and Moodle is running at konf.mydomain.tld. We‘ve checked whether the API key is correct and the cookie domain is setup as .mydomain.tld.

Upon creating an Etherpad activity, we see a while rectangle instead of the Etherpad content. Further investigation reveals that the Iframe does point to the created Etherpad, however the Iframe itself is empty, with no content between the body tags. The API responses on the Etherpad server also seem to indicate that everything is working as intended and that the new pad is actually created.

Navigating to etherpad.mydomain.tld:9001 directly in Firefox or Safari works and allows me to create new pads.

We‘ve tried everything that seemed to be applicable from earlier threads, but have so far come up empty.

Thanks in advance,
Stefan

Average of ratings: -
In reply to Stefan Ostner

Re: Etherpad Lite problems on Moodle 3.9.3

by Andreas Grabs -
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers Picture of Translators

Hi Stefan,

I can't find the information whether or not do you run your sites on https.
If your Moodle installation runs on https the etherpad installation must also run on https. Both installations should use valid certificates because actual browsers don't like to embed unsecure iframes.
Can you verify that the new pad is created by the API? What does the name look like?

Best regards
Andreas

In reply to Andreas Grabs

Re: Etherpad Lite problems on Moodle 3.9.3

by Stefan Ostner -

Hi Andreas,

thank you for the prompt answer which led us on the right tracks! The problem was indeed with http/https, as our test implementation of Etherpad wasn't running https.

All the best,
Stefan