Error retrieving modules directory data (ProcessWireUpgradeCheck)

[Mikie]

Anyone know what would cause this? Is it a failing endpoint somewhere, or a misconfiguration in a local module I am working on.

Only being thrown on one install.

[Macrura]

I believe the directory itself is the issue, it is "broken" at the moment. Broken because it forwards HTTP to HTTPS and this causes the check to fail, because the non-HTTPS url is hardcoded in the config file.

Edit: So this is happening on all sites since yesterday. I tracked down the issue to the non-SSL service URL in the wire/config.php file.

You can fix it by changing the $config->moduelServiceURL in your site/config.php like this:

$config->moduleServiceURL = 'https://modules.processwire.com/export-json/';

 

[teppo]

Opened an issue for this here: https://github.com/processwire/processwire-issues/issues/1083. It's great that http to https redirects are finally in place (assuming that this was intentional), but it appears that it's going to be an issue for the core.

[Mikie]

Cool thanks guys. Now that I think about it the other install I tested on probably didn't have debug on as it was a live site.

[teppo]

This is fixed: in the latest dev version wire/config.php points to the HTTPS URL of the modules directory, and the modules directory also again accepts HTTP connections (which should guarantee backwards compatibility).

[gornycreative]

Hate to bring it up again, but for some reason I am getting really spotty results from this.

Looking at the code I get spotty results - sometimes it loads but most of the time I get no module data - just processwire dev and core.

Anyone else having issues with connecting?

Running this:

$mod = $this->modules->get('ProcessWireUpgradeCheck');
db($mod->getModuleVersions(false, true));

in the tracy console gives me null for the getModuleVersions function.

When I try the $url that it generates manually, I get a result no problem.

I have session DB enabled. Perhaps a timeout someplace?

 

[gornycreative]

Altering the timeout from 4.5 to 30 temporarily allowed the results to load.

Not sure why that should take longer than 4.5 seconds to pull, but it's a simple enough fix I guess.