Cloudways server backups require at least 50% storage space of the server to perform a full backup. This mean's although they are moved off the server once complete if you are currently using 51GB of 100GB storage the full server backups will fail to run. For those that backups are important to, at least 50% must always be available.

It would be good to have a feature somewhere in the server management that won't allow you to fill the server more than 50%.

Other suggestion:
- Warnings to say "Your website is 51% full, backups won't run! Free up storage on your server or increase your storage for backups to run on the next cycle."

When you click on a database table, you're taken to the Select data tab, which is great. However, the header section is only displaying two fields, neither of which are labeled. All the actual labels and additional fields are missing. This means it's impossible to sort the data, filter, or search for advanced content.

Here are two screenshots, one of what IS visible:
https://www.dropbox.com/s/yyp2meohkaxlakk/What%20IS%20Visible.png
and another of what SHOULD BE visible.
https://www.dropbox.com/s/qaycu7qc3h5ux00/What%20SHOULD%20BE%20Visible.png
Hope that helps explain what I'm talking about.

Clearly, all the form fields are already there, but they're hidden. Looking at the CSS, it looks like there are two rules that are for some reason hiding the missing fields.
In the file: /css/style.css
There's this rule:
#inner_page #content fieldset legend {
display: none;
}

This hides the labels for each field.

Additionally, each fieldset seems to have the class "hidden" which then hides those fields.

It would be super helpful to have access to these fields to be able to select the appropriate data using the form rather than having to write SQL for simple Select actions.

Particular to NJ location VULTR HF. When I purchased a 16 GIG VULTR HF, there were options for 32 and 48 available in NJ. But I cannot vertically scale without cloning and moving. I'm not able to vertically scale the VULTR HF. I understand these are VERY popular servers, with good reason, but as I expect my business to grow and traffic increase, it's not efficient to have multiple server when in just a few minutes I should be able to scale. I moved here from SIteground due to stability issues. I don't want to have to clone, or add more servers. I just want to scale!

I have dozens of domains added to my server, all with Let's encrypt certificates.

Sometimes, I face an issue when I can't add a certificate for a new domain because one of the old ones has got its IP address misconfigured.

Error reporting for these cases, as it is now, is not very descriptive, so I am forced to manually copy-paste all my domains (up to 100 of them) into a DNS lookup tool.

The current error message in such cases look like this:
Server 4: Please make sure that your domains are pointed correctly to your server IP

Desired look
Server 4: Please make sure that your domains are pointed correctly to your server IP. Domain go.example.com is not pointed to your server IP.

The cpanel currently accepts configuration values for SMTP that get carried through to postfix (or whatever), but do not allow us to set a custom From: header. As a result, nearly every SMTP relay will reject the message.

Workarounds include generating email from PHP (usually via PHPMailer) or on the command line using mail -r "from@example.com". However by default, without any workaround, email generated by the system (such as using the MAILTO= in a crontab) will simply fail.

I've not encountered a server stack before that takes in SMTP configuration for the server but fails to take in all values needed to actually deliver system-generated outbound mail without a workaround. It seems like it would be a useful baseline for the stack that outbound mail works "out of the box" at the OS level.

Currently, new sites cannot be created with the development user/pass UI for adding a username and password to access the site. When you are developing a new site it is important to keep it from being crawled by search engines, so it needs to be behind password protection. right now the only way to accomplish this is to either edit the htaccess file or else install a maintenance plugin.

Specifically, I wanted to create a Staging site from a site that is currently hosted on a server that has an older database. My development server has the latest versions of PHP and of the DB software, but the landing page was created on a site that isn't upgraded. One of the sites on that source server is old and I don't want to deal with upgrading it right now. So I am having to clone the other sites to one of my non-upgraded servers, upgrade that one, then clone it again to my dev server in order to get the user/password option. Because not all the users in my company will be well versed in such things as htaccess files, I feel it's a bad practice to use htaccess for this purpose.

You could add the option to create a new site as a staging site, or else just add a UI to put a user/pass on the site as you are developing it. That would be a great new feature.