Page MenuHomePhabricator

Fix VE4ALL extension in DicoAdo.org : http timeout error when VEForAll connects to Parsoid
Closed, ResolvedPublicBUG REPORT

Event Timeline

$ is not defined is provoked by a little script added by the company Dokit when they made some change to the Foreground skin. It attempts to call masonry (a library for organizing elements AFAIK) but fails, I don't know if it is the reason why VE4all does not load.

Good news: "$ is not defined" is now fixed
In fact, the problem already occured on legacy dicoado and was fixed, I just transferred the fix.
The wmch version is on an old version of the "legacy" dicoado. For example wmch.fr.dicoado.org is on MW 1.35.2 while fr.dicoado.org is on 1.35.5. Also we updated a few things in our config on legacy, so we will need to also import thoses changes in the wmch server.

Bad news: this issue had nothing to do with VEForAll :D
The problem seems to come from the fact that the server isn't able to connect to itself. Try wget https://wmch.fr.dicoado.org while being connected on the server and it will wait forever for a response that doesn't come.
Thus, the VEForAll API cannot send any request to the REST API for Parsoid, it fails with a HTTP timeout error. Thus the visual editor fails to load.
Here's a scheme to understand better, using Firefox, Dia and the "uppercut" page of Dicoado.

dicoadobug.png (1×4 px, 367 KB)

the parsoid url that was used by VEForAll and that showed up in the log was, if I recall correctly, something like https://wmch.fr.dicoado.org/wiki/rest.php/wmch.fr.dicoado.org/v3/transform/wikitext/to/html/uppercut

Raphoraph renamed this task from Fix VE4ALL extension in DicoAdo.org "$ is not defined" to Fix VE4ALL extension in DicoAdo.org : http timeout error when VEForAll connects to Parsoid.Nov 3 2022, 3:24 PM
valerio.bozzolan claimed this task.

I talked to the LAN manager of this VPS. The bad news is that I have not a good explanation for that. I'm more confused than before. The good news is that I've fixed resolving this hostname directly inside /etc/hosts.