Hi Ryan, It seems that the domain with www wasn't the cause and our developers are looking into it further. Could you try doing one more thing in the meantime, go to WPMU DEV dashboard in your WP admin and disconnect your site from WPMU DEV and then just login again. This should refresh the domains and might be enough to sort it out now that www domain is gone. Best regards, Predrag

Hi Matt, There seem to be issues with certain droplets which are hosted on a specific location, our sysadmins are currently investigating this and we're hoping to get some news soon. Best regards, Predrag

Hi Keith, I did couple of tests and I couldn't get access to page in question no matter what I tried, I created a new user with no role to replicate the existing one and I didn't had access to the page in question. I then tried doing the same thing on my test site with some other changes as well trying to access protected page but it also worked fine. I have attached version 1.1.6 of M2 plugin so you can try that out and see if there's anything in 1.1.5 that could be causing this, I would suggest having full backup before the update just in case. Is this an active member of yours and would it be possible to get access to it (by temporary changing the password for example) so we can test if this account still has access to that page? Also, are you certain that M2 plugin was active at that time? Were you perhaps performing a conflict test or something like that on the August 6th? Best regards, Predrag

Hi Ted, I must be honest and say that I forgot to test the backend Divi editor while doing these tests. So I gave it a try now but this also worked for me when I edited the post: [attachment=1419921,133020] From the screenshot you shared, I would say you are using Chrome on Win10, is that correct? That's what I'm testing with as well so it's strange I can't see it on my end, can you try testing this in incognito mode (CTRL+SHIFT+N) and see if it works after that? If it does it's most likely either a caching issue or some Chrome extension that you are using. Best regards, Predrag

Hi Joseph, That can indeed be expensive, so I just checked with the devs about this and they are actually discussing adding this feature in one of the future releases :) Best regards, Predrag

Hi Josh, I've seen that you had some issues with your site after the upgrade and that the restore had to be performed, unfortunately, the support access is not working properly now so could you please try revoking it and granting it again? Best regards, Predrag

Hi Kevin, I was able to create a backup on your site by trying out different Snapshot backup methods and I had to exclude _plugins.zip, ai1wm-backups and WPPS Backups folders because they were around 10GB when combined and your server was unable to handle those files. Your server limits were pretty much near the limit even without them so I would suggest scheduling Snapshot backups to start at the time when there's less load on the server to it has enough resources to finish the process. Best regards, Predrag

Hi Randall, I was able to replicate this on my installation and I have created a report for our developers to check what's causing this. Thanks for bringing this to our attention! Best regards, Predrag

Hi Wayne, I was searching for some information about AWS and all the browser caching resources were referring to Cloudfront settings, note that this is not Cloudflare, just to avoid confusion. You don't have any support whatsoever with AWS hosting? At least getting the information about which config file should be changed? another website which is hosted at Google Cloud also having this same issue. the site name iqkxx.com Is the site not working after you have added the rules or the caching status is not changing even though the rules are added? Do you have support plan with Google Cloud to ask which is the correct conf file that needs to be changed? Best regards, Predrag