Talk:Parsoid/JS/Troubleshooting

There are several points of clarification that should be added to troubleshooting guide
I have added hidden comments to the page saying where I think there needs to be edits. I am not personally able to edit these things as I am myself using the troubleshooting guide right now and trying to learn how to use Mediawiki but I hope my feedback on where the structure of the guide is unclear will be of use to someone who is more knowledgeable on this issue.

Do sites that go through https rather than http need to similarly have parsoid do the same?
Do sites that go through https rather than http need to similarly have parsoid do the same? --Silversonic (talk) 11:48, 25 November 2013 (UTC)
 * Depends on how you plan to use Parsoid. If you use it with VE and install Parsoid on the same machine or behind a firewall, then the communication between the VE PHP extension and Parsoid does not need necessarily need to be encrypted. The communication between the browser and MediaWiki (the VE extension) will still be encrypted, which is what you probably care about. -- Gabriel Wicke (GWicke) (talk) 16:09, 25 November 2013 (UTC)
 * Thank you for the clarification. I'm mostly concerned with getting it to work... it's hanging when I try to use the visual editor, and the editor times out while the parsoid node says that it connected.  I was hoping this might be the answer why but alas, I need to keep looking. --Devin Roark  (silversonic) 20:33, 25 November 2013 (UTC)
 * Does anyone have a solution to this problem? I've been struggling with the same issue for a week. I'm running Parsoid for VE on the localhost. When I edit a page in the wiki, parsoid.log reports that the parsing completed successfully, however no result ever appears in the wiki as the editor hangs. Any advice is appreciated... --JeffC
 * Have the same problem --suthernfriend

Adding more parsoidConfig.setInterwiki statements in.
In the main Page it is said :
 * "You can set up any number of interwikis by adding more parsoidConfig.setInterwiki statements in ."

Can you give an example of this ?

Is it this writing ? :

--Dieudo (talk) 23:02, 4 March 2014 (UTC)

Parsoid Did not find page revisions for *
I'm using MW 1.26alpha with VisualEditor 0.1.0 and Parsoid 0.2.0. I used to use MW with VisualEditor and Parsoid with a previous version of MW with no problem at all, but now, after upgrading to MW 1.26alpha, I'm having this error in the parsoid logs: "[fatal/request][localhost/v3/page/html/Pàgina_principal/1668] Did not find page revisions for V3/page/html/Pàgina_principal/1668"

What's wrong? Any idea?

Thanks.

Robert.

posting this to Visual Editor
I believe this is a problem with VisualEditor as I can fix the problem by changing manually the url called to build the editor. I change the action from "parse" to "metadata", then it works.


 * Wait, how exactly did you fix this? where did you post it "on VisualEditor"? I'm still having this problem. Cd1207 (talk) 08:03, 22 July 2016 (UTC)

Cover "parsoidserver-http: HTTP 0 problem" please?
I've seen "parsoidserver-http: HTTP 0 problem" mentioned several times on the MediaWiki Support Desk. Could this please be covered here? Thanks in advance.

Handling 404 errors
Another one to potentially cover from IRC: "When I click on Edit button on my wiki's Main Page iI get this error: Error loading data from server: 404: parsoidserver-http: HTTP 404. Would you like to retry? How can I try to fix it or to get more information on what happened?" --Malyacko (talk) 08:46, 1 June 2016 (UTC)

-- Wait, there is still no solution to this? Been having the 404 problem ever since i got VE and Parsoid (on Heroku) set up, can't figure out what is causing it, and searching only shows that pretty much everyone else has the same problem. Nobody has a solution for this issue?

-- This may not be quite the answer for everyone but I struggled too much not to share. I was installing the free version of BlueSpice MediaWiki 3 and have tripped over the configuration of Parsoid (for the Visual Editor feature) like every man on this planet apparently did. I was having 404 errors when opening the VE. The solution I found was to to set  to   in the parsoid config, going against what the BlueSpice documentation was saying. In my case the wiki is only accessed internally so I think it's okay.

Parsoid doesn't start, and get error message 'Cannot read property 'uri' of undefined'
When I try to start parsoid, it is doesn't start, and give error message to parsoid.log:

/usr/lib/parsoid/src/lib/mediawiki.ParsoidConfig.js:386 this.reverseMwApiMap.set(url.parse(apiConf.uri).host, prefix); ^

