Talk:MediaWiki 1.35

About this board

Error contacting the Parsoid/RESTBase server: (curl error: 7) Couldn't connect to server

Sccotty (talkcontribs)

Getting this error when trying to use the visual editor. Can create a new page fine but cannot save them (same error).

MediaWiki 1.35.1
PHP 7.3.25 (apache2handler)
MariaDB 10.3.27-MariaDB
ICU 63.1

Any help is appreciated.

Jaideraf (talkcontribs)
2003:C0:4F1B:CB40:78F1:237A:6989:B7B9 (talkcontribs)

Meine Lösung:

setsebool -P httpd_can_network_relay 1

Vick Dolce (talkcontribs)

sudo setenforce 0

worked for me! SELINUX causing problems.

Xiangpeng.zhang (talkcontribs)


this section didn't provide a really solution, just an explication. (talkcontribs)

Try to add next line to your LocalSettings.php

$wgCanonicalServer = "http:||localhost:80"; (talkcontribs)

|| replace with //

Reply to "Error contacting the Parsoid/RESTBase server: (curl error: 7) Couldn't connect to server"

Given the number of Support Desk topics about character-encoding problems should the Release Notes for 1.35 include a warning?

Peculiar Investor (talkcontribs)

There are a number of topics in the Support Desk that indicate that installing/upgrading to MediaWiki 1.35.x can render a wiki unusable. See Index.php displayed with wrong characters on Project:Support desk ( and Has MW 1.35 changed when/how the HTTP header, Content-Length, are used? on Project:Support desk ( as two examples, there are more.

This is being tracked as ⚓ T235554 MediaWiki::outputResponsePayload seemingly causes net::ERR_HTTP2_PROTOCOL_ERROR 200 and compression issues in 1.35 ( and a few others.

Should the Release Notes page include a warning about these problems so that anyone upgrading is aware of the problem?

Jdforrester (WMF) (talkcontribs)

I believe that this should be finally fixed as of 1.35.2.

Reply to "Given the number of Support Desk topics about character-encoding problems should the Release Notes for 1.35 include a warning?"

Possible fix for Parsoid PHP curl error: 7 in Docker

Octfx (talkcontribs)

I noticed that if the service name of the MediaWiki Container is the same as the domain e.g.:

    image: mediawiki:1.35.0


VisualEditor will fail with either 404 or curl error 7

After suffixing or prefixing the service and container_name with an arbitrary string like:

    image: mediawiki:1.35.0
    container_name: my-wiki.com_mw


VisualEditor successfully connected to Parsoid PHP.

The issue is, that containers running in compose automatically resolve to their name to the local ip of the container. In this case it tries to connect to the domain using the name (as intended) but then getting the local ip back which causes the error (at least when running https)

Alistair3149 (talkcontribs)
Reply to "Possible fix for Parsoid PHP curl error: 7 in Docker"
Nicole Sharp (talkcontribs)

Regarding the PHP 8 incompatibility notice, I am using MediaWiki 1.35.1 LTS with PHP 8.0.1 and haven't had any problems yet. Nicole Sharp (talk) 04:23, 28 February 2021 (UTC)

Reply to "PHP 8"


Summary by Ciencia Al Poder (talkcontribs)

After the upgrade to MediaWiki 1.35 we run into annoying errors on some (Special-)Pages with Edge, Chrome and Internet Explorer.

Blank page, nothing worked, not one byte was loaded. The console in the webdeveloper window shows error net::ERR_HTTP2_PROTOCOL_ERROR 200

First thought was, that we had issues with the SSL certificate. But it wasn't.

Then we found

$wgDisableOutputCompression  = true;

in the LocalSettings solved the problem.

TiltedCerebellum (talkcontribs)

It solved the problem for us too, but only on 1.35.0, after that per the phab task there is not a resolution as of yet for folks that encountered this issue previously. Setting $wgDisableOutputCompression  = true; in 1.35.1 only resulted in random characters being displayed for Chrome and iOS Safari (on our setup). For us the 1.35.0 problem happened on FF, Chrome and iOS Safari (Edge always being fine, edge still being fine on 1.35.1, where FF is now also fine on 1.35.1, but Chrome and iOS were messed up, strangely got Chrome working by accident by toggling on and off random caching options... then putting it back to exactly how I had it before!--inexplicable, and iOS Safari still broken with "cannot parse response" error). --We're using Dreamhost VPS. Trying to decide if we should move our prod site to 1.35.0 with $wgDisableOutputCompression  = true; so we can have VE, or if other issues might emerge... for now staying on our current version.

Reply to "net::ERR_HTTP2_PROTOCOL_ERROR 200"

MediaWiki 1.35 internal error - Installing some PHP extensions is required.

WillC93 (talkcontribs)

I have just installed MediaWiki and am getting the below error. I do not know what I need to do. I have called my host site, HostGator, and they did not know what to do. I have tried installing MediaWiki using the installer in my cPanel. I have also extracted the MediaWiki tar file and both result in the same internal error.

I do not know how to install or add the below extensions. The links do not provide any downloads either.

I am using HostGator as my host site. I have updated my PHP to version 7.3.26. The domain is an addon domain.

I have been trying to research this issue for a while now and I cannot find anything online to help.

MediaWiki 1.35 internal error

Installing some PHP extensions is required.

Required components

You are missing a required extension to PHP that MediaWiki requires to run. Please install:

  • mbstring (more information)
  • xml (more information)
  • ctype (more information)
  • json (more information)
  • iconv (more information)
  • fileinfo (more information)
Reply to "MediaWiki 1.35 internal error - Installing some PHP extensions is required."

MediaWiki 1.35.1 release announcement, where is the Extensions Security Release Supplement?

Peculiar Investor (talkcontribs)
Kghbln (talkcontribs)

I personally would love to see these two announcements sent the same day to allow people touch their wiki at the same time. Anyhow, this announcement is still in the pipeline. If you have the Widgets extension running - you can update now. All the rest will be disclosed in the upcoming announcement.

Peculiar Investor (talkcontribs)

Thanks. Based on the first announcement and the fact that security fixes were publicly disclosed I would have thought they would come of close together for exactly the reason you mention. That would have been helpful. I had already found the information about the Widgets extension.

Reply to "MediaWiki 1.35.1 release announcement, where is the Extensions Security Release Supplement?"

Visual editor can't connect to server

Summary by Hcadby

Fixed issue

Hcadby (talkcontribs)

I have installed the new mediawiki 1.35 and some extensions, during setup I installed Visual Editor however when trying to edit a page with visual editor i get the following error:

Error contacting the Parsoid/RESTBase server: (curl error: 7) Couldn't connect to server

Any help would be appreciated.

My mediawiki install.

Product Version
MediaWiki 1.35.0
PHP 7.4.12 (fpm-fcgi)
MariaDB 10.3.17-MariaDB
ICU 65.1 (talkcontribs)

me too, the same error, does someone has a solution?

Bluedreamer1 (talkcontribs)

Also getting this error with the latest docker image of mediawiki.

Bluedreamer1 (talkcontribs)

I found out how to do this, the key part is very much missing from the documentation as it says "no configuration"

Add this to LocalSettings.php to use default 1.35 Parsoid code wfLoadExtension( 'Parsoid', 'vendor/wikimedia/parsoid/extension.json' );

Hcadby (talkcontribs)

I have tried this but still getting the same result

Bluedreamer1 (talkcontribs)

So I did various other things.

I added this to my php.ini

curl.cainfo ="/etc/cacert.pem"

I download the file from curl's site at

I tried manually curling my site's api page

curl --cacert /etc/cacert.pem https://<my wiki site>/api.php

That still gave me an error

curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here:

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

So I added my SSL pem cert to the end of the file /etc/cacert.pem

Then I added this to my LocalSettings.php

wfLoadExtension( 'Parsoid', '/home/un9/mediawiki/vendor/wikimedia/parsoid/extension.json' );
$wgGroupPermissions['user']['writeapi'] = true;

That's what I did and now it works, not sure if every step is necessary.

PHP 7.3.19 is too new for CentOS 7

Noloader (talkcontribs)

Hi Everyone,

I'm tossing this out there since it is a blocker for us. We have a CentOS 7 VM with Red Hat Software Collections (SCL) enabled. We are currently on Mediawiki 1.34, and we cannot migrate to Mediawiki 1.35.

The problem is, Red Hat's SCL only provides PHP 7.3.11. The platform does not offer a PHP that meets minimum requirements for Mediawiki 1.35.

If Mediawiki downgrades the PHP requirements then we can perform the migration.

For completeness, CentOS 7 offers versions of PHP 7.0, 7.1, 7.2 and 7.3. There is no version of 7.4 available.

Also see CentOS Issue 0017826: CentOS 7 with SCL enabled only provides PHP 7.3.11.

Reply to "PHP 7.3.19 is too new for CentOS 7" (talkcontribs)

I am trying to install on xampp this new version but before setting up the wiki it gives me "internal error Installing some external dependencies (e.g. via composer) is required."

Can someone fix the version for xampp please?

Noloader (talkcontribs)

> Installing some external dependencies (e.g. via composer) is required.

I don't know about XAMPP specifically. However, on Linux, here is the procedure we use to update Mediawiki and components via Composer: wiki-upgrade.txt. Steps (5), (6), (7) and (9) are the important ones for Composer.

Reply to "Help"