ttttim

Error shown on upgrade page

Recommended Posts

Hi,

I want to upgrade my 2.6 processwire to the new 2.71 but when i go to the upgrade page i get the following error message.

 Error loading GitHub branches https://api.github.com/repos/ryancramerdesign/Processwire/branches#0...'>https://api.github.com/repos/ryancramerdesign/Processwire/branches#0... 2 mins 
Error loading GitHub branches https://api.github.com/repos/ryancramerdesign/Processwire/branches#0 /mnt/webs/a1/32/54491832/htdocs/processwire/site/modules/ProcessWireUpgrade/ProcessWireUpgradeCheck.module(129): ProcessWireUpgradeCheck->getCoreBranches() #1 /mnt/webs/a1/32/54491832/htdocs/processwire/site/modules/ProcessWireUpgrade/ProcessWireUpgrade.module(164): ProcessWireUpgradeCheck->getVersions() #2 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/ProcessController.php(213): ProcessWireUpgrade->execute() #3 [internal function]: ProcessController->___execute() #4 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(387): call_user_func_array(Array, Array) #5 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(325): Wire->runHooks('execute', Array) #6 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/admin.php(93): Wire->__call('execute', Array) #7 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/admin.php(93): ProcessController->execute() #8 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/modules/AdminTheme/AdminThemeDefault/controller.php(13): require('/mnt/webs/a1/32...') #9 /mnt/webs/a1/32/54491832/htdocs/processwire/site/templates/admin.php(15): require('/mnt/webs/a1/32...') #10 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/TemplateFile.php(169): require('/mnt/webs/a1/32...') #11 [internal function]: TemplateFile->___render() #12 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(387): call_user_func_array(Array, Array) #13 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(325): Wire->runHooks('render', Array) #14 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/modules/PageRender.module(385): Wire->__call('render', Array) #15 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/modules/PageRender.module(385): TemplateFile->render() #16 [internal function]: PageRender->___renderPage(Object(HookEvent)) #17 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(387): call_user_func_array(Array, Array) #18 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(325): Wire->runHooks('renderPage', Array) #19 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(409): Wire->__call('renderPage', Array) #20 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(409): PageRender->renderPage(Object(HookEvent)) #21 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(325): Wire->runHooks('render', Array) #22 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/modules/Process/ProcessPageView.module(187): Wire->__call('render', Array) #23 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/modules/Process/ProcessPageView.module(187): Page->render() #24 [internal function]: ProcessPageView->___execute(true) #25 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(387): call_user_func_array(Array, Array) #26 /mnt/webs/a1/32/54491832/htdocs/processwire/wire/core/Wire.php(325): Wire->runHooks('execute', Array) #27 /mnt/webs/a1/32/54491832/htdocs/processwire/index.php(241): Wire->__call('execute', Array) #28 /mnt/webs/a1/32/54491832/htdocs/processwire/index.php(241): ProcessPageView->execute(true) #29 {main}

Any ideas how to fix this problem? I know I can upgrade manually but i'd like to do it thought the admin area. 

Share this post


Link to post
Share on other sites

Yes, i've had the problem for a while now. If I go directly to the link it works fine. Could it be a hosting problem?

Share this post


Link to post
Share on other sites

I'm just having the same problem.

I've just upgraded a website from 2.5.3 to 2.7.1.

But now, when going to Administration > Configuration > Upgrades, I have "The process returned no content." and "Error loading GitHub branches https://api.github.com/repos/ryancramerdesign/Processwire/branches".

I'll check again later.

If I go to Administration > Modules > Upgrades Checker and check for updates, I have "Error reported by web service: Unable to find that module".

If I do the same with "Upgrades", I don't have any error message.

Edit: I've uninstalled both from the admin (Upgrades and Upgrades Checker) and then I've uploaded again the module (ProcessWireUpgrade) via FTP and installed them again.

Now I can see the list of upgrades/updates available.

