Jeremy Davis's picture
Edmond writes via email:

Dear reader,

I have been testing the Etherpad instance but it keeps crashing.

What happens: when i try to use out of the box and open a new pad, it will hang with a message saying 'loading' and it ends with the message:

... javascripts/lib/ep_etherpad-lite/static/js/pad.js?callback=require.define at line 266'

It seemed to me that it only happened using http; so I forced nginx to SSL and installed Let's encrypt. This seemed to work fine. But then the error came back.

Searching the web there was suggested that the dabase should be changed to utf8mb4, which I did. (https://github.com/ether/etherpad-lite/wiki/How-to-use-Etherpad-Lite-wit...). But this doesnt solve it.

So now I am turning to you as it seems that I cannot find the issue at hand.

Thanks in advance,

Forum: 
Jeremy Davis's picture

So is this a new server running v14.0? Have you made any modifications or did it do this right from the start? I'll try to reproduce it and see what happens...
Edmond's picture

I just reproduced it with an out of the box instance v14:

http://52.18.99.20/p/test

It seems to happen when Mozilla comes in play in a Pad, after that the following error-page  is being showed after a while (in Dutch but saying that a property of setChannelState kan not be called):

An error occured
The error was reported with the following id: 'gYpFH3PpUMS3Qaqstj4S'

Please press and hold Ctrl and press F5 to reload this page, if the problem persists please send this error message to your webmaster:
'ErrorId: gYpFH3PpUMS3Qaqstj4S
URL: http://52.18.99.20/p/test
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; InfoPath.3; rv:11.0) like Gecko
Kan de eigenschap setChannelState van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen in http://52.18.99.20/javascripts/lib/ep_etherpad-lite/static/js/pad.js?cal... at line 266'
 
I will send you the password of this box private.
 
Jeremy Davis's picture

Although I noticed that you had a written a response on the pad. And that it appeared to be an issue behind your work proxy when using http.

Maybe you should just redirect http to https?

Edmond's picture

Thanks for your reply. IT @ work is reviewing the proxy with an external service provider. There seems to be happening some things there.

Redirecting to https isn't solving the issue as if parts of the website keep using http.

Lets close this issue here because it doenst seem to be an issue of the instance.

Add new comment