The latest version of WordFence adds a firewall. This requires that WordFence is able to write to the /wp-content/wplogs directory, but this is owned by the wrong account when created, causing the firewall to throw up an error. The 'Reset Permissions' button doesn't fix this ownership issue either.

To run WordPress we recommend your host supports:
- PHP version 7.2 or greater
- MySQL version 5.6 or greater OR MariaDB version 10.0 or greater
- HTTPS support
.
https://wordpress.org/about/requirements/

All webmasters using subdomains or wordpress multisites will be happy about it

Your KB article on WP Rocket says that you don't fully support minification of JS/CSS due to Varnish caching on the server.

It would be amazing if you guys could reach out to WP Rocket and see if this could be resolved.

W3 Total Cache is rarely updated and is not officially compatible with WP 4.4 as of yet. Many people are speculating that the author may have even abandoned this plugin. Issues with WP 4.4 are being reported and are not resolved. I would prefer a more stable and regularly updated caching plugin.

As it is now, we have to manually create the sub domains or use sub directories, which isn't the best solution. Personally I don't have time or even want to do this manually, and I guess this is the case for most people that are interested in Multisites.

It would be great if EWWW Image Optimizer plugin would be a part of default WordPress app installation. There is an issue with installing EWWW to an existing WordPres app.

I arelady talk to EWWW developers about that.
https://wordpress.org/support/topic/cannot-install-jpegtran-optipng-etc-on-cloudways-hosting?replies=26#post-8260174

Current versions is 0.21.1, but I have 0.17.0 installed.

Maybe we can autoupdate once a week?

Our WordPress setup sets multiple cookies (from WordPress itself, Google Analytics, CloudFlare, and Third-Party Ad Networks), so every page request after the first will have cookies in the request headers. Because of those headers, Varnish considers it a "Miss" in the cache and passes through to the back end.

We need a way to be able to tell Varnish which cookies to strip for the sake of caching; on our previous dedicated server setup, we simply stripped the Google Analytics and WordPress (non-login) cookies, and that increased caching significantly.

When adding a fresh WordPress App, the default admin account Cloudways creates adopts the account holders email address. This is also becomes the display name by default, showing up on the front-end, exposing the account holders email address involuntarily. The display name should be set to something other than the email address.

For wordpress security, it is a common practice to move up by one level the wp-config.php file from the publichtml directory. Allowing the very important wp-confog.php file to remain in the publichtml directory is considered unsafe. Presently this is not possible in cloudways. WIll this be allowed by cloudways in the futire?

A button in the application dashboard which would allow us to reset the file permissions for that particular application.

Cloudways definition of staging is somewhat different from other managed WP services like SiteGround and MT Premium WP. It would be great to have dual WP setup for live and test without cloning, and hopefully with easy/simple sync feature.

WordPress is spelled with a capitol P. All over Cloudways spells it with a lowercase P.

The W3 Total Cache plugin, General Settings, should have the Minify and Database Cache methods pre-selected, like the Page Cache, Reverse Proxy

These should be pre-set like the Page Cache, Reverse Proxy, etc..

Not a high priority but useful for those new to Cloudways.

Make changes to Vanish as described here:

http://docs.woothemes.com/document/configuring-caching-plugins/

to allow varnish to work with woocommerce.

When using WP multisite with subdomains, it's a real pain to have to add each subdomain to the app control panel to make it work. Wildcard subdomains are the preferred method, since you only have to set it up one time. After that WP controls subdomains, and so no additional info is required.

It would be great to have WordPress applications have wp-cli support out of the box. It is possible to download and set it up manually but many other hosts include it pre-configured.