Hello team, pushing and pulling individual tables and folders between staging and the live environment is better compared to transferring the entire database or files. Because in Woocommerce, pushing the database might lead to loss of orders made in between.

After enabling SSL in my sites, I run multiple tools to scan for vulnerabilities and imisconfigurations. Every one of them is telling me that those protocols are insecure, deprecated and should be disabled. I asked support to do it server wide, but they said it can only be done manually on app basis. To me this is unacceptable, since this should be approached from a server perspective as a whole.

Latest version available is 9.2.0.247 but servers uses 8.7.0.242. They fixed issues with Drupal, Codeigniter, Predis, Guzzle, Wordpress, Symfony, PHP-FPM and more.

Please support TLS 1.3 since it's faster and more secure. Chrome 70 and Firefox 63 officialy support it now.

https://www.ietf.org/blog/tls13/

Thanks for adding the new staging feature, this is great!

During my testing I discovered that my staging .htaccess file was pushed to live and the result was a 500 error on live. I need to use a slightly different .htaccess file on staging, because I force the www version on live. I couldn't access staging with this rule. So the differences in .htaccess rules caused the error.

It would great if you could add a way to ignore certain files, similar to gitignore.

Instead of forcing us to dig up the htaccess file for modifications, make this a simple Control Panel-based modification.

Please add Paris as a supported region. In France, for legal reasons, data must be hosted in France.

Please add the new Europe Nordic Region for Amazon AWS

It is very important have the possibility from console or from the web panel reset the permissions to the application user. Today we can res

Provide Let's Encrypt free wildcard SSL

https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html

ElasticSearch package is outdated and needs to be updated to be compatible with my current applications.

I have GeoIP country switcher on my woocommerce site.
But when I use with Varnish, it forces back to the country which the GeoIP detects instead of the one user wahts to change to. Once Varnish deactivated, country switcher works properly. First detection correct as well as manual change of the country possible.
This module should solve the issue.
https://guides.wp-bullet.com/cache-woocommerce-currency-geoip-varnish-4-vmod/

Staging enviroment withouth syncing the orders from staging back to the live enviroment. It would be great to have this feature, as the orders on the live site should always be leading.

This also goes for WooCommerce shops.

Composer auto update not working on new server deployment. Please fix this.

Currently, you have laravel 5.5 version as the latest version. But the latest version of Laravel is 5.6 right now.

I would like to suggest you upgrade laravel from 5.5 to 5.6 because currently I am working on 5.6 but your system doesn't support that.

Currently, Breeze doesn't purge automatically Varnish caché when saving post updates vía Gutenberg plugin. It would be useful since new editor will be shipped by default with the next major version.

Currently, while cloing an application, the automatic site url provided to the clone is not written in the database. This results in launching (redirected to) the original website when you are typing the new url.

The issue does not exist when the original site has been issued a domain name. Because the staged website does not have a domain and trying to clone a staged website, the database entries are not written. I don't know why. Could you please test and fix this? Thanks!

When will cloudways support or upgrade to mysql 5.7 and varnish 5?

tks.