TypeError: Cannot read property 'uri' of undefined at ParsoidConfig.setInterwiki.ParsoidConfig.setMwApi (/usr/lib/parsoid/src/lib/mediawiki.$   at Object.exports.setup (/etc/mediawiki/parsoid/settings.js:21:16)    at new ParsoidConfig (/usr/lib/parsoid/src/lib/mediawiki.ParsoidConfig.js:99:17)    at Object. (/usr/lib/parsoid/src/api/server.js:83:21)    at Module._compile (module.js:410:26)    at Object.Module._extensions..js (module.js:417:10)    at Module.load (module.js:344:32)    at Function.Module._load (module.js:301:12)    at Function.Module.runMain (module.js:442:10)    at startup (node.js:136:18) How to solve this issue?


 * For me, this went away when I used the old function for setting the URI (parsoidConfig.setInterwiki) instead of the new one. Then I moved on to the "Parsoid Did not find page revisions for *" error above... Cd1207 (talk) 07:23, 22 July 2016 (UTC)

http://172.0.0.1/load.php?debug=false&lang=en&modules=ext.visualEditor.desktopArticleTarget.init%7Cext.visualEditor.supportCheck%2Ctrack%2Cve%7Cjquery.accessKeyLabel%2CbyteLength%2Cclient%2Ccookie%2CtabIndex%2Cthrottle-debounce%7Cmediawiki.RegExp%2CTitle%2CUri%2Capi%2Ccldr%2Ccookie%2CjqueryMsg%2Clanguage%2Cnotify%2Ctemplate%2Cuser%2Cutil%7Cmediawiki.action.view.postEdit%7Cmediawiki.api.options%2Cuser%7Cmediawiki.language.data%2Cinit%7Cmediawiki.libs.pluralruleparser%7Cmediawiki.page.startup%7Cmediawiki.template.regexp%7Cskins.vector.js%7Cuser.defaults&skin=vector&version=3a6ea11fc844

Parsoid Installation Issue
npm WARN deprecated circular-json@0.3.1: CircularJSON is in maintenance only, flatted is its successor. npm WARN deprecated formidable@1.0.17: Old versions of Formidable are not compatible with the current Node.js; Upgrade to 1.2.0 or later npm WARN deprecated is-my-json-valid@2.16.0: catastrophic backtracking in regexes could potentially lead to REDOS attack, upgrade to 2.17.2 as soon as possible npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade npm WARN deprecated kad-fs@0.0.4: Please upgrade to @kadenceproject/kadence - See https://kadence.github.io npm WARN deprecated kad-memstore@0.0.1: Please upgrade to @kadenceproject/kadence - See https://kadence.github.io npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated nsp@2.8.1: The Node Security Platform service is shutting down 9/30 - https://blog.npmjs.org/post/175511531085/the-node-security-platform-service-is-shutting npm WARN deprecated joi@6.10.1: This version is no longer maintained. Please upgrade to the latest version. npm WARN deprecated wreck@6.3.0: This version is no longer maintained. Please upgrade to the latest version. npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead. npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN system32 No description npm WARN system32 No repository field. npm WARN system32 No license field.

Problems 147.202.207.18 is having...
This doesn't work for me: " curl http://your-mediawiki-server/api.php ". Instead, I have to do: " curl http://your-mediawiki-server:8142/mediawiki/api.php ". Is that expected, are my settings wrong, or what?

What should I do if the Parsoid folder doesn't exist in the mediawiki folder? Is "Parsoid/js/api/localsettings.js" obsolete now? I don't see any js folder in the Parsoid folder...

Does this log tell Parsoid is Working?
\\\\\\\\\\\\\\\\ version : MW 1.33.0 ubuntu 16 server : Amazon WebService EC2 Ubuntu \\\\\\\\\\\\\\\\\\\

Entered "systemctl status parsoid" and see logs. Can you tell me Parsoid is working? cause I can't use VisualEditor, showing message of "Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 7) Couldn't connect to server. Would you like to retry?".

I did "curl -L http://localhost:8142/localhost/v3/page/html/Main_Page/" but "connection refused" showed up.

Thanks

[Systemctl Ststus Parsoid] parsoid.service - LSB: Web service converting HTML+RDFa to MediaWiki wikitext and back Loaded: loaded (/etc/init.d/parsoid; bad; vendor preset: enabled) Active: active (running) since Sun 2019-08-25 10:44:51 UTC; 24min ago Docs: man:systemd-sysv-generator(8) CGroup: /system.slice/parsoid.service ├─11379 /bin/sh -c /usr/bin/nodejs /usr/lib/parsoid/src/bin/server.js -c /etc/mediawiki/parsoid/config.yaml >> /var/log/parsoid/parsoid.log 2>&1 └─11381 /usr/bin/nodejs /usr/lib/parsoid/src/bin/server.js -c /etc/mediawiki/parsoid/config.yaml

Aug 25 10:44:46 ip-172-31-41-225 systemd[1]: Stopped LSB: Web service converting HTML+RDFa to MediaWiki wikitext and back. Aug 25 10:44:46 ip-172-31-41-225 systemd[1]: Starting LSB: Web service converting HTML+RDFa to MediaWiki wikitext and back... Aug 25 10:44:46 ip-172-31-41-225 parsoid[11367]: Started Parsoid server on port 8142 Aug 25 10:44:51 ip-172-31-41-225 systemd[1]: Started LSB: Web service converting HTML+RDFa to MediaWiki wikitext and back.

[/var/log/parsoid/parsoid.log]
 * Here is parsoid log. there is fatal error...

{"name":"parsoid","hostname":"ip-172-31-41-225","pid":11381,"level":30,"levelPath":"info/service-runner","msg":"master(11381) initializing 1 workers","time":"2019-08-25T10:44:46.808Z","v":$ {"name":"parsoid","hostname":"ip-172-31-41-225","pid":11390,"level":60,"moduleName":"../src/lib/index.js","levelPath":"fatal/service-runner/worker","msg":"Unexpected token {","time":"2019-$ {"name":"parsoid","hostname":"ip-172-31-41-225","pid":11381,"level":40,"message":"first worker died during startup, continue startup","worker_pid":11390,"exit_code":1,"startup_attempt":1,"$