Hi

I notice that recently you have put in place tools which force a strong username and password for staging sites. Previously the username and password could be anything at all.

I'd like to suggest that you should roll back this change. Although (of course!) I am wholly in agreement that passwords should be strong in almost all cases, I believe that staging sites should have an option for this not to be the case.

Why?

1. Mainly - because the most obvious use case here is for sharing with a client. Whereas we could previously have for instance "demo" and client name as u/p (easily memorable both for us and for clients) - now we have to create and constantly re-share passwords when the client can't remember how to get in

2. Password managers don't normally offer the option to save popup NTCR-style passwords like this so we have to resort to logging into the CloudWays interface to see what is set

3. The actual thing that is being passworded isn't very sensitive - and actually shouldn't be. A staging site is almost always just a copy of a live site where tech changes have been made. In our case, the only reason for passwording it in the first place is that we don't want Google and other bots spidering it - it isn't sensitive at all.

4. If you left this option so that you had a warning there about weak passwords - "Are you SURE you don't want a strong password for this?" then IT people like myself can make a call on whether to set it as strong or weak, depending on use case. Mandating it in the way you do is preaching to an already tech-savvy audience!

Regarding Cloudways' account verification process, please consider changing this system. I can no longer suggest my clients to use a company that doesn't put the server online within the hour. A 24-48 hours time period to get the server online it's nonsense. You guys really need to figure out another way to do this faster and easier. Also, to send documents for account verification by email is very rudimentar, I don't see this method for account verification anywhere else. Maybe upload documents on the website? Maybe let user know how long it will actually take to get the server online? Maybe verify the account within the hour? Many things to improve there in my opinion.

We are happy with cloudway support and services. But i found a major drawback there with cronjob setup. We can't setup cronjobs there as command line. Like in cakephp project we need to run console command like Console/cake Marketplaces runshellcommand, But it doesn't accept it, Now a days all frameworks need a console command to run for cronjob, But this feature not available there.
2) I didn't found a way for File manager, Where if possible we can edit files online, rather than connect with FTP.

Please add 2 features there, Would be good for applications and user point of view

As a developer, i am continously pushing changes via git deployment interface, but throughout the day my session ends and i am logged out.

When i log back in i have to go finding my application and git screen again.

It would be great if the cloudways interface could remember where i was when the expired session logs me out, and when i log back in it remembers then i can perform the git pull i tried to do before i was logged out.

Or better yet an option to set my own timeout values as that kind of security isn't required for my workplace.

Hi,

I have canceled my plan due to the horrible support:

• Non-English speakers, most of the time I couldn't even understand what your support staff is trying to say. Please hire people that at least know some basic English. That happened on multiple occasions.

• Terrible advices. I've never seen so bad advices from a hosting provider.

• Weak passwords. I've never seen a hosting that is forcing its customers not to use upper case for its passwords. That was brutal.

• Support randomly closed tickets after failing to explain what they want to say.

I am a technical person and I do website hostings from 2012, so I am not a newbie.

Your support is terrible!

This is not a longterm strategy for a company.