Currently, Varnish cache is "broken" for all query parameters. This means anyone comeing from Facebook, which adds "fbclid", or from any link with standard UTM parameters like "utm_source" is served an un-cached page.

Varnish WILL then cache that entire page + query strings, but that's not very helpful.

It would be ideal to have it behave like Cloudflare APO as described here: https://developers.cloudflare.com/automatic-platform-optimization/reference/query-parameters/

So, for the "allowed" parameters, Varnish would serve cached content of the base URL without parameters.

This is such a basic feature that exists on any cPanel hosting plan. Simply allow us to set the root folder for a new SFTP accounts for an application.

I have software that automatically uploads to the SFTP but the upload fails because your default root (applcations/(appname) is not writable. Simply add a field to let us specify where the root for he new SFTP we just created will be (i.e. applications/(appname)/public_html/newfolder

I cannot stress enough how useful this will be for us developers and will make the CloudWays experience more robust and scalable.

During Vertical Scaling when the website goes down it would be great to see cloudways display a page like "Back soon currently making this site more awesome" or something to comunicate that the website will be back up after the scaling as no server side extension or feature can run for most of the upgrade it just shows as no responce from server.

I need an Indian server for my Indian users can you please add more Indian data centers in Digital Ocean and vultr. currently, I have only one option in the digital ocean for Indian users.

Right now, we can whitelist IP addresses. Please allow wild card (%) for whitelisting any IP for remote access. Thanks.

I think it is essential to have the option for monthly schedule updates. Plugin updates sometimes can break a site from faulty code, and I think it would be useful to have the option for not-so-regular updates. A monthly option sounds ideal because it will reduce workload for our developer to check on regular base the site after the updates which now the latest scheduled option is weekly.

Right now, if we need to add varnish exclusions, they must be entered 1 by 1 in the cloudways control panel. UTM tracking is more and more popular, in which case there are 18 cookies to exclude. Most cache plugins simply have a text box to paste those exclusions in, 1 on each line. Having this in the Breeze plugin instead of the control panels would be a great improvement!

I'd like to be able to blacklist or whitelist some ip to make sure that my users MUST pass by the WAF to access my website.
In this moment, if they know my server ip, they can bypass the waf.

My customers are in the USA and my employees in Asia. The US based server is super fast when accessed from the USA, but from Asia it's slow. I want to run a duplicate mirror server in Asia, but have been unable to find someone with the skills to do this. Would be a great feature if Cloudways could do this with a few clicks.

Hi, I've read somewhere in this forum that your architecture don't support multiple php versions. How about making another architecture that supports php versioning per app? It could be a mini server that caters only to single app.

Offer the ability to wipe all files and database entries, before pulling a fresh copy from live to staging.

Sometimes I need to redo our Sandbox environment.
Most of the time, there are various changes to the files and database.

When I choose overwrite it won't wipe the remaining data.

If I delete the whole app and stage again, I have to redo SSL and other settings.

Please give a third option to the "Live > Staging" process.
- Overwrite
- Incremental
- Wipe and Write

Thank you

Please update Composer to version 2.

Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2. See https://blog.packagist.com/deprecating-composer-1-support/

Also, allow a user to write to composers cache folder:

"Cannot create cache directory /home/12341234.cloudwaysapps.com/hfjhsdkfhdsjkf/.cache/composer/repo/https---repo.packagist.org/, or directory is not writable. Proceeding without cache"

The current version of ImageMagick is from the legacy (v6) branch. Updating to the latest version of the v7 branch would allow for AVIF image format support. AVIF has been out for a couple years now and can provide substantially better compression than WebP.

Gatsby seems to be sinking its teeth in. It may be here to stay. True headless sites are so ridiculously fast, you can't ignore them. From my research, it seems cloudways does not currently support gatsby serving. I've looked at your other headless options and they're good, but not the same as Gatsby. I recommend you look into it and begin offering options. Thank you for hearing me!

Add option to purge inode,
Right now the only option to do this is just through support.