Please add geo detection capabilities into Varnish, this will accelerate use case scenarios where geo detection is essential.

For e.g. in WooCommerce, their current method to provide multi-currency that's compatible with cache is using Woocommerce based geo detection, which tends redirects the visitor 4 times to the correct URL of the page with the correct currency/tax displayed.

Other multi-currency plugins attempt improve this but their loading speeds are too slow, drastically affecting woocommerce store loading times, and making caching useless.

By having geo detection capabilities right in the server stack (Nginx or Varnish, which ever is hit first by visitors) we have opportunities to use this capability to serve the pre-cached store with the correct currencies.

For reference, this is one example of a Varnish configuration to link with a multi-currency plugin.

https://guides.wp-bullet.com/cache-woocommerce-currency-geoip-varnish-4-vmod/

Another with NGINX and various other caching plugins.
https://aelia.freshdesk.com/support/solutions/articles/3000042591-how-to-add-dynamic-caching-to-your-site?fref=gc&dti=962543703760049

The issue of multi-currency woocommerce store with caching issue is discussed here.
https://aelia.co/woocommerce-currency-switcher-cache-new-solutions/

So here my suggestion for a better backup scheme. Do something like keeping:
= 1 - 3 monthly backups
+ 3 weekly backups
+ 4 - 6 daily backups
This way a longer period is covered without increasing the space required for backups. You can try keeping it at 8, although 12 would be ideal as it will cover last 3 mo, last 3 wk, and last 6 days.

Other suggestions:
- Allow to choose the time of day to do backup so it won't slow down the server during busy hours.
- Allow to choose external backup destination like S3, Dropbox ... so you don't have to worry about space. Of course you need to create a way for us to be able to recover a full server from a backup too.

===========================================
Current backup as it says on https://support.cloudways.com/how-to-backup-my-server/

"Note about backup retention:
We keep eight days worth of backups (this is a fixed setting that you can’t change)...
How many backups this includes, depends on the backup frequency that you have set:
- If you have set frequency to daily (default), we will keep eight backups (one per day for the last eight days).
- If you have set frequency to seven days (weekly), we will keep just one backup."

I was considering setting it to every 2 days thinking that I'd have 16 days more or less covered. Or weekly to have 8 weeks worth of backups. But according to your article I would only end up with 1 weekly backup. So why not retain 8 backups no matter what the interval was set as?
I also don't see the value of hourly backups if only 8 are kept.

However, in the end, none of these make a good backup scheme.

When a website is SSL secured (https) it is recommended to have redirect rules in place which enforce https (redirect http to https) and of course redirecting to one version (www vs non-www).

It appears that the Let's Encrypt Auto-Renewal does not work. It will fail saying there are htacces rules restricting it from working. I am not sure if this is an issue for Cloudways to fix, or Let's Encrypt.

In either case, the solution provided by Cloudways support is to:
1. Temporarily rename your .htaccess (so it is not in effect)
2. REVOKE your Let's Encrypt Certificate
3. Install a new Let's Encrypt Certificate
4. Revert the name of your .htaccess (so it is back in effect)
(note, even if you remove your .htaccess in step 1, the manual "Renew Now" will say it worked, but it will not work, the old certificate will remain)

I would like to think there is a long term solution whereby the auto-renew will work. Especially since these redirect rules should in fact be in place (if you are not redirection all variants of your website to a single variant, you do not have your site setup correctly).

Is there some way for this to be resolved?

Allow a way for a SINGLE person (and their email) to be associated as a TEAM MEMBER on more than one account.

At the moment, a person would need to create several different emails to be be a TEAM MEMBER on more than one account.

There should be a GENERAL ACCOUNT console (that doesn't require a hosting/server plan.... however it CAN support a purchased plan if desired) that is separate from any TEAM MEMBER access associations.
On the console you should be able to see all of the accounts you are associated as a TEAM MEMBER on... and access them from your own MAIN ACCOUNT.

The current option to add mailboxes from Rackspace is extremely limited.
The only way to order them, is via a small window and is very limited information.
I have no details at all about current mailboxes, quota usage etc...
Also, the only way to order mailboxes is by TYPING in the details in the window including the desired password for the mailbox???
Afterwards, I get a confirmation back from support with the password in the email.
It's completely unsafe to communicate about passwords this way.

And lastly, there is no control at all about the mailboxes.
I can't create extra alias, I can't activate forwarding, etc...
for each and every change we have to request via support and wait for them to fix it, while some things I can do very easy myself instantly.
I don't understand why there isn't a control panel to manage the mailboxes?

My suggestion is that all WordPress apps use the Woocommerce Varnish by default.

This way there's no risk of a user installing a normal WordPress app and later installing Woocommerce on it, only to find out that their cart is broken because of Varnish.

Here is why:

I found out that the WordPress app uses a unique Varnish and the Woocommerce app uses it's own unique Varnish.

I ran into a problem with a WordPress app that I later decided to install Woocommerce on. Once I did, the normal wp Varnish did not support Woocommerce and it broke my cart functionality. I had to make a new Woocommerce app and migrate my site over there so it could use the Woocommerce Varnish.

The support team told me that Woocommerce Varnish would also work for a plain WordPress app without Woocommerce.

Having to pay for a bandwidth that will rely on behavior of internet (such as robot attack, malware, what ever intention...) but not being able to stop the expense is not something anyone would sign for, woudl you?

Therefore, having an alarm on bandwith with a threshold set by us is something to consider. Though the monitoring can be done through SSH , alarm must be done by email since none of us are spending they day watching the bandwidth consumption.

I will not sign for the account for this reason. that is total not acceptable interm of business rules for the moment. Since I have no protection and can end up with a bill of $ 5000 without even knowing it and with no corresponding customers on the website.

On top of not being able to delete logs ourselves (which should be made possible - as suggested by other feature request), it would be massively useful if there was an option to set a timer for logs (both error & access) to be auto-cleaned.

Even if we can control the error logs to a degree (by fixing the application errors), we can't fully control access logs which is a problem because it literally means that the disk space for app is constantly growing - and if you don't pay attention it could take your site down due to full disk within a few weeks (more or less depending on disk size).

Long story short, would love to see a feature to setup a timer for auto cleaning all kinds of logs (older than X days; every 30 days, every 15 days, etc).