But I still have the message "Error reported by web service: Unable to find that module", if I go to Administration > Modules > Upgrades Checker and check for updates again.

Share this post


Link to post
Share on other sites

Getting the same error while trying to upgrade from 2.6.1 to 2.7.1. Reinstall Upgrade Modules doesn't solve it.

Share this post


Link to post
Share on other sites

DaveP, is user_agent set in your php.ini? Github's api rejects requests that don't have a user-agent header.

Share this post


Link to post
Share on other sites

I realise this is a (very) late reply, but this problem just won't go away. In reply to @BitPoet user_agent isn't set in php.ini. I was under the impression that the request from the PW backend to GitHub set its own user agent. Can anyone confirm this one way or another? I may be able to upload a custom php.ini if there is a chance it will fix this.

Share this post


Link to post
Share on other sites

Done some more digging on this.

Tried adding 

ini_set("user_agent", "PHP " . PHP_VERSION);

to config.php. Didn't work.

Found https://github.com/BitPoet/ProcessWireUpgrade/blob/dev-useragentfix/ProcessWireUpgrade.module and added 

$ua = ini_get("user_agent");
if(empty($ua)) ini_set("user_agent", "PHP " . PHP_VERSION);

(Lines 101 & 102) to ProcessWireUpgrade.module, per @BitPoet's fork. Didn't work.

I also added, as a test,

<?php
    ini_set('user_agent', 'ABC');
    echo ini_get('user_agent');
?>

to one of my template files and it did echo 'ABC', so ini_set() is working.

So it isn't user_agent that is causing the problem.

Share this post


Link to post
Share on other sites
4 hours ago, DaveP said:

So it isn't user_agent that is causing the problem.

Does your hosting allow outgoing http connections? Perhaps try it with a short, PW-independent php script that does a file_get_contents on a publicly reachable url.

Share this post


Link to post
Share on other sites

The error only shows for PW repos (see screenshot). If there were a general problem, then surely the other repos would be unavailable too.

Screen Shot 2017-07-18 at 18.00.46.png

Share this post


Link to post
Share on other sites

@DaveP, the GitHub API can respond with a 403 in a number of different situations, as described here: https://developer.github.com/v3/

But there should be some explanation in the "message" value of the returned JSON. You could put this in a template and see what you get back:

$http = new WireHttp();
$http->setHeader('User-Agent', 'ProcessWireUpgrade');
$json = $http->get('https://api.github.com/repos/processwire/processwire/branches');
print_r($json);

 

Share this post


Link to post
Share on other sites

@Robin S Thanks for your reply.

I tried your snippet, but got nothing back. (Absolutely zilch - I even wrapped any output in asterisks to make sure something was happening.) Then I added

echo $http->getError();

and guess what I got?

Quote

