I have an old installation at the time the user was the name of the application, after creating the master credentials changed the name, now I face some problems with session files, popup that does not close, I believe it is related to this because to magento save information records with The name of another user different from what it has now, then two different ones and when reset the permissions the old one disappears and the new one appears and after a while the old one returns ... it's all gone ... I'm having to clean the files Session several times a day, etc.
Would not it be nice to have an option for us to know which name permissions will be reset?

Suggestion: Change the Delete confirmation for deleting an app or server to type DELETE Server Name or DELETE Application name or something.

Reason: The process for deleting a Server or an Application is exactly the same, same buttons, same location, etc. It is just a matter of which screen you are on when you initiate the delete sequence. And although the Console does a good job of showing what you are about to delete, the comfortable and clumsy user (like myself) often doesn't pay attention and just types DELETE (because that is the process). Thus, it can be easy to accidentally delete a whole server when you intend only to delete an application on the server.

If one were forces to type DELETE SERVER 1944, it would cause the user to think about what they are deleting.

It would be very helpful for monitoring purposes and quality control purposes if we could be alerted when emails are trying to be sent from the server instead of 3rd party or add-on.

For example I have a plugin that allows me to setup emailing through mandrill on a site by site basis. This allows for better tracking. In some cases the sites are not able to communicate with mandrill and it falls back to using wp_mail() which would try to get the server to send out the email. Since Cloudways doesn't support emailing from servers these emails fail silently.

Email failing silently is very bad especially for websites that rely on form contacts for leads and sales, sign ups, etc... And this can go on for multiple months without ever knowing, which makes it even worse.

It would be awesome if this was part of cloudways server monitoring. So any time an email send requests is made on the server an alerted is made(probably through cloudwaysbot and/or webhook). That way no emails are missed and the issue can be looked into right away.

I am currently in the process of moving my sites from cPanel based hosting env. to Vultr, DO, and Linode.

I think everything you guys offer at CW is pretty great, except you folks do not provide us with root access. That's a bummer!

I think you folks should create a new package for DevOps or just for developers who are interested in having the root access. This package will offer everything your platform offers, the custom panel, staging area, security management and stuff but it would also provide root access.

Devs would know what they are doing. You'll be able to contain more folks in this package because you won't be restricting the root access.

Since you do NOT own the hosting stack, that means the only bottleneck here is your team, which is not offering the root access to keep things secure or whatever the reason there is. I understand that, but root access means more transparency to me. It also provides me with added advantages like for example I migrated, sorted, analysed 200GBs of data from my old host to Dropbox within 4 hours at Vultr. Had I not have root access, I would not have been able to do that.