Git-updater: WP-Cron does not finish

[maxleistner]

The following message does not stop appearing even after 1h 15 min of waiting and reloading the sites front-end and admin. This happens since the latest commit. Any ideas?

GitHub Updater Information  
Please be patient while WP-Cron finishes making API calls.

[afragen]

A couple of questions.

Has updating via WP-Cron ever successfully worked for you or is the first time you’ve used the plugin?

If you have previously used GHU successfully, what version was it?

Is something on your server set to disable WP-Cron?

[maxleistner]

Thanks @afragen for the fast response. No i did not use the plugin on this site before.
I tried it on another page and after several hours it updated the repo information, but on this on page the message still does not disappear.
WP Cron works fine on other tasks.

[afragen]

Can you install https://github.com/afragen/github-updater-support ? It adds a couple of other plugins to assist in figuring out the issue. It also overrides the WP-Cron updating which helps in troubleshooting.

[maxleistner]

Alright - i get the following error after installing the support-plugin:
GitHub Updater Error Code: cURL error 35: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

[afragen]

Is there an HTTP GET that the error is associated with? It seems like that particular server may have an SSL issue.

[maxleistner]

As it seems i might be a problem with cURL and SSL in relationship with an older php version (5.6.10). I will ask the administrator to check the certificate and update to php 7.*
I will recheck and get back to you. Thanks!

[maxleistner]

I upgraded to php 7.2 and the error message disappeared, but still there is no mention of an available update, but for sure there ist one :) Do i need to call the function somehow which checks for new versions?

[afragen]

Can you share the repo URL? Can you paste the plugin headers here?

[maxleistner]

https://github.com/hingst/layotter
What do you mean with plugin headers?

[afragen]

A link to the repo is fine.

I was able to install and update without any issue. Are you still having issues?

[blachawk]

I'm facing this same issue of having the notification show up at the top of my wp-admin pages. its also preventing me from having options to switch branches on my github plugins. Is there anyway we can dig into this and find out what the technical hold up is?

[afragen]

@blachawk I'm attempting to _dig_ into this. Please install the GitHub Updater Support plugin, referenced above and activate it. Activation results in GitHub Updater not using WP-Cron which helps figure out what the actual issue may be.

Specifically, look into Query Monitor HTTP API Calls and the debug.log

Please let me know the results.

[blachawk]

Many thanks for investigating this! The latest wordpress notification that now shows up is...

GitHub Updater Error Code: There may be a problem with WP-Cron. A GitHub Updater WP-Cron event is overdue.

I'll be taking next steps with your suggested plugin and testing.

[afragen]

That error usually shows if WP-Cron is not running on your server.

https://github.com/afragen/github-updater/wiki/Background-Processing

[blachawk]

@afragen I installed the support plugin successfully. But the first notification to pop up once it was active was the following:

Notice: Undefined index: source in C:\Users...\wordpress\ithub\wp-content\plugins\github-updater-support-develop\vendor\afragen\wp-dependency-installer\wp-dependency-installer.php on line 427

[blachawk]

I discovered the source for the previous notification I posted. I had the following setup within my wp-config.php file. Once I commented it out, the notification went away. This was a practice I found online in order to reduce posts from being automatically saved so often. It's ok in my situation to comment it out...

//NFFA- Reduce WP Post Revisions
define('AUTOSAVE_INTERVAL', 600); // seconds to help reduce auto save increments
define('WP_POST_REVISIONS', 5);

...I'm now waiting to see if the WP cron job will fix itself now and process the way it should...

[blachawk]

I believe I found the source for why WP-Cron does not finish, all with the help of your support plugin! For some reason, GitHub Updater is tracking the "Search Everything" Plugin and causing 404 errors.

https://api.github.com/repos/afragen/github-updater/contents/search-everything.php?ref=master&access_token=my-access-token

How do I keep the WordPress "Search Everything" plugin active in WordPress, but remove it from being tracked by the GitHub updater? It should of never been tracked to begin with.

Many thanks!

[afragen]

Well the Search Everything plugin as an incorrectly set GitHub Plugin URI.

https://wordpress.org/support/topic/error-in-github-plugin-uri-header/

If this is causing the issues, I would remove the GitHub Plugin URI headers from Search Everything. It doesn't appear that it has been updated recently.

[afragen]

@afragen I installed the support plugin successfully. But the first notification to pop up once it was active was the following:

Notice: Undefined index: source in C:\Users...\wordpress\ithub\wp-content\plugins\github-updater-support-develop\vendor\afragen\wp-dependency-installer\wp-dependency-installer.php on line 427

Does this persist?

[blachawk]

No it, no longer persists because I removed...

define('AUTOSAVE_INTERVAL', 600);

from my wp-config.php file. which I was using for other purposes.

[afragen]

@maxleistner are you still having issues?

[blachawk]

No, this issue can be closed. Thanks for the work-arounds!

[rob]

This message constantly shows for us.

We do have cron disabled in wp-config.php because we're running it manually via crontab on the server. Maybe that's why?

[afragen]

@rob take a look at
https://github.com/afragen/github-updater/wiki/Background-Processing and make sure that you run the cronjob at least once a day.

[afragen]

@rob you might want to look at WP-Crontrol to see if there are any other wp-cron issues. 😉

[afragen]

@rob could you create a new issue for your particular problem?

[rafaelurben]

For future readers: I also got this problem, but after activating the debug mode, I realized, that Firefox has put py password in the GitHub-Access-Token field and so there was a wrong token which stopped the update process from working.