Page MenuHomePhabricator

VisualEditor cURL Error: 7, Debian 9.11
Closed, DeclinedPublic


Very similar to an issue that was already closed, but despite following the steps, I still get a cURL 7 error. Relatively new to MediaWiki
Similar to T207504, but all attempts to follow it and other tickets were unsuccessful at fixing the issue.

Debian 9.11
MediaWiki 1.31.0
PHP 7.0.33-0+deb9u1
Parsoid 0.10.0

Server is working on an intranet in an office and the regular HTML editing works fine. We can cue up VE on a new page since there's nothing for it to parse, but going to save it returns the cURL error.

I think the issue is either the port I am using or a firewall setting. I am attempting to do 8142 (recommended for Debian), and every time I use cURL on http:// [[IPAddress or localhost]] / [[wiki name]] / api.php I get the HTML output. But when I do http:// [[IPAddress or localhost]]:8142 / [[wiki name]] / api.php, I get "Failed to connect to [[IP/localhost]] port 8142: Connection refused. netstat doesn't list the port either.

Any help is appreciated. I do not mind redoing steps I've already tried. Thanks!



  • # This is the only required parameter,
    1. the URL of you MediaWiki API endpoint uri: 'http:// [[IP Address]] / [[wiki-name]] / api.php'
  1. domain: 'localhost' #optional

$wgVirtualRestConfig['modules']['parsoid'] = array(

// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => 'http:// [[IPAddress]] :8142' ,
// Parsoid "domain", see below (optional)
// 'domain' => 'localhost' ,

Event Timeline

It is possible to it is the same as this thread: use nodejs >= 6.x (in Debian Stretch backports) instead of 4.x (default for Debian Stretch).

If confirmed, I’m afraid there will be no new version of the package T212555.

@Bumbliciousness: any update? If you do not intend to further debug it, please close the issue.

Aklapper changed the task status from Open to Stalled.Apr 5 2021, 11:20 AM

Unfortunately closing this Phabricator task as no further information has been provided.

@Bumbliciousness: After you have provided the information asked for and if this still happens, please set the status of this task back to "Open" via the Add Action...Change Status dropdown. Thanks!