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

Domainkeys
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

CentOS5
CentOS5

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.

How to know your Server meets PayPal SSL Requirements

paypal-ssl
paypal-ssl

PayPal is upgrading the SSL certificates it uses to secure its sites and API endpoints. SSL certificates will need to be signed using the SHA-256 algorithm and VeriSign’s 2048-bit G5 Root Certificate.

PayPal’s service will discontinue the use of SSL connections that rely on the VeriSign G2 Root Certificate.

You can easily determine whether your server supports this new standard by logging into your server via SSH and running a single command:

openssl s_client -connect api-3t.sandbox.paypal.com:443 -showcerts | egrep -wi “G5|return”

If your server complies with the requirements, you will see a result similar to the following:

i:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2006 VeriSign, Inc. – For authorized use only/CN=VeriSign Class 3 Public Primary Certification Authority – G5
Verify return code: 0 (ok)

In that output, you will want to note the presence of two specific items:

  • A Certification Authority containing “G5”. Note that you may see several CA lines in your output; as long as G5 is included, your server is compliant.
  • A Verify return code of “0 (ok)”.

If both are present, your server is compliant and no further action needs to be taken.

If neither is present, then your server will need to have the G5 certificate bundle installed.

NOTE: CentOS 5 (and earlier) is not capable of supporting the new standard. If your server runs CentOS 5 (or earlier), it will need to be upgraded.

Google Webmaster Tools: An Overview

google-webmaster-tool
google-webmaster-tool

Google Webmaster Tools (GWT) is the primary mechanism for Google to communicate with webmasters. Google Webmaster Tools helps you to identify issues with your site and can even let you know if it has been infected with malware (not something you ever want to see, but if you haven’t spotted it yourself, or had one of your users tweet at you to let you know, it’s invaluable).

And the best part? It’s absolutely free. If you don’t have a GWT account, then you need to go get one now.

This guide to Google Webmaster Tools will walk you through the various features of this tool, and give you insight into what actionable data can be found within. (For more in-depth help, go toGoogle’s Webmaster Help.)

Highlights of Magento Edition 2.1.0

magento2-0
magento2-0

Magento edition 2.0.1 includes several exciting and new features:

Braintree Hosted Fields securely collect all sensitive payment information in checkout so merchants can qualify for the simplest set of PCI compliance requirements. Merchants retain complete control over their checkout style and layout because Braintree gathers credit card data using small, transparent iframes that replace individual payment fields. Braintree settlement reports are now also conveniently available within the Magento Admin.

PayPal enhancements include PayPal in-context checkout and saved credit cards. In-context checkout helps to increase conversion rates 69 bps by allowing shoppers to pay with PayPal without leaving the merchant’s site. PayPal saved credit cards boost repeat purchases by allowing merchants to securely store credit card information with PayPal so customers do not need to re-enter it in checkout or when reordering items from the Admin interface.

Improved management interfaces make it faster and easier to search for information in the Admin, set up global search synonyms, and create new product, category, and CMS content.

Security Enhancements

The release includes enhancements to improve the security of your Magento application. There are no confirmed attacks related to these issues to date, certain vulnerabilities can potentially be exploited to access customer information or take over administrator sessions. Its recommend that to upgrade Magento software to the latest version as soon as possible.

System Requirements

Our technology stack is built on PHP and MySQL. Magento 2.1.0 supports:

 

Incase you are looking for Magento hosting try our : Specialized Magento Web hosting packages

 

421 Too many connections from this IP

This article discusses why you may receive a Too many connections from this IP error message when you use FTP, and how to resolve the problem.

Causes an idle FTP connection?

The default setting is usually 8 or 10 simultaneous FTP connections from 1 IP. If you exceed this amount, you may run into a 421 Connection Error which are often caused by Idle FTP connections.

Idle FTP connections are caused when an FTP client opens multiple connections, without closing the previous ones, or due to an incorrect setting.

VPS and Dedicated hosting plans have the ability to modify the number of simultaneous connections allowed in their WHM; the default setting is usually 8.

Increasing this limit will prevent the error messages.  Our Shared and Reseller plans allow up to 8 simultaneous FTP connections from 1 IP address at a time, but cannot raise this limit.

Response: 421 Too many connections (8) from this IP

If your FTP client is using more than 8 connections at the same time, you will get refused with a message similar to this:

Response: 421 Too many connections (8) from this IP Error: Could not connect to server Status: Disconnected from server Status: Disconnected from server Status:  Delaying connection for 5 seconds due to previously failed connection attempt...

 

Closing Idle Connections in cPanel (Disconnect users from an FTP session)

If you suspect malicious activity from a user, or if the user is idle, you can disconnect their FTP session.

To disconnect a user from an FTP session, perform the following steps:

1. Login to cPanel, Click the FTP Session button under the Files section.

ftpconnections1.1

 

2. You will then see a list current FTP connections. Click the disconnet_icon icon next to the process ID that you wish to disconnect in the Action column.

ftpconnections1.2

 

You will then see a message similar to this Are you certain that you wish to disconnect the “test@” FTP user? Click the Disconnect button to proceed.

ftpconnections1.3

Now check reloading the page.

How do I Directory Privacy in my Control Panel

protect folder
protect folder

This feature allows you to protect certain directories of your account. If you enable this feature, the system prompts users for a username and password when they attempt to view content in a protected folder.

How Directory Privacy works

It’s important to understand how Directory Privacy on a folder works. When you choose to password protect a directory in cPanel, cPanel creates a rule in your .htaccess file.

This rule specifies that the folder is protected and the visitor will need to provide the proper username and password to log in and view the files.

Configure a password for a directory
  1. To password protect a directory, perform the following steps:
  • Select the directory that you wish to protect.
  • Click the appropriate folder iconto navigate to a different folder.
  • Click the desired folder’s name to select it.
Note: A protected directory's subdirectories inherit their parent directory's password protection.

2. Select the Password protect this directory checkbox.

3. Enter a display label for the directory in the Name the protected directory text box.

Note: This name is only a label for the directory, and you should not confuse it with the directory's actual name.

4. Click Save.

After you complete this process, you must create a user that can access this directory.

Create a user

To create an authorized user for the directory, perform the following steps:

  1. Enter the desired username in the Username text box.
  2. Enter and confirm the new password in the appropriate text boxes.
Notes:The system grades the password that you enter on a scale of 100 points. 0 indicates a weak password, while 100 indicates a very secure password.

Some web hosts require a minimum password strength. A green password Strength meter indicates that the password is equal to or greater than the required password strength.

Click Password Generator to generate a strong password. For more information, read our Password & Security documentation.
Click Add Or Modify The Authorized User.
Note: To change the authorized user's password, enter the user's information again in the Create User section of the interface, but enter a different password for the user.
Remove password protection

To remove password protection from the directory, deselect the Password protect this directory check box in the Security Settings section of the interface and click Save.