1) Backups of server is a payed service. Totally fair, but it is not noted anywhere inside the platform portal. You have to dig like 3 articles deep to find out the actual costs for backup storage. It would be nice if in the server settings this was more transparent communicated.

2) Once you have multiple servers it is nearly impossible to find out what is actually charged per month for backup storage costs and what is droplet cost. Some reporting on this would be helpfull.

3) And last but not least, I think backup should be optional. I can easily create a custom script and cron job to create backups of applications myself to possibly a cheaper backup storage service. However, I must use the CloudWays backup service and I am forced to pay for this.

I have a site with a number of dynamic "areas" that are not displaying/refreshing correctly due to caching. One primary area of the site is an online LMS (Learning Management System) made up of multiple lessons, topics, and quizzes. I could list each URL individually, however, it would be well over a 100 just to get started, and would also require me to continue updating the list of URLs as I continue to add new content/lessons, etc.

Ideally, I could enter in a relative url with a wildcard or utilize regex to not cache all URLs matching the pattern, such as "/courses*" for example.

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.