Remkus de Vries

It’s actually https://remkusdevries.com and I get enough traffic. I’d like more, but it’s enough ??

I received the emails at the following intervals:

• Oct-16 at 16:09
• Oct-17 at 04:06
• Oct-17 at 16:06

So that confirms an interval of 12 hours, but it doesn’t make sense it is updating to the same version every single time.. right?

I have gotten three email notifications now stating the following:

WordPress 3.7-beta2-25801-20131016
----------------------------------
Updating to WordPress 3.7-beta2-25801-20131016
Downloading update from https://www.ads-software.com/nightly-builds/wordpress-latest.zip...
Unpacking the update...
Verifying the unpacked files...
Preparing to install the latest version...
Enabling Maintenance mode...
Copying the required files...
Upgrading database...
Disabling Maintenance mode...
WordPress updated successfully

And yes, that means three times it’s updated to WordPress 3.7-beta2-25801-20131016

I added the public IP address to the whitelisted list and that did the trick. Thanks for the extra brainpower ??

We are using the standard WordPress cron. Default whitelisting is done by adding 127.0.0.1/32 and 33.33.33.1/32 to the list.

The blocking is done by using admin_ips – range of IPs (in CIDR notation) that can access the version of apache2 running as the app_container “admin” user. Effectively, accessing a site from these IPs gives the user more permissions to do things like upload WordPress Updates / Plugins. More info here at the bottom. If you’re curious what the chef recipe actually looks like go here.

What this does is when you come from an admin ip, then you get redirected to an apache running as a user with write permissions to the WP files. If you come from a non admin IP, then nginx redirects you to an apache running with only read permissions on the WP files

No worries Mel. I’ll continue to poke around and see what’s what. Thanks!

Ok, so the most important assumption is correct ??

Should I be getting an email if WordPress thinks it’s been prompted for FTP credentials explaining me it can’t update itself?

I have seen that list, but the only thing that I don’t understand if it were to fail is why I wouldn’t receive an email if something went wrong.

Our servers are setup in a way that anyone accessing the site behind a non-whitelisted IP address will be prompted to enter the FTP credentials. If you’re accessing from a whitelisted IP address you can simply run any updates as expected.

It’s my understanding that WordPress itself, from localhost that is, is triggering the update, correct?

Remote and yes. The only thing going on is that we have IP based access going on for the updates. As in, I need to whitelist my IP address (and localhost and such) to be able to update plugins and core.

I’m now beginning to wonder from which IP address the actual update script is instigated. Does anyone know?

Any thoughts on why I didn’t get any email notifications whatsoever though?

Wouldn’t actually have to be that hard. Via an add_theme_support( 'schema' ); call you could implement something like this.

What’s the status of this currently?

Odd, this worked in the older versions just fine. Wrapped the remove inside a function and hooked in later. Works fine now. Thank Ron!

Thanks Dave, appreciate that ??

I should’ve mentioned this, but of course I already tried all of this. Not new to the game ?? I merely put it here so Nathan has a reminder ??

Quickest way to get that going is to install the Jetpack plugin: https://jetpack.me/support/infinite-scroll/

Were you seeing the translation prior to this last update? And are you now seeing a translation with version v1.2.8.3?