• Go to your phpMyadmin.

• Choose the database you want to replicate from the drop-down menu (by clicking on the database from the phpMyAdmin home screen).

• Select the Operations tab once you’ve entered the database.
• Go to the section where it says Copy database and scroll down.
• Fill in the new database’s name.

• To replicate everything, select structure, and data. You can also choose Structure Only if you only want the columns and not the data.
• To build a new database, check the box CREATE DATABASE before transferring.
• Make sure the box Add AUTOINCREMENT value is checked.
• To continue, click the Go button.
• Select the Home icon.

• In the left column, you’ll see your new database listed. If you look inside, you’ll notice that the database is a duplicate of the prior one.

The post In phpMyAdmin, how can I copy a database? appeared first on cPanel Plesk.

We assist web hosts, VPS providers, and cloud providers in preventing such assaults and ensuring high service availability. Our web server management services include server load mitigation and attack mitigation. We’ll go through how to recover from an xmlrpc.php attack and how to avoid it in this article.

How do you recover from a heavy load?

When the server is overloaded, the first concern is to get everything back to normal. You’ll need to block access to xmlrpc.php at the Apache connection level to accomplish this. By adding the following directive to the Apache configuration file and restarting the server, you may achieve this:

Files ~ "xmlrpc.php"
  Order allow,deny
  Deny from all
Files

How can you prevent xmlrpc.php from being abused?

Disabling xmlrpc.php access is only a temporary fix, as many websites rely on it to track blog ping-backs and do remote posting. As a result, the approach is to stop attacks based on a shared signature. The following is an example of an xmlrpc.php attack log:

37.203.208.49 - - [21/Jan/2015:15:37:54 -0500] "POST /xmlrpc.php HTTP/1.0" 503 4859
37.203.208.49 - - [21/Jan/2015:15:37:55 -0500] "POST /xmlrpc.php HTTP/1.0" 503 4859
37.203.208.49 - - [21/Jan/2015:15:37:57 -0500] "POST /xmlrpc.php HTTP/1.0" 503 4859
37.203.208.49 - - [21/Jan/2015:15:38:02 -0500] "POST /xmlrpc.php HTTP/1.0" 503 4859
37.203.208.49 - - [21/Jan/2015:15:38:11 -0500] "POST /xmlrpc.php HTTP/1.0" 503 4861
37.203.208.49 - - [21/Jan/2015:15:38:13 -0500] "POST /xmlrpc.php HTTP/1.0" 503 4861
37.203.208.49 - - [21/Jan/2015:15:38:18 -0500] "POST /xmlrpc.php HTTP/1.0" 503 4861

A genuine request will have a referrer field, whereas assaults will typically not have one. As a result, such requests can be blocked using a firewall rule. This is when Mod security comes in helpful. To the mod security rule set, add the following:

#Block requests to xmlrpc.php with no referring URL
SecRule REQUEST_METHOD "POST" "deny,status:401,id:5000900,chain,msg:'xmlrpc request blocked, no referer'"
SecRule &HTTP_REFERER "@eq 0" "chain"
SecRule REQUEST_URI "xmlrpc.php"

Installing a plugin like “xmlrpc assaults blocker” on dedicated servers with a small number of WordPress sites may be easier and more versatile.

The post How to recover & prevent (Apache web server) from XMLRPC attacks appeared first on cPanel Plesk.

First-level checks:

• Make sure you typed your website address into the address bar of your browser correctly. e.g.http://www.example.com
• Is your internet connection up and running? Are you able to access other websites, such as http://www.google.com? If it doesn’t work, restart your router or computer.
• Is it possible to visit the website using a secondary browser if you have other web browsers installed on your computers, such as Chrome and Firefox or Internet Explorer?
• Have you looked at your Internet Service Provider’s status page to see if any service reports are available?
• To discover if any service outages have been reported, go to our status page.

Secondary inspections:

• Check to determine if the website in question is available to the general public: Detector of Downfall (do a search).
• Are you able to “ping” your website from other sites, such as this one:http://tools.pingdom.com/ping/
• Is it possible to access the site through a proxy page (a virtual machine that belongs to someone else), such as this one:http://kproxy.com/
• Are you able to access the cPanel for your website? (control panel).
• Have you tried using your cell phone network to view your website? (e.g. different from your wifi broadband)
• Have you checked to see if data roaming is enabled if you’re using mobile data?

Troubleshooting Steps:

If you can access your website using the procedures above, it’s likely that the problem isn’t with the website or the server, but rather with something local to you.

In that situation, please attempt the procedures below to “clear the cache” – The cache is a collection of records that can become stale or corrupted over time and require refreshing.

Clearing your browser’s cache / cookies

