Service Improvement
Cloudways values its customers and their feedback! You can now give us your feedback on how we can improve Cloudways services, solution and products by pitching in your ideas!
-
Upgrade wget to version 1.20
Version 1.20 provides some very useful switches such as error only logging etc.
1 vote -
SSL Session Cache
Add the ability to turn on sslsessioncache.
Gives a speed boost for but also cuts down overheads for not having to request new keys every time a page request is made.
This is a pretty standard option, it shouldn't cause any conflicts as can be set individually on drops.
This is one line for a quick gain...current SSL testing is failing on this point.
4 votes -
Multiple IP addresses assigned to a server
I would love to have the option to assign multiple IP addresses to a server, so we can have different apps each on its own IP, on the same server. Right now, we have to boot up a new server (multiplying the costs) each time we need a new IP for an app.
8 votes -
Suggestion: Add 'mailhog' service to servers
https://github.com/mailhog/MailHog
MailHog is very handy if it comes to development. It catches every sent mails and shows them on a web interface.It would be nice if one could enable/disable MailHog like other services for development purposes.
3 votes -
720 Permissions on app creation Issues
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.
1 vote -
Multiple webroots per single application
More advanced PHP applications can have multiple webroots accessed via different subdomains. For example, one is the public website for customers (www.mydomain.com) and another for the staff (accounts.mydomain.com).
For example, Cloudways is advertising support for Yii Framework (https://www.cloudways.com/en/yii-hosting.php). This framework implements the mentioned architecture in the following way:
There are "frontend" and "backend" modules in the application directory and each of them has a separate webroot. The configuration could look like this:
www.mydomain.com -> /path/to/yii-application/frontend/web/
accounts.mydomain.com -> /path/to/yii-application/backend/web/This could be even configured on a basic cPanel hosting. I have already asked on the support…
1 vote -
Add Database Server like RDS for multi server applications.
Multi-server applications are very common these days.
Example: Application files on one server and Database on another server like RDS.
We need such option to put our large applications onto it.2 votes -
Wildcard SSL for multisite but also works for mapped domains
Right now we have two options for having SSL working for WordPress networks. We can have a wildcard SSL certificate OR we manually map domains to each subsite. It would be nice of we could have both.
Thank you
8 votes -
Server Monitoring Details - Adding back "2 Hours" and "6 Hours" timeframes
On "Server Monitoring --> Details" the timeframes of "2 Hours" and "6 Hours" should be added back. They're very usefull and missed.
1 vote -
It would be great to see a dedicated service (virtual dedicated, metal dedicated or otherwise) that support custom OS installations
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)
1 vote -
Add write permissions to user (~) directory for SSH application user
The application user does not have write permissions to their own user directory (i.e.
~/
). This prevents any application that needs to write to this directory from being run when logged in as an application user, such as git, ssh, npm, etc.Making the user directory for the application user writable by the application user, so that new files and sub-directories can be created, will solve many issues that myself and others are having running applications when logged in as an application user.
Other feedback ideas this should solve include:
Please enable NPM in SSH when we are using…
5 votes -
add HTTP2/PUSH feature
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/.1 vote -
2 votes
-
Settings of max server power per app
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.1 vote -
add unmanaged servers
add unmanaged servers for cheap price
1 vote -
LEMP Stack with Apache removed
The current setup seems to be only using nginx as reverse proxy in front of apache/php-fpm.
Right now requests seem to go this way nginx->apache->php-fpm.
We'd like to test with apache completely removed and nginx->php-fpm direct.
We'd like to have a nginx -> php-fpm setup for generating dynamic content on uncached pages for faster performance.
We are able to get twice the page loading speed from a direct setup on Linode with identical specs with Nginx used for php-fpm than the Thunderstack use of Nginx only as a reverse proxy and Apache for php-fpm dynamic content.
When a customer is…
39 votes -
Same package as Digital Ocean
Have the possibility to have the same Standard Droplets and CPU Optimized Droplets as Digital Ocean : https://www.digitalocean.com/pricing/
7 votes -
Tracked deletions in git should be synced with the server upon deployment
Currently when using the git deployment feature, if you delete a previously tracked file and push this change to the server it doesn't delete the file from the server.
This means you're left with lots of legacy files that are no longer needed, and your repo is no longer in sync with your server files.
This can cause issues if you ever wanted to push changes back from the server to git as it would then track the previously deleted files and re-add them to the sever!
I'd assume this to be expected behaviour but there might be a reason…
7 votes -
1 vote
-
It would be really good if more exposure to tools like jenkins and dockers are there and also easy proxy port selection
Docker configuration setup for staging and development scenarios
6 votes
- Don't see your idea?