WooCommerce Server Requirements


The first step insetting up your WooCommerce-powered online store is to install WordPress and the WooCommerce plugin itself. But before doing so, you should check that your hosting environment meets our minimum requirements. These are:

  • PHP 5.6 or greater
  • MySQL 5.6 or greater
  • WooCommerce 2.5 requires WordPress 4.1+
  • WooCommerce 2.6 requires WordPress 4.4+
  • WP Memory limit of 64 MB or greater (128 MB or higher is preferred)


You should also check WordPress minimum requirements.

Optional Items
  • Some other optional things that may be required include:
  • CURL or fsockopen support for PayPal IPN
  • Some of our extensions require SOAP support
  • An SSL certificate if you wish to install direct payment gateways
  • Multibyte String support if you’re running a non-english store
  • If you want WordPress pretty-permalinks, there are some additonal requirements listed here
  • You can check if your server has the items listed above after installing WooCommerce from the System Status page.

You can check if your server has the items listed above after installing WooCommerce from the System Status page.

Moving Hosts

Need a new host? Check out our hosting here or dedicated WordPress web hosts listed here.

Domain Name 60 Day Lock

Domain lock
Domain lock

To prevent domain name theft, ICANN requires that domain names be prevented for transfer for 60 days in certain situations:

  • Domain name is within 60 days of initial registration
  • Domain name is within 60 days of a previous transfer

In addition, certain registrars may have procedures to prevent transfer for 60 days as well. For example, the registrar GoDaddy places a 60 day lock on any domain name when the whois information is modified. However, as discussed on Domain Name Wire by Bobdobbs (and verified by DomainSherpa), “The 60 day lock can be overridden by a supervisor if you really NEED your domain transferred.”

However, a domain can be sold and transferred during the 60-day registrar lock. Although the domain cannot typically be transferred to an account outside of your registrar, it can be “pushed” to another account within the same registrar. To do so, the buyer must have an account at the current registrar. The seller then uses the buyer’s registrar account login name and/or account number during the transfer.

What is DomainKeys


What is DomainKeys – DomainKeys is an email authentication technology developed by Yahoo, and is primarily used as an additional anti-spam and anti-phishing method.

How DomainKeys works

  • Sending emails


The domain owner generates a public / private key pair to use for signing all outgoing messages (multiple key pairs are allowed). The public key is published in DNS, and the private key is made available to their DomainKey-enabled outbound email servers.

When each email is sent by an account within the domain, the DomainKey-enabled email server automatically uses the stored private key to generate a digital signature of the message. This signature is embedded as a header in the sent email, and the email is sent on to the target recipient’s mail server.

  • Receiving emails


The DomainKeys-enabled receiving email server extracts the signature and claimed From: domain from the email headers and fetches the public key from DNS for the claimed From: domain.

The public key from DNS is then used by the receiving mail server to verify that the signature was generated by the matching private key. This proves that the email was indeed sent by, and with the permission of, the claimed sending From: domain and that its headers and content weren’t altered during the transfer.

The receiving email server applies the local policies based on the results of the signature test. If the domain is verified and no other antispam tests catch it, the email can be delivered to the user’s inbox. If the signature fails to verify, or there isn’t one, the email can be dropped, flagged or quarantined.


How to use a Microsoft Access database on Windows Plesk Hosting

Uploading your database

Login to your the Plesk Control Panel and open the File Manager.

Open the private folder and select Add New Folder.

Click the Browse button and location the database file (*.mdb) file from your local computer.

Press the OK button to upload it.


Setting up a database connection

Click on Home to return to the Home page and select ODBC Settings under Services.

Click on the “Add new ODBC DSN” button

Enter the name of the new connection for the database uploaded in the previous steps (You must only use letters and numbers – no spaces). You can also add an optional description.

From the drop down, select “Microsoft Access Driver (*.mdb)” and click OK.

Enter the Database File Path, this will be in a format similar to: E:\inetpub\vhosts\<example.com*gt;\private\<uploaded_database.mdb> (See the section Finding the Database Path below) where example.com is your domain name and uploaded_database.mdb is the name of the database uploaded to the site. Normally the domain name will not include the www part.

The rest of the fields are optional and are normally not needed.

Click on the “Test” button and if the connection has been created correctly you will be shown the message “Connection Successful”.

If you do not see “Connection Successful” please check you have specifed the correct path (without the www). If you need to enter a password to open the database enter the appropriate username and password details.


Finding the Database Path

Save the attachment shown below “showpath.asp” and upload this to the ‘httpdocs’ folder for your website.

Browse to this page in your web browser http://www.example.com/showpath.asp (replacing www.example.com)

This should show you a path similar to C:\inetpub\vhosts\<example.com*gt;\httpdocs\showpath.asp

To create the path to your database remove the portion “httpdocs\showpath.asp” from the end and add “private\<uploaded_database.mdb>.

Once this is working, please remove the file showpath.asp from your website as it is no longer needed

CentOS 5 End of Life- Bye Bye


CentOS 5 – 6 months until End of Life

This notice was originally posted when CentOS 5 had one year of supported life left. It now has 6 months. You are encouraged to put your migration plans into action now if you haven’t already done so. CentOS 6 goes EOL in 2020, CentOS 7 in 2024.

As per the announcement upstream, http://rhn.redhat.com/errata/RHSA-2016-0561.html you should know that CentOS 5 now has one year of support life left. People using CentOS 5 are encouraged to start their migration process to a supported version.

It should be noted that, unlike RHEL, there is no extended support option for CentOS. Once RHEL 5 goes EOL upstream on March 31st 2017, there will be no further updates for CentOS 5 at all. Those using CentOS 5 and requiring more than 1 year of life are encouraged to investigate the RH extended support program although that will require a migration to RHEL 5 as it does not apply to CentOS 5.