403 Forbidden: 2: fopen(https://api.github.com/repos/processwire/processwire/branches): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden , Forbidden

:huh:

Thanks a lot, Github.

Share this post


Link to post
Share on other sites
1 hour ago, DaveP said:

Thanks a lot, Github.

I think your result means that the problem isn't with GitHub - the request is not being sent successfully. Perhaps a firewall or some other security restriction on your server is blocking it.

Are you able to use fopen() on any remote files? If you put this in your template...

$handle = fopen('https://www.google.com/', 'r');
bd($handle, 'handle');

...Tracy should show a stream resource in the dump.

2017-07-19_212900.png.66ee3feff70d67f8039fdfa950d24377.png

  • Like 1

Share this post


Link to post
Share on other sites

Ok, I got that. Doesn't look much different to yours, or am I missing something?

Screen Shot 2017-07-19 at 11.11.25.png

Share this post


Link to post
Share on other sites

Currently I have no issues with Upgrades module connecting to GitHub either. In the past once I had issues with it too, but at that time GitHub was brought down by DoS attack or something like that.

Share this post


Link to post
Share on other sites
12 hours ago, DaveP said:

Doesn't look much different to yours, or am I missing something?

Looks normal, so must something particular about the GitHub URL or the way that it is accessed that causes it to be blocked.

It may be something that only your host can advise you on. You could try and set up a basic case to serve as a demonstration for them. ProcessWireUpgradeCheck.module basically does what I showed in a post above. If you take a look into WireHttp.php here and here you should be able to extract some of that code to create a basic test case in a PHP file that demonstrates the problem.

For reference, here is what you should see when executing the code I posted above:

[{"name":"dev","commit":{"sha":"651e8bd20c1f7bf13c08a2098f862adf82700a28","url":"https://api.github.com/repos/processwire/processwire/commits/651e8bd20c1f7bf13c08a2098f862adf82700a28"}},{"name":"master","commit":{"sha":"57b297fd1d828961b20ef29782012f75957d6886","url":"https://api.github.com/repos/processwire/processwire/commits/57b297fd1d828961b20ef29782012f75957d6886"}}]

 

Share this post


Link to post
Share on other sites

I'd just read @szabesz & @Robin S's replies, and went to reload the offending page, and got this...

59706cffe8905_ScreenShot2017-07-20at09_36_52.thumb.png.260fe15c20e5464274db290c70bdabb5.png

Yep. it worked.

But only the once. Now it's back to the same state as my post above.

Could it be some cache-related weirdness? If it works once it should work every time.

Share this post


Link to post
Share on other sites
8 minutes ago, DaveP said:

Could it be some cache-related weirdness? If it works once it should work every time.

I am wild guessing here but do you have "Check for upgrades on superuser login?" turned on? The Upgrades module utilizes loginHook and maybe your other 3rd party module too and there might be some conflict there.

Share this post


Link to post
Share on other sites
1 hour ago, szabesz said:

do you have "Check for upgrades on superuser login?" turned on?

It was set to 'No', but I've changed it to 'Yes'. Now I get the error on login as well.

Having said that, the site (it is an intranet so every user has to be logged in) uses LoginPersist, so I have to log out intentionally in order to need to log in.

  • Like 1

Share this post


Link to post
Share on other sites

Further update on this - earlier today was still getting 403. However, we just relocated offices (this is a debugging step I don't recommend), and with a new IP, no 403. Could GitHub be blocking IPs for some reason?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By BitPoet
      MediaLibrary
      Update: MediaLibrary can now be found in the official module list.
      Out of necessity, I've started to implement a simple media library module.
      The basic mechanism is that it adds a MediaLibrary template with file and image fields. Pages of this type can be added anywhere in the page tree.
      The link and image pickers in CKEditor are extended to allow quick selection of library pages from dropdowns. In the link picker this happens in the MediaLibrary tab, where you can also see a preview of the selected image. In the image picker, simply select a library from the dropdown at the top, everything else is handled by standard functionality.
      I've put the code onto github. This module is compatible with ProcessWire 3.
      Steps to usage:
      Download the module's zip from github (switch to the pw3 branche beforehand if you want to test on PW 3.x) and unpack it into site/modules Click "Modules" -> "Refresh" in the admin Click "Install" for MediaLibrary For testing, create a page with the MediaLibrary template under home (give it an expressive title like 'Global Media') and add some images and files Edit a differnt page with a CKEditor field and add a link and an image to see the MediaLibrary features in action (see the screencap for details) Optionally, go into the module settings for MediaLibrary Note: this module is far from being as elaborate as Kongondo's Media Manager (and doesn't plan to be). If you need a feature-rich solution for integrated media management, give it a look.
      Feel free to change the settings for MediaFiles and MediaImages fields, just keep the type as multiple.
      There are some not-so-pretty hacks for creating and inserting the correct markup, which could probably be changed to use standard input fields, though I'm a bit at a loss right now how to get it to work. I've also still got to take a look at error handling before I can call it fit for production. All feedback and pointers are appreciated (that's also why I post this in the development section).

      Edit 09.03.2016 / version 0.0.4: there's now also a "Media" admin page with a shortcut to quickly add a new library.

      Edit 01.05.2016:
      Version 0.0.8:
      - The module now supports nested media libraries (all descendants of eligible media libraries are also selectable in link/image picker).
      - There's a MediaLibrary::getPageMediaLibraries method you can hook after to modify the array of available libraries.
      - You can switch between (default) select dropdowns or radio boxes in the module configuration of MediaLIbrary to choose libraries.
      Edit 10.10.2018:
      Version 0.1.3:
      - Dropped compatibility for ProcessWire legacy versions by adding namespaces
      - Allow deletion of libraries from the Media overview admin page
      - Added an option to hide media libraries from the page tree (optionally also for superusers)
    • By Robin S
      This module corrects a few things that I find awkward about the "Add New Template" workflow in the PW admin. I opened a wishlist topic a while back because it would good to resolve some of these things in the core, but this module is a stopgap for now.
      Originally I was going to share these as a few standalone hooks, but decided to bundle them together in a configurable module instead.
      Add Template Enhancements
      A module for ProcessWire CMS/CMF. Adds some efficiency enhancements when adding or cloning templates via admin.

      Features
      Derive label from name when new template added: if you like to give each of your templates a label then this feature can save some time. The label can be added automatically when templates are added in admin, in admin/API, or not at all. There are options for underscore/hyphen replacement and capitalisation of the label. Edit template after add: when adding only a single template, the template is automatically opened for editing after it is added. Copy field contexts when cloning: this copies the field contexts (a.k.a. overrides such as column width, label and description) from the source template to the new template when using the "Duplicate/clone this template?" feature on the Advanced tab. Copy field contexts when duplicating fields: this copies the field contexts if you select the "Duplicate fields used by another template" option when adding a new template. Usage
      Install the Add Template Enhancements module.
      Configure the module settings according to what suits you.
       
      https://github.com/Toutouwai/AddTemplateEnhancements
      https://modules.processwire.com/modules/add-template-enhancements/
    • By Mike Rockett
      As I mentioned in this issue, I've create a new textformatter for ParsedownExtraPlugin, which adds some oomph to your markdown.
      Repo: Parsedown Extra Plugin
      Unlike the built-in textformatter for Parsedown and Parsedown Extra, this should be used when you want to use Extra with additional configuration/customisation.
      Some examples:
      ### Test {.heading} - A [external link](https://google.com/){.google} with `google` as a class that opens in a new tab if the config property is set. - [Another link](/page){target=_blank} that opens in a new tab even though it isn't external. ```html .html <p>Test</p> ``` There's some config options available to you, such as setting attributes on all/external images and links, setting table and table-cell alignment classes, adjusting footnote classes and IDs, adding <code> attributes to their parent <pre> elements, and changing the <code> class if your syntax highlighter does not use language-*.
      I was thinking about adding the ability to make links open in a new tab by appending a plus to the link syntax, but only external links should be opening in a new tab anyway. Further, this would add extra, unnecessary processing time.
      Please let me know if you bump into any problems. ☺️
    • By Mike Rockett
      TextformatterTypographer (0.4.0 Beta)
      A ProcessWire wrapper for the awesome PHP Typography class, originally authored by KINGdesk LLC and enhanced by Peter Putzer in wp-Typography. Like Smartypants, it supercharges text fields with enhanced typography and typesetting, such as smart quotations, hyphenation in 59 languages, ellipses, copyright-, trade-, and service-marks, math symbols, and more.
      Learn more on my blog
      It's based on the PHP-Typography library found over at wp-Typography, which is more frequently updated and feature rich that its original by KINGdesk LLC.
      The module itself is fully configurable. I haven't done extensive testing, but there is nothing complex about this, and so I only envisage a typographical bug here and there, if any.
      Please do test it out and let me know what you think.
      Also note that I have indicated support for PW 2.8, but I haven't tested there as yet. This was built on PW 3.0.42/62.
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.50
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy!