A number of instances now, our website’s DOMAIN_CURRENT_SITE fixed, saved inside wp-config.php has been overridden by what seems to be a reverse DNS of our websites IP tackle… Since we use AWS elastic IPs, this seems to be one thing like aws.12345146.someothertext.aws.com as an alternative of www.ourdomain.com. When this occurs, the positioning turns into unreachable.
The DOMAIN_CURRENT_SITE worth must be reverted, and we additionally have to run a couple of updates on the database to revive some urls there.
The final two time this has occurred it was Friday morning, so we suspect an automated replace (plugin maybe) or course of. An audit log plugin reveals Yoast search engine optimisation and Gravity Kinds up to date early this Friday, however nothing seems for the Friday prior, so that could be a pink herring.
Logging is presently disabled and I can flip it on, nevertheless I want to reserve permitting the positioning to fall over once more subsequent week solely as a final resort, as when that occurs it’s a Dangerous Factortm.
I can submit a request to alter the reverse DNS outcome for our elastic IP nevertheless I would favor to repair the reason for the problem slightly than the symptom.
Anybody have any concepts?
Replace: to re-iterate, the database additionally wants an replace run to take away the brand new url in a couple of locations, which means I can not solely make wp-config.php read-only and name it a day… the db adjustments are, particularly:
UPDATE wp_options SET option_value = 'http://www.ourdomain.com' WHERE option_name IN ('siteurl', 'house');
UPDATE wp_site SET area = 'www.ourdomain.com';
UPDATE wp_sitemeta SET meta_value = 'http://www.ourdomain.com' WHERE meta_key = 'siteurl';
UPDATE wp_blogs SET area = 'www.ourdomain.com';
I’ve put in a cron viewer for wordpress scheduled jobs, and snapshot-controller-full-cron-start_backup is run 1am Friday mornings, and stands out as the trigger. Have not been capable of find and additional information.