Have you tried deleting the cache and cookies on your computer?

• In the upper right corner, click the Chrome menu icon.
• Select More tools -> Clear browsing data from the drop-down menu.
• Select Beginning of time from the top menu.
• Make sure that Cache is the only option in the pop-up window.
• To clear browsing data, click the Clear Browsing Data button.
• If the problem persists, follow the instructions above and restart the computer.
• For additional information on How and Why to Clear Your Cache, please visit the Google Chrome Support page.

Flush the DNS on your local machine

Depending on your computer’s operating system, flushing DNS is done in a different way. Let’s go over the steps for each of the primary systems.

How to Flush DNS in Windows 10

The steps for flushing your DNS cache on Windows 10 are as follows. These procedures should work with Windows 8.1 as well.

• To begin, press the Start button. In the lower-left corner, it’s the Windows logo.
• Choose Command Prompt from the drop-down menu.
• You can also open the command prompt console by pressing the Windows and R keys at the same time and typing cmd.
• A popup window may appear, asking if you want Command Prompt to make changes to your computer. Select Yes if you do.
• If you’re prompted for an administrative password at this stage, you’ll need to contact your system administrator.
• Type ipconfig /flushdns in the command prompt window.
• Press Enter.
• A notification should appear confirming that the DNS Resolver Cache has been cleared successfully.

Restart your modem

Your Router (also known as a modem or simply “the box on the wall”) can become stuck with outdated or out-of-date internet records (the cache!). A restart may clear out the old information in the cache, which is the simplest method to see if this is the problem.

• Locate the power button on your router or the wall switch.
• Turn off the router for 10 seconds before turning it back on.
• Wait for your network to reconnect before attempting to access the website again.

Contact Internet Service Provider

Your Internet Service Provider (ISP) may be doing some caching on your behalf, similar to how your web browser and router keep a cache of recent online pages. Even when you use refresh to retrieve new data from a webpage, the pages may appear to be outdated in some (rare) instances. This could be because your Internet Service Provider’s cache isn’t cleared frequently enough, or because there’s an issue. It’s possible that their hardware isn’t up to date enough to serve the most recent web pages in this scenario.

• When you run into this issue, you’ll need to contact your ISP to get it resolved.
• Inform them if you believe their cache is broken.
• Check with them to see if they have any explanations.

Getting Further CreativeON Support

If you haven’t been able to resolve the problem using the procedures above, please submit a support ticket so that we can help you.

It is incredibly helpful if you can offer as much information as possible when contacting us:

• Date, time, and type of the error.
• What steps have you taken to address the issue?
• Provide detailed instructions for replicating the error.
• Take a picture of any error messages you encounter.
• Please provide us with your IP address so that we can start tracing your computer.
• Who is your Internet Service Provider (i.e., to whom do you pay your broadband bill)?

The post Why I can’t access my website? appeared first on cPanel Plesk.

Ping Test

The PING command is used to test a network connection’s connectivity and latency. The PING command delivers data packets to a specified IP address and then calculates the time it takes for the specified computer or device to respond.

Windows 10-11 (for Windows 8 and Mac, see below)

• Click START, then RUN to open the command window. Press Enter or click OK after typing CMD.

• In the command dialogue window, type PING.
• Once, press the spacebar.
• Ping the IP address or website address you want to ping. For example, to ping your own website, type “mywebsiteaddress.com” (without quotes) – REPLACE THIS WITH THE WEBSITE ADDRESS OF YOUR CHOICE.
• Return to your keyboard or press “Enter.” If the website is up and running, you should receive responses from the server you ping with the following information:

• The Internet Protocol (IP) address.
• The total amount of data sent.
• In milliseconds, the time it took.
• Any data loss while in transit.
  
  You can now go to the following stage, which is to conduct a TRACERT test (see below)

Traceroute Test

The TRACERT programme performs a similar test to PING, but instead of reporting the connection time, it examines the exact server hops required to link your machine to the server.

After running the PING test, you should already have the CMD prompt dialogue box open.

1. In the command prompt window, type “TRACERT” (without quotes).
2. Once, press the space bar.
3. Enter the IP address or website address you’d want to check. For example, if you wish to verify your own website, write “mywebsiteaddress.com” (without quotes) – REPLACE THIS WITH THE WEBSITE ADDRESS OF YOUR CHOICE.
4. Return to your keyboard or press “Enter.” If the website is up and running, you should receive responses from the server you ping with the following information:

• The number of hops it takes for your machine to reach the server

How to send this information to your Webhost

Right-click on the Cmd Prompt TITLE BAR and select Properties.

Select Edit and then All.

Right click on the TITLE BAR again, and select EDIT > COPY this time.

