Topic on Extension talk:VisualEditor

I do get the error "Error contacting the Parsoid-/RESTBase-Server (HTTP 403)", as soon as I want to edit with Visual Editor. As long as I work with the source code, everythings fine.

I recently updated from MediaWiki 1.34 to MW 1.35, my wiki is not private and i run the website via cPanel/NameCheap. As I could not find any solution to my problem in the past week, i am now hoping to find help in this forum.

As I am a noob to wikimedia, i installed no extensions (except VisualEditor via MW 1.35) and the only additions i wrote into my localsettings.php are the following:

wfLoadExtension( 'VisualEditor' );

$wgGroupPermissions['user']['writeapi'] = true;

$wgVisualEditorParsoidAutoConfig = true;

These changes are the result of my former investigation. Without these VE is not shown as an option to edit my wiki.

Furthermore, the Insert-options i get by editing via VisualEditor are only for tabulars, images and comments. Options for inserting formulae or graphs are missing. As i want to insert mathematical equations, please tell me how to get this option into my VE.

I would appreciate any kind of support. Thanks in advance!

Check Topic:Vv9zl5e9gre77rgq

I had $wgGroupPermissions['*']['writeapi'] set to false and got the same error message ("Error contacting the Parsoid/RESTBase server (HTTP 403)").

Therefore, I suggest that you include the following: $wgGroupPermissions['*']['writeapi'] = true;

This has no change on the issue for me.

Where did you change that setting???

Where in cpanel?

I am putting this out more widely as an answer to this issue as I had a LOT of trouble resolving it. Basically, on some (cPanel) hosted sites the Parsoid/RESTBase Server API communications are blocked by several ModSecurity rules. I had to contact my hosting tech support and get them to whitelist rules for my wiki one or two at a time, while generating new ModSecurity rule errors by attempting to edit using VisualEditor until we had found all the rules which were resulting in this error. NB: At some point during this process a few pages might start working - not throwing a 403 - but then test a few more pages as they might still trigger ModSecurity.

To answer the last two questions above - you have to add that code as new lines in your wiki's LocalSettings.php file

I've got the same problem here.

In my case the problem disappeared, when I removed the .htaccess file from the root folder of the server, which just allowed access from a specific IP address.