Page MenuHomePhabricator

Manually loading exit node list on new install fails
Closed, DuplicatePublic

Description

Version: 1.30.

Fresh install, edited LocalSettings.php and loaded the extension along with the directive, "$wgTorLoadNodes = false;" as an optional setup configuration as suggested by the extension's home page. Running the loadExitNodes.php file manually (as server root user) fails with the message "Could not load exit nodes." (exit code: 1).

Removing the line "$wgTorLoadNodes = false;" and re-running the file loadExitNodes.php then succeeds, printing: "Successfully loaded 921 exit nodes." (exit code: 0).

Reinstating the line "$wgTorLoadNodes = false;" and re-running the file loadExitNodes.php then "succeeds", but this may only be because a cached list now exits (the printed message is the same as before: "Successfully loaded 921 exit nodes.").

Issues:

  1. The directive "$wgTorLoadNodes = false;" in LocalSettings.php seems to break the operation of loadExitNodes.php.
  2. The error message is poor and adds no information on what went wrong.
  3. The documented suggestion on loading the exit nodes manually via cron/systemd seems not to work and may require updating if additional configuration is required to run correctly.

Ancillary issues:

  • The documentation on the extension's home page is poor. There is no indication of which parameters need to be set, if any, or whether the listed parameters are the defaults. Some of the descriptions are vague; for example: "An array of IP addresses that the wiki server uses. Only exit nodes allowed to connect to these IPs will be returned in the internal list." What is the internal list? This phrase is a nonce. Does the author mean the list of exit nodes? If so, then nomenclature is not consistent.