This worked for us, thank you. Any idea what causes the errors/disconnects? Seems like we’ve increasingly experienced them over the past year or two. Is staging possibly a factor? If so, do you have any suggestions for handling staging? We use the staging feature offered in the DreamPress control panel.
Sorry for my even slower response. Yes, there is a .git directory in site root. It appears to be created and used by DreamPress one-click staging, which I enabled for the site some time ago. There are no .git, .svn, .hg, or .bzr directories in wp-content, wp-content/plugins, or wp-content/themes.
@anthoniusalfred I did a Force updates as requested, and saw a message, “Force update checks have been initialized”, but as I had before I tried forcing updates, I still have 4 plugins that all indicate, “There is a new version of plugin name available.”
I installed WP Crontrol to see if it would show anything possibly useful/helpful. All appears normal as best as I can tell, and a web search seems to suggest MPSUM_Disable_Updates->maybe_auto_update() is specific to Easy Updates Manager.
Right, so I had already followed that down to the success message, but the trouble is with removing the A (host) record for website/domain and creating a CNAME record for that domain, that points to the Cloudfront distribution domain. When a website is created on DreamHost shared hosting, the A record is automatically created and it can’t be deleted directly (only by removing hosting for the website/domain). DreamHost prevents creation of a CNAME with the same hostname as an existing A record…and I doubt that would work well or as desired, if I could create a CNAME record with the same hostname as an existing A record. I can create an ALIAS record, but that doesn’t work as desired. Then there is the trouble of creating an alternative hostname (as described in the FAQ) and pointing it at the same IP address as the main/original A record for the website/domain. Since this is for a DreamHost shared hosting environment, where is traffic to that IP going to be routed? I don’t think DreamHost shared hosting uses a dedicated IP per website/domain…? 🤷🏻♂️ If that’s correct, they’re probably using name hints to determine how to route web traffic and the alternative hostname A record simply wouldn’t work…?
I’m a little confused by point 1, where you indicate the CDN needs to be purged after converting images, so that webp images can replace the existing images. After purging the CDN, will the CDN also pull jpg/jpeg/png images as needed, for browsers that don’t support webp?
According to DreamHost support, the problem appears to be with Wordfence. DreamHost support responded with, “…it seems as if our servers cannot reach WordFence’s cloud host as the connection dies at the boarder. A traceroute to noc4.wordfence.com dies at their boarder and a trace back to us dies as well. From what we have determined, the issue seems to be with WordFence and not us…”
Presumably, boarder == router 🙂
