Resources, Articles, Tricks, and Solutions in connection to Server Management Service

Trace email spamming in Plesk using php scripts

This article covers how to locate the mail spammer in a Plesk server which is a bit difficult when compared to #Cpanel servers.

To prevent spam being sent from your server, Plesk offers a tool that controls the sending of email messages. 

This tool gathers statistics about outgoing messages and prevents mail being sent when specified limits are exceeded. 

You can specify limits on outgoing mail at the following levels: mail server, service plan, subscription, domain, and mailbox.

Administrators can prevent outgoing spam by using limits on the number of outgoing email messages per hour. 

In addition, the administrator can easily determine the exact source of possible spam with the help of reports and notifications.


Types of Threats in Plesk:

Plesk introduces different limits for prevention of the following different types of threats:

1. Stolen mail accounts.

SMTP user account credentials can be stolen by malicious users when they hack a mail server by using a system vulnerability (for example, PHP vulnerability) or an application exploit (for example, exploit for an outdated WordPress version). Also, if customers use very weak passwords, their passwords can be obtained by using brute force tools.

You can prevent this type of threat by limiting the number of outgoing email messages from a mailbox.


2. Web scripts for malicious mass mailing.

A malicious user can use a Plesk customer account in order to create a website with a script that will distribute spam emails. Also, a malicious user can steal the FTP credentials of a customer account and upload a website with a mass mailing script via FTP.

You can prevent this type of threat by limiting the number of outgoing email messages from a domain.


3. Hacked system accounts on #Linux.

Malicious users can gain access to Linux system user accounts by using system or application exploits. After that, they can plant scheduled background tasks in crontab. Such scheduled tasks can run mass mailing scripts that spread spam mail.

You can prevent this type of threat by limiting the number of outgoing email messages from a subscription.


Best practices for sending outgoing mail from a #Plesk server:

1. Configure the #hostname for a Plesk server

Go to Tools & Settings > Server Settings and type in your server's hostname.

2. Enable SPF/DKIM/DMARC features

By default, a SPF DNS record is added to the domain's DNS zone during a domain creation, if this DNS record exists in the Plesk DNS Template.

Make sure there is a TXT record for SPF in domain's DNS settings at Domains > example.com > DNS Settings

3. Make sure that DKIM support is enabled server-wide in Plesk at Tools & Settings > Mail Server Settings.

4. A reverse DNS (rDNS) lookup returns the hostname of an IP address. Many mailbox providers, including Gmail and Yahoo!, will block email coming from a mail server that does not have rDNS in place.

To configure rDNS, a PTR DNS record should be created by the owner of the IP address. 

Contact your hosting service provider or Internet Service Provider (ISP) to get more details.

Read More


Optimize Magento Database to improve site speed

This article covers how to perform Magento #speed #optimization using open-source software. Basically, #eCommerce customers expect a website to load within 2 seconds.

Magento is a resource-heavy ecommerce platform that requires the right set of resources and configurations for optimum performance. 

Even if you have a sound infrastructure, there is a chance that your Magento powered store might be slow.


Developers who are responsible for maintaining the Magento stores generally make sure that they incorporate the best Magento 2 performance optimization practices into the projects. 

As a result, ecommerce stores perform at peak efficiency 24/7.


To achieve high speed it's very essential for your online store.


Importance of having speed boost of your #Magento site:

1. To increase traffic at your website.

2. To gain a customer preference to buy from your site only.

3. Increase in conversion rate.

Read More


Zabbix server cant connect to java gateway - Fix it now

This article covers how to fix Zabbix error "Server can't connect to java gateway" by making some changes in the server configuration files and restarting the Zabbix and java gateway. 

Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. 

This allows a fast reaction to server problems. 

Zabbix offers excellent reporting and data visualization features based on the stored data. 

This makes Zabbix ideal for capacity planning.

Read More


Redis Slow Log - More about it

This article covers how Redis Slow Log works. Redis Slow #Log is one of the best tools to debug and trace the Redis database. 

The Redis Slow Log is a system to log queries that exceeded a specified execution time. 

The execution time does not include I/O operations like talking with the client, sending the reply and so forth, but just the time needed to actually execute the command (this is the only stage of command execution where the thread is blocked and can not serve other requests in the meantime).


You can configure the slow log with two parameters: 

1. slowlog-log-slower-than tells Redis what is the execution time, in microseconds, to exceed in order for the command to get logged. Note that a negative number disables the slow log, while a value of zero forces the logging of every command. 

2. slowlog-max-len is the length of the slow log. The minimum value is zero. When a new command is logged and the slow log is already at its maximum length, the oldest one is removed from the queue of logged commands in order to make space.


Redis Slow Log configuration can be done by editing redis.conf or while the server is running using the CONFIG GET and CONFIG SET commands.

Available since 2.2.12.

This #command is used in order to read and reset the Redis slow queries log.


Redis slow log overview

The #Redis Slow Log is a system to log queries that exceeded a specified execution time. 

Slowlog, as its name, is used to record commands whose execution time exceeds limitation (a little slow).

The execution time does not include I/O operations like talking with the client, sending the reply and so forth, but just the time needed to actually execute the command (this is the only stage of command execution where the thread is blocked and can not serve other requests in the meantime).

The Redis SLOWLOG is used to help identify queries which are taking too long to execute.


You can configure the slow log with two parameters:

slowlog-log-slower-than tells Redis what is the execution time, in microseconds, to exceed in order for the command to get logged. Note that a negative number disables the slow log, while a value of zero forces the logging of every command. slowlog-max-len is the length of the slow log. The minimum value is zero. When a new command is logged and the slow log is already at its maximum length, the oldest one is removed from the queue of logged commands in order to make space.


The configuration can be done by editing redis.conf or while the server is running using the CONFIG GET and CONFIG SET commands.

Read More


Methods to reduce server load

This article covers tips to reduce server load. The load speed of websites mainly depends on the constant load that the server is maintained. 

Load expresses how many processes are waiting in the queue to access the computer processor. This is calculated for a certain period of time, and the smaller the number the better. 


Tips To optimize and speed up your server:

1. Enable caching.

2. Setup a fast reverse proxy.

3. Choose the right application server.

4. Fine tune your web server.

5. Turn on HTTP/2.

6. Defragment your database tables & optimize server settings.

7. Fix your DNS query speed.

8. Trim down your site's critical rendering path.


Why is your Website server slow?

The cause of slow servers usually lays with the web host. 

You could be having a slow site because you are hosted on a free web hosting. 

You are on a low quality hosting service with poor support. 

Or your site needs a higher spec hosting account with more resources eg a VPS.

A large volume of unoptimized images is usually the most common reason behind website slowness. 

High-resolution images can consume lots of bandwidth while loading. 

Uploading larger sized images and then scaling them down can unnecessarily increase the size of your web page – causing your website to load slowly.

Read More


MongoDB failed to load list of databases - Fix it now

This article covers how to resolve the error 'MongoDB failed to load the list of databases' can occur due to various reasons that include failed database user/password authentication, outdated Robo 3T version, and so on.

The error 'MongoDB failed to load the list of databases' means that you can't connect if there are no databases to list. 


To fix the error 'MongoDB failed to load the list of databases':

1. You can fix this issue with 1.2 connecting to a new mongo 4.2.

It's fixed when using robo3t version 1.3, which supports newer version of mongo.

2. You can create a database and a collection for it. 

Once you create a database and a collection, it works.

3. You will need to upgrade mongodb to the last version, so you can to connect in your local database.

Read More







Focus on your business, not your servers.

Click Here to Learn More