Topic on Extension talk:VisualEditor

I have been browsing all reaches of the internet and just cannot seem to find anyone else with this same error code. (of if i do its not entirely related, such as they can create but not edit, etc). This is a clean installation and i have spend the better part of the last couple of days troubleshooting this before posing here.

---

[environment]

CentOS 7 64x

Apache 2.4.6

PHP 7.0.33

MySQL 5.7.25

MediaWiki 1.32.1

Visual Editor REL1_31-6854 (VE 1.32 was throwing an exception for incompatibility and demanding my to update mw to v1.33...)

I referred to this resource to preform the VE and Parsoid install. https://www.howtoforge.com/tutorial/how-to-install-visualeditor-for-mediawiki-on-centos-7/

---

So here is where I'm at. MediaWiki is currently functioning as intended, as well is the parsoid instance which loads at mydomain:8000.

- When i try to create a wiki page with the visual editor, it will open and allow me to use the editor but when i try and save i get error "Something went wrong - (curl error: 6) Couldn't resolve host name."

- When i attempt to edit any page with the virtual editor i get error "Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 6)"

The actual call is "http://wiki.domain.local/api.php?action=visualeditor&format=json&paction=parse&page=Main_Page&uselang=en" Which is correct.

Access logs are recorded but nothing is reported in the httpd error log.

Doing some trouble shooting, i ensured every file is chown/chgrp to apache, all /www -R files are set to 644 and directories are 755.

I have disabled SElinux, ensured all config paths are correct, etc. I'm truly stumped...

---

Parsoid: Config.yaml https://pastebin.com/JVnv7iGC

Parsoid: localsettings.js https://pastebin.com/EuHjZV40

mediawiki: LocalSettings.php https://pastebin.com/EStrUNmn

EDIT:

I'll leave this in the event anyone else stumbles across this.

Curl error 6 was caused in my case by resolv.conf getting overwritten on startup. Had to disable dhcp script as I'm statically configured anyway.
Sometimes its not always a complicated solution to a cryptic problem.

For those that need it:

My issue was the parsoid conf wasn't correctly finding my wiki page.

To see if it's set correctly, use:

curl {your full parsoid.yaml url}

That should dump out the entire yourwiki/api.php page. If not, then the parsoid config.yaml file isn't using the right address.

As an additional test, you can see if parsoid is running by visiting the yourwiki:8142 (or 8000 if non-debian) address. It should say something about "Welcome to the Parsoid web service".

Don't forget to update the LocalSettings.php with the correct URL.