Then copy and paste the output into an email message or a TXT file.

You should now be able to see all of your PING and TRACERT test results. If you don’t, or if you’re having difficulties pasting, try copying the result again.

The CMD prompt conversation window can now be closed safely.

The technique is similar whether you’re running Windows 8 or a Mac.

Windows 8

• Go to the Windows 8 desktop. Place your mouse in the screen’s bottom-left corner. 
• Click the Start icon with the right mouse button.
•  You may also do this from Windows 8 Start menu.
• A pop-up menu will appear after right-clicking the Start symbol. To begin, press the Run button.
• In the Run window that displays, type “cmd” (without the quotations).
• Follow the steps outlined in step 2 above.

Mac

Using the Network Utility OR the Terminal programme, ping your Mac directly.

• Open Network Utility (under Applications > Utilities in the menu bar).
• Continue with the steps outlined in step 2 above.

Start the ping programme. The ping of the network is repeatedly tested by the terminal. When you’re finished, press Ctrl + C to exit the Terminal ping test.

The post How to Ping & Traceroute Tests appeared first on cPanel Plesk.

• Now type Remote Desktop into the search box and click on it.

• Click Connect after entering the IP address of your Virtual Machine.

• Click OK after entering the Administrator Username and Password.

• Type cmd once you’ve connected to your VM/Remote Desktop.

• Right-click the command prompt and select Run as administrator from the context menu.

• Creating the IPv6 addressing rule

Now copy and paste the following command into the command prompt and press the Enter key:

• netsh advFirewall Firewall add rule name=”OSRadar Rule PING IPv6″ protocol=icmpv6:8,any dir=in action=allow

• We can now test it by pinging it from a remote computer:

• Type command in the CMD to disable the exception for IPv4 addresses:

• Please type the following command if IPv6 is being addressed:

netsh advFirewall Firewall add rule name=”OSRadar Rule IPv6″ protocol=icmpv6:8,any dir=in action=block

• To see every rule in the system in detail, run the command below:

netsh advFirewall Firewall show rule name=all

• Report in detail

The post Enable and disable ICMP PING in Windows 10 Firewall appeared first on cPanel Plesk.

Typically the error looks as below:

Response: 530 User cannot log in, home directory inaccessible.
Error: Critical error: Could not connect to the server

Usually, this error occurs due to incorrect IP assigned to the domain in Domains > Yourdomainname.com > Hosting & DNS > Web Hosting Access.

If you run the following command into SSH you will see the error:

#plesk repair ftp -y

Checking all domain names resolve to appropriate IP addresses
The domain name Yourdomainname.com resolves to another IP address (104.156.48.165) ……………………………………………………. [WARNING]

To fix this error:

1. Log into Plesk

2. Go to Domains > yourdomainnanme.com > Hosting & DNS > Web Hosting Access

3. Then, select the IP address that resolves globally for the domain

4. Finally, click OK

The post “530 user cannot log in home directory inaccessible” error in Plesk appeared first on cPanel Plesk.

type=AVC msg=audit(1524598331.078:35761): avc: denied { read } 
for pid=450 comm="postfix-srs" name="secret" dev=dm-0 ino=136160 
scontext=unconfined_u:system_r:postfix_master_t:s0 tcontext=unconfined_
u:object_r:mail_spool_t:s0 tclass=file

1- Log in to the server via SSH

2- Install audit2allow utility:

# yum install policycoreutils-python

3- Create allows policy for postfix-srs:

# grep postfix-srs /var/log/audit/audit.log | grep denied | 
audit2allow -M postfix-srs

# semodule -i postfix-srs.pp

The post Error to send emails: Unable to open file /var/lib/plesk/mail/srs/secret: Permission denied appeared first on cPanel Plesk.

Install WordPress Locally on Windows

To install WordPress locally on Windows, You need to install a free software called WampServer on your local system.

After downloading the software, You can install it like any other Windows software.

During the installation process, WampServer may ask you to choose the default browser. Just click on the “Open.” There is no need to specifically choose a default browser.

As we are not going to configure PHP mail at this time, let’s keep the settings on default and click on the button “Next” in the “PHP Mail Parameters” window to continue.

If you are prompted for Firewall permissions, simply click on the button “Allow Access.” Once the installation completed, select the checkbox “Launch WampServer now” and click on the “Finish” button.

Now WampServer will be launched and you can see that in the taskbar. If everything goes well, WampServer will let you know by changing its taskbar icon color to Green. You might have to wait a few seconds before the icon can change to green color.

To test it further, launch your favorite browser and enter “localhost” or “127.0.0.1” in the address bar and press the enter button. This will open the WampServer homepage.

