Home Cloud / VPS

Cloud / VPS

By Dennis Nind

• 5 articles

cPanel License Pricing for VPS / Cloud Servers

Fixed Pricing Plans Solo Cloud - Accounts: 1 - Cost: £9.95/month Admin Cloud - Accounts: 5 - Cost: £14.95/month Pro Cloud - Accounts: 30 - Cost: £24.95/month Plus Cloud - Accounts: 50 - Cost: £29.95/month Premier Cloud 100 - Accounts: 100 - Cost: £39.95/month Premier Cloud 150 - Accounts: 150 - Cost: £49.95/month Premier Cloud 200 - Accounts: 200 - Cost: £59.95/month Premier Cloud 250 - Accounts: 250 - Cost: £69.95/month Premier Cloud 300 - Accounts: 300 - Cost: £79.95/month Premier Cloud 350 - Accounts: 350 - Cost: £89.95/month Premier Cloud 400 - Accounts: 400 - Cost: £99.95/month Premier Cloud 450 - Accounts: 450 - Cost: £109.95/month Premier Cloud 500 - Accounts: 500 - Cost: £119.95/month Scaling and Increments All fixed plans above 100 accounts will be scaled in increments of 50 Accounts, adding £10/month in incremental licensing cost per block of 50 Accounts. This equates to £0.20 per account. Upgrading Plans When a licensed server reaches the account limit of any fixed plan, an upgrade is required in order to add more accounts to that server. Upgrading between two fixed plans will require payment of the difference in price between the two plans. For example, upgrading from cPanel Admin (£14.95/month) to cPanel Pro (£24.95/month) will cost £10 to upgrade. Please note we are unable to prorate upgrades that occur in the middle of your monthly billing cycle.

Last updated on Jun 12, 2025

Grant SSH Access on your VPS to Brixly Support

To grant us access to your server, please run the following command in the root of your server prompt… curl https://gitlab.com/brixly/ssh-keys/raw/master/public.keys | tee -a /root/.ssh/authorized_keys && chmod 600 /root/.ssh/authorized_keys **Important: We are not permitted to access your servers via Password Authentication - as such, the above is required before we can access any virtual server or cloud server. **

Last updated on Jun 12, 2025

VPS / Cloud Server Management - What's included?

Let us manage your Brixly-hosted servers, freeing up your technical staff. Server-managed services include OS updates and patches, server security hardening, optional proactive service monitoring, and more. Unmanaged Servers are, by default, deployed unmanaged. We will only provide a guarantee against the network uptime and provide support for the platform/infrastructure. However, we will not be able to SSH or login to any server without an active management plan. Managed - £39.95/m Our managed plan allows us to provide complete server administration with up to 3 hours of technical assistance/consultation monthly. Please note that, at the moment, we do not provide support or management plans for Windows servers. Tasks will be carried out on request via our support ticket system on a reactive basis. - 24/7/365 Technical Support (more information) - Senior Analyst Escalations / Assistance - CentOS / Ubuntu / RedHat Support - Setup / Configure CSF / Firewall - LAMP Stack or Control Panel Installation - Malware Scanning with Maldet - Performance Optimisation and Tuning - Configuration Changes (NGINX, Apache, MySQL, PHP etc) - Installation of Software, such as Control Panels or other We do not proactively monitor managed servers by default, as we are aware clients from time to time may take their servers offline or carry out their maintenance - this leads to a high number of false positives, reducing the effectiveness of our monitoring facility. However, if you require proactive monitoring, please get in touch with our support team, who would be more than happy to enable this on your managed servers. External Server Management - £89.95/m If you have servers hosted with another provider but require assistance with your servers, we offer a management plan to help. The exact terms as the above apply to servers externally hosted. Hourly Administration - £75/h If you require assistance outside the scope of our management plans, with prior agreement, we offer an hourly administrative service at just £75/h

Last updated on Jun 12, 2025

How to Provide a Traceroute Using MTR: A Comprehensive Guide

MTR (My Traceroute) is a network diagnostic tool that combines the functionality of the traceroute and ping programs in a single network diagnostic tool. This guide will walk you through how to use MTR to provide a traceroute. Step 1: Install MTR MTR may not be installed on your system by default. Here's how to install it: On Ubuntu/Debian: Open a terminal and type: sudo apt-get install mtr On CentOS/RHEL: Open a terminal and type: sudo yum install mtr On macOS: If you have Homebrew installed, open a terminal and type: brew install mtr Step 2: Run MTR To run MTR, open a terminal and type: mtr Replace with the hostname or IP address you want to trace. For example, if you wanted to trace the route to google.com, you would type: mtr google.com Step 3: Interpret the Results MTR will start running and display a live updated report. Each line of the report represents a hop in the route. Here's what the columns mean: - **Host: **The hostname and IP address of each hop. - **Loss%: **The percentage of packet loss at each hop. - **Snt: **The total number of packets sent to each hop. - Last/Avg/Best/Wrst/StDev: These columns show various timing statistics for the packets sent to each hop. Step 4: Provide the Traceroute You'll need to stop MTR and copy the results to provide the traceroute. Press Ctrl+C to stop MTR. Then, select the text in the terminal and copy it. You can then paste this text into an email, a support ticket, or any other form of communication. Remember, MTR provides a live, ongoing traceroute, so the longer you leave it running, the more accurate the results will be. It's recommended to let MTR run for a few minutes before stopping it and copying the results.

Last updated on Jun 12, 2025

Add monitoring scripts to server for monitoring top, iostat (server-status)

Quick Installation mkdir -p /var/log/server-status; wget -O /var/log/server-status/getstats.sh [https://gitlab.com/brixly/file-dump/raw/master/getstats.sh](https://gitlab.com/brixly/file-dump/raw/master/getstats.sh); echo "* * * * * root /usr/bin/flock -n /var/run/cloudlinux_getstats.cronlock /bin/sh /var/log/server-status/getstats.sh >/dev/null 2>&1" > /etc/cron.d/getstats.sh; chown 655 /var/log/server-status/getstats.sh; yum install perf -y; Log Location The logs will be located in /var/log/server-status

Last updated on Jun 12, 2025