Kolab now integrates with Seafile, a cloud storage system. Find out what benefits this brings Plesk Premium Email customers.Continue reading
So Plesk Onyx came along and it had implemented NGINX caching. Naturally I was curious and removed all my customizations. Then I started to compare the website performance with the inbuilt NGINX caching, other caching methods, and the Speed Kit extension that speeds up websites.
This was the variety of tests and configurations I made on the platform:
|Platform||Web Server Configuration||Caching Engine Configuration|
|1||WordPress Website on Plesk Onyx 17.8.11||Proxy Mode and Smart static files processing turned ON||NGINX Caching OFF|
|2||WordPress Website on Plesk Onyx 17.8.11||Proxy Mode and Smart static files processing turned ON||NGINX Caching ON|
|3||WordPress Website on Plesk Onyx 17.8.11||Proxy Mode and Smart static files processing turned ON||NGINX Caching OFF Redis Caching ON|
|4||WordPress Website on Plesk Onyx 17.8.11||Proxy Mode and Smart static files processing turned ON||NGINX Caching ON Redis Caching ON|
|5||WordPress Website on Plesk Onyx 17.8.11||Proxy Mode and Smart static files processing turned ON||NGINX Caching OFF SpeedKit Ext. ON|
|6||WordPress Website on WordPress.com||Everything in default mode||—|
|7||WordPress Website on Vesta CP||NGINX Web Template turned ON with the WordPress2 Option selected||—|
I installed the Plesk server (version 17.8.11 update 25) on the Digital Ocean droplet on CentOS7 with 2 GB RAM. Next, installing the Redis server as it was. I plugged in Redis Object Cache with its default settings. And had no additional parameters in additional NGINX directives.
There was PHP version 7.2.10 with default settings and the “FPM application served by NGINX mode. And the VestaCP server installed on Digital Ocean droplet on Ubuntu 16.04.
As a test page, I used a typical blog post with lots of photos. Hosted both on the server and externally, with a small chunk of text and one comment.
Testing on the Plesk Onyx Platform
For testing, I used the httperf command line tool (with the same launch parameters) and a well-known online testing system GTmetrix.com. From the GTmetrix.com reports, I chose the following parameters:
Time to First Byte (TTFB) is the total amount of time spent to receive the first byte of the response once it has been requested. It is the sum of “Redirect duration” + “Connection duration” + “Backend duration“. This metric is one of the key indicators of web performance.
Once the connection is complete and the request is made, the server needs to generate a response for the page. The time it takes to generate the response is known as the Backend duration.
- Fully Loaded Time: RUM Speed Index is a page load performance metric indicating how fast the page fully appears. The lower the score, the better.
- PageSpeed Score
- YSlow Score
The httperf utility was launched with the following parameters:
The creation of 100,000 sessions (5 calls each 2 seconds) with speed 1,000. And here, the following markers received with httperf were the most interesting:
- Connection rate – the real speed of creating new connections. It showed the server ability to process connections.
- Request rate – the speed of processing requests, in other words a number of requests a server can execute per second. It showed web app responsiveness.
- Reply rate – an average number of server replies per second.
Plesk Onyx Test Results
Clearly, there’s an ocean of tools and solutions to test website performance. Some more complete and respected than others. But even the tools I used allowed me to come to pretty objective conclusions. The test results are summarized in the table below with the green buts highlighting the best values of the parameter, and the red – the worst.
And so, after analyzing the received data, we can conclude the following:
- Unchanged PageSpeed and YSlow Scores
PageSpeed and YSlow Score metrics in Plesk remain absolutely the same, no matter the configuration. Therefore, they don’t depend on caching or other server settings like for code optimization, image size, gzip compression and CDN usage.
- Caching is essential for speed
No caching on Plesk at all gives the worst time metrics. Fully Loaded Time and TTFB dramatically increase. Websites with the turned off caching are significantly slower.
- NGINX and Redis are a successful combo
Comparing caching methods, NGINX caching used in Plesk seems better than Redis Cache. It’s possible the default Redis Cache configuration doesn’t let us achieve a higher performance. It’s not quite clear how the used combination of both caching tools works, but it gives quite alright TTFB и Backend duration metrics.
- WordPress performance suffers
WordPress.com shows the worst performance results. However, by default, it doesn’t actually offer bad optimization for the PageSpeed Score.
- Vesta and NGINX mean extremely fast page load
Using the lightweight Vesta control panel with the turned on NGINX Web Template + php-fpm (wordpress2) designed for WordPress hosting gives great speed results. Even more, for WordPress hosting, VestaCP has custom NGINX web templates including NGINX caching support.
Moving to a new DigitalOcean Droplet
I deployed Plesk to the new DigitalOcean droplet using Web Installer as it doesn’t require me to go to the server via SSH and do all the stuff in web interface. This recent migration from my VPS to a new DigitalOcean droplet gave me new data for my last Plesk experience. All in all, the migration was successful with minor warnings, which in most cases I resolved using migration wizard suggestions.. The bottom line is that Plesk with turned on key features and settings gives very good results for your website.
Also, I strongly recommend you turn on NGINX caching with your Plesk if you’re seeking a simple and reliable way to speed up your website. You won’t need to set up any difficult configurations. And web pros can make the most of Plesk by fine-tuning as they see fit. That’s what it’s made for. their right.
Finally, my story was aimed at people without professional knowledge who simply want to use built-in Plesk features. So I hope that this story will be good reason for you to login to Plesk and take a fresh look.
Plesk first crossed my path when it came packaged with web hosting acquired from a Russian provider. At the time it was version 12.0, but I never paid any attention to it until I discovered that part of its service was domain names registration.
Starting Off with Plesk
It couldn’t hurt to register a couple of domains for myself, and so I did. I added them to Plesk, and configured the DNS records. Now these websites loaded default web pages. Then, as I already had websites hosted in Plesk, I thought “Why not use mailboxes registered on my own domains?”. So I went and created a couple of mailboxes and configured Roundcube webmail.
But it was all just personal use until I occasionally started to use this complete infrastructure as a sort of a test server. Why? In order to solve tasks related with questions from forum users. And so, my Plesk server operated like this for a while without any use cases development. That is, until the start of 2017 – when I spontaneously took a closer look at something I had available, but which was laying there unused this whole time.
Easy Building on the Plesk Platform
I realized that I could now use my own platform for my personal blog. It didn’t take me long to choose WordPress as I had previous experience with it. What’s more, the new Plesk Onyx had integrated its WordPress Toolkit, which looked promising. After getting a license with additional extensions, I started building – themes, plugins, you name it, before publishing my first posts.
Plesk is also built for multiple domains. So when my famous, American Instagrammer friend needed a website to develop her “Travelling with kids” idea, I offered my hosting platform.
Within Plesk, I created a personal account for her and subscriptions with two domains. One was used to host her website, and the other to host her personal mail.
She quickly learned how to use the WordPress admin dashboard and Plesk. She created mailboxes and installed WordPress plugins and themes. Then created posts and moderated comments. Which I believe says a lot about how easy Plesk’s interface is.
As thousands of subscribers were actively visiting both our blogs, it was time to pay more attention to Plesk server maintenance. And later, to server optimization, creating regular work in the Plesk interface and even more in the Linux command line. But more on that later. Before that, there were common issues of all sorts that I had started to face.
Issues uncovered and solved by using Plesk
- Service downtime
Various services like httpd and MySQL stopped every now and then. I managed to solve this by turning on and configuring Watchdog.
- Memory usage
Then Health Monitor started to constantly notify that MySQL consumes RAM.
- Basic MySQL settings
I had optimized operation modes of MySQL via CLI and thought it would benefit to have at least some basic settings of MySQL optimization in the Plesk interface. Eventually, RAM for VPS was increased from 1 to 2 GB, solving the issue.
- Frequent updates
Email notifications about new WordPress plugins made me login to Plesk often. I am one of “update-it-all” types and very meticulous when it comes to installing the latest software versions. The Smart Updates feature in WordPress Toolkit solved this task.
- Extensions accessibility
I used to find accessing my installed extensions inconvenient. So it was great when WordPress Toolkit had installed extension icons in the left menu.
Speeding up and hardening the WordPress Website
During an internal contest for the best WordPress website hosted in Plesk, I focused on two goals. I wanted to make my WordPress website the fastest and the most secured.
To achieve the A+ note on ssllabs.com, special NGINX parameters became necessary. They were installed via Additional nginx directives and the /etc/nginx/conf.d /ssl.conf file. An attempt to maximize the speed of my website powered by NGINX was a special matter.
At that time, NGINX caching wasn’t yet implemented in Plesk. So I tried various caching solutions, such as redis, memcached, and the very same NGINX caching. All via the CLI, of course, but with the help of customized settings.
It didn’t take long to realize the NGINX version shipped with Plesk was not suitable to use with trendy acceleration technologies. Ones like caching, the brotli compression method, PageSpeed Module, or TLS1.3. Even the Plesk Forum also raised this issue as it seemed to occupy the minds of advanced users.
The result was publishing different ways how to compile the latest NGINX versions. Thus, supporting modern technologies, and substituting the NGINX version shipped with Plesk for a custom one. I also joined forum users in compiling and optimizing NGINX builds for my Plesk server, all during the contest.
In the end, I got the speedy WordPress site I wanted powered by customized NGINX with Redis caching. All was well until Plesk Onyx was released. See what happened next in part 2 of my Plesk experience story tomorrow.
What a journey! But we couldn’t have achieved so much without the engagement and support of our customers and partners. You drive us to develop better products, service and solutions. So let us take a moment to thank you for being great, and present Plesk’s top wins of the year.
1. New Plesk Onyx 17.8 Release
We took your feedback and gave Plesk Onyx a huge update in March. Thus, better aligning our complete platform with the way web professionals work. We focused on five main areas: Site performance and speed, SEO tools integration, WordPress Toolkit efficiency and ease, tighter security and Cloud integration.
2. Major Industry Events
From Cloudfest in Germany to WordCamp Europe in Serbia, to J and Beyond in Germany and WordCamp US in Nashville. These were only a few of the events that allowed us to connect with new and old friends this year. Plus, learn and grow from the communities and the great minds we met. We even organized our own successful APAC Partner event in Singapore to better connect and exchange ideas with our partners.
3. SolusVM Joins the Group
London-based SolusVM from OnApp is a virtual server management system that offers Infrastructure-as-a-Service hosting. And is trusted by thousands of service providers. Plesk vowed to carry on its growth strategy and elevate it from a single server control panel to a future-proof cloud platform. In the same way, SolusVM boosts Plesk’s offering as it now becomes a complete solution, thanks to combined skills and resources.
4. New Plesk Editions
If Plesk Web Pro, Web Admin and Web Host Editions didn’t suit your needs exactly, we now also have Plesk WordPress Edition and Plesk Business and Collaboration Edition. Providing even more solutions, to more users. Plesk WordPress Edition offers Managed WordPress Hosters a complete solution to manage, secure and grow their business. While Plesk Business and Collaboration Edition combines all the features of a corporate grade collaboration suite. The ready-to-use solution includes communication, performance and security tools too.
5. More Partner Success
This year, in our efforts to get closer to Partners and provide better solutions, we refocused our Partner Success Team. Thus, better serving our partners, no matter where or how big. Providing more resources and support, better initiatives and offers, dedicated partner events and much more. Want to become a partner too and reap our special benefits? Get more info on our Partner Program page or get in touch.
6. Plesk Extensions of the Year
We’re constantly searching for new ways to deliver better solutions to plug into your Plesk. And so we released loads of extensions this year, both in-house and from partners – many available for free. We’ve made leaps forward in providing add-ons for web development and apps, security and monitoring, backup, Cloud, DNS, and more. Check out our full extension catalog to see what’s new – and what you can benefit from
Now that we’ve had a look back at the good stuff, we can continue flying forward. We hope to carry on exceeding expectations in 2019. So from all the Plesk Team: Thank you – and we’ll see you next year!
See what Smart Updates for WP Toolkit on Plesk Onyx maintains your site and how AI technology helps you make the right update choices.Continue reading
Here’s a comparison of the latest Plesk security extensions we released this year, protecting your sites from threats and available for your Plesk platform.Continue reading
Keeping a development team running smoothly can be tough as nails. Find out how a solution involving Plesk for Git Hosting eliminates this headache.Continue reading
So as of today 16:00 UTC / 18:00 CEST, the new Roundcube responsive skin by Kolab will go live for Plesk Premium Email customers. And because Plesk has contributed greatly to its creation, we get to be the first to give it a whirl! Here’s why you should be excited about Kolab’s new feature.
About the new Roundcube Responsive Skin
The Elastic skin is, as you’ve heard by now, responsive. Hence, it adapts its interface to the real estate available to your device. Regardless if you’ve got the tiniest mobile phone, a tablet or a large desktop system.
Naturally, if you’ve already got Plesk Premium Email, you’ll get the responsive skin. And since you’re a Plesk Premium Email customer, you’ll get it immediately after the launch this afternoon. Before all other Roundcube users worldwide. You’ll also have calendar, tasks, notes, and file cloud features available for all kinds of device sizes.
Now, since we are the first to test this new feature, Kolab would like our feedback on which skin version wins: Is it the current “light” version or the “darker” stuff? Let us know on Facebook and Twitter.
Here are the roll-out details
The new Roundcube Responsive skin comes in these package updates:
- roundcubemail 1.4
- Note: This update makes the “Out of Office” interface available.
- roundcubemail-plugins-kolab 3.4
- roundcubemail-plugin-contextmenu 3.0
- roundcubemail-skin-plesk 0.4
- roundcubemail-skin-plesk-larry 0.3
If you install Plesk Premium Email or have a subscription with Plesk Premium Email permission enabled, your systems will update. And you’ll enjoy the new responsive skin on your Roundcube webmail installations.
Getting new Roundcube Responsive Skin
If you have enabled automatic system updates in your Plesk installation you’ll receive the new responsive skin automatically. Otherwise you can install the updates via the Plesk’s UI by using the System Updates tool (“Tools & Settings” -> “System Updates”).
Of course the update can also be installed from the command line:
Via Plesk Update Manager
# /usr/local/psa/admin/sbin/pum –verbose –update –unsafe
Using the native CentOS 7 / RHEL 7 package manager:
# yum -y update
Using the native Debian 8 / 9 or Ubuntu 16.04 package manager:
# apt-get update ; apt-get -y upgrade kolab-plesk
How to switch back to the older skin version
You’ll be able to switch back to the old skin in any of the following ways:
- Edit /etc/roundcubemail/config.inc.php, and change $config[‘skin’] from ‘plesk’ to ‘plesk-larry’.
This change applies globally and to all existing customers, current and future.
- Provide a file /etc/roundcubemail/<VHOST_NAME>/config.inc.php with the following contents. The vhost name is the value $_SERVER[‘HTTP_HOST’] header used, i.e. ‘webmail.kolab-customer.maipo.whd.pxts.ch’.
$config[‘skin’] = ‘plesk-larry’;
As may be clear, this change only applies to the specific domain’s webmail interface.
- (Not recommended): Unlock user’s discretionary selection of skins by removing the ‘skin’ item from the $config[‘dont_override’] in /etc/roundcubemail/config.inc.php. This would apply globally, and can be selectively applied by ejecting ‘skin’ from $config[‘dont_override’] on a per-vhost basis such as described above;
$config[‘dont_override’] = array_diff(
We don’t recommend you do this, however, because the following skins would become available for selection:
- “Plesk Premium Email (Larry Version)”,
- “Plesk Premium Email (Responsive Version)”
A system administrator can choose to make the selected skins unavailable by changing the chmod on /usr/share/roundcubemail/skins/<SKIN> to 0700. But this is not supported in the packaging, so you’d have to repeat it after any updates are applied.
Meanwhile, you could be getting too much trash in your inbox. Can SPF, DKIM and DMARC free you from junk emails? Learn more.