Now we may proceed to install WordPress locally on Windows. Before that, we have to download the latest version of WordPress from their official website.

Once download completed, extract the “WordPress” zip folder to the location C:\wamp\www\. After extracting, rename the folder as per your choice.

Now, we need to create a database for the local WordPress site. To do that, left-click on the WampServer and select the option “phpMyAdmin” from the list of options.

The above action will launch the “phpMyAdmin” page. On the phpMyAdmin home page, select the option “Databases” from the top navigation bar.

To create a new database, enter the new database name and click on the button “Create” under the “Create Database” section.

Once the database has been created, you will see the new database in the list. Since we are done creating a database, close the page.

Now, type http://localhost/example-folder/ in your browser address bar and press the enter button. Don’t forget to replace, “example-folder” with your folder name. Now in the WordPress installation screen, select your language and click on the button “Continue.”

WordPress will ask you to add the database details. Just click on the button “Let’s go.”

In next screen, enter the database name and the username as “root” and click on the button “Submit.” WampServer by default has no root password. So there is no need for you to enter a password in the password field.

Now, click on the button “Run the Install” to start the WordPress installation process.

Finally, enter all the details like the site title, username, password, email address, etc.., and click on the button “Install WordPress.”

Now the WordPress installation process will be completed and you can just log into your new local WordPress site by click on the button “Log In.”

That’s all to do.

The post How to Install WordPress Locally on Windows appeared first on cPanel Plesk.

/var/www/vhosts/system/example.com/logs/proxy_error_log file:

Nginx support is enabled on the server:

/usr/local/psa/admin/bin/nginxmng -s
Enabled

We try to adjust client_max_body_size in /etc/nginx/nginx.conf but it has no effect. Actually, Value for client_max_body_size directive is overwritten on domain level and is insufficient.

To resolve this error:

Add the following directives to /usr/local/psa/admin/conf/panel.ini file to customize Plesk defaults:

[webserver]
nginxClientMaxBodySize = 2000m

If there is no /usr/local/psa/admin/conf/panel.ini file, You can create it from the sample file:

cp /usr/local/psa/admin/conf/panel.ini.sample /usr/local/psa/admin/conf/panel.ini

Now rebuild web server configuration files:

plesk sbin httpdmng --reconfigure-all

Please note: Execution of the above command could cause a significant downtime to the hosted websites if there are a big number of them. Perform such action during the maintenance timeframe
Adjust settings of PHP handler assigned to the domain. Go to Plesk > Tools & Settings > PHP Settings > X.X.XX FPM application in php.ini tab and adjust the following parameters:

post_max_size 2000m

upload_max_filesize 2000m

max_file_uploads 100

That’s all.

The post Uploading of big file size fails: client intended to send too large body appeared first on cPanel Plesk.

It can be installed using the Plesk Installer or via the Plesk Extensions catalog.

Here are the few things you will need before starting migration:

• A domain name or IP address that resolves to your old server.
• The root password for your old server.
• A shared IP (as opposed to exclusive) available on your new server. See Shared and exclusive IPs in Plesk for details.
• Your IP address should also be set to shared on the old server.
• You also need to have a new IP address on your new server. You cannot use the same IP(s) that you had previously.

Now we start by installing the extension through either the Plesk Installer or Plesk Extensions Catalogue.

1. Log in to the Plesk control panel and look for Extensions in the menu on the left side of the screen.

2. Open the extensions catalogue and click the install icon next to Plesk Migrator.

3. Once installed, open the migrator extension and click Start New Migration. You should now see the New Migration form.

Panel Type: Select the panel that you’ll be migrating from. Please note: When migrating between Plesk services, the migration will fail if the receiving server’s version of Plesk is lower than the host server.

Address: This is the ip address of the server that you’ll be migrating from. Make sure that the ip address must be set to shared or the migration will fail.

Root Login: In most cases this will simply be “root” or “Administrator“

Authorization: Choose either root login or SSH keys. If you choose to use SSH keys to migrate, make sure that you know where the keys are located on the target server. /root/.ssh/id_rsa is the default location.

Root Password: The root password of your server.

SSH Port: The default SSH port is 22, but it is often changed for security purposes. You can locate your SSH port number in /etc/ssh/sshd_config.

Temp Directory: It is location where temporary files will be stored during the migration.

4. Once you’ve given all the migration, click Prepare migration. Plesk will now verify if it’s able to connect to the remote server and the setup is compatible with a migration.

5. Once Plesk verify your settings, click Start Migration. This process may take several minutes, Depending on the amount of data being migrated.

6. Once the migration completes, you will be able to access and verify your site data.

The post How to install and use plesk migrator extension appeared first on cPanel Plesk.