If you check here - https://github.com/liximomo/vscode-sftp/issues/541

many of us are facing issues with SFTP getting disconnected and not automatically connected again. This is very frustrating in development. Creating a ticket every time and asking to increase this is not convenient.

It will be better if you could have a button that when pressed it will terminate/kill running servers or at least it will ask you "Do you want to terminate your servers and then cancel your account?"

Cloudways, you guyz must have to add the feature for downloading backup from specific point, you have to carry the data backup at least seven days as per on day wise, or time wise.

Laravel jobs tend to offload queues using "Supervisor" jobs. Laravel's docs show how to pipe "stdout" output to a file for reading. Cloudways Supervisor logs will only write errors, so there's no way to access the Laravel queue processing logs.

Normally, this is set in the Supervisor job ".conf" file with setting "stdout_logfile=".

This should be an option so Laravel users can access the Laravel queue logs, or the current Cloudways Supervisor logs should have "stdout" in addition to errors.

ie backup entire server before upgrading MySQL, so that restore of entire server is possible (inc older MySQL version) if something goes wrong with the upgrade. I understand this would be chargeable but it would save the stress levels for many a web dev

Version 1.20 provides some very useful switches such as error only logging etc.

On "Server Monitoring --> Details" the timeframes of "2 Hours" and "6 Hours" should be added back. They're very usefull and missed.

It would be great to see a dedicated service (virtual dedicated, metal dedicated or otherwise) that support custom OS installations from ISO with temporary console access (or permanent console access won't hurt)

There was an infrastructure update that defaults files/directories to 720 permissions. Now FTP users no longer see any of the files or directories because of these permissions. Chat support's "solution" is to use the "reset permissions" function, which will then change the permissions of files and directories to 770.

First, why were the default permissions changed from 664/755, to 720? I've never seen this configuration before, so it seems odd to me.

Second, why is this a two step process for FTP users to gain access to the public_html directory? The default application permissions should MATCH the "reset permissions" permissions.

HTTP2/Push feature can improve performance greatly.
it is introduced with the newer nginx version https://www.nginx.com/blog/nginx-1-13-9-http2-server-push/.

Hi,
it will be great if there is app setting for max usage of server power. E.g. a can set, that this app can use max 50 % of server power.

add unmanaged servers for cheap price

DesktopServer version 3.5.2 has a new direct deployment feature to get your WordPress websites from your desktop to your hosting provider in just a few clicks.

To do this Cloudways must support File System Direct.

File System Direct is a (PHP) feature that allows WordPress to write files to the local file system on the server. At the moment it does not so we can't use this feature in DesktopServer.

I think there should be possible besides generating CSR uploading own CSR and key for the SSL certificate. This would minimize time when migrating from some other server

Varnish hit rate is low on low traffic sites. By setting the cache time of varnisch on an application level you can beter manage site speed per application.

opcache.maxacceleratedfiles=? , opcache.validatetimestamps=? and opcache.consistencychecks=? , i would like to change this opcache settings