UKC

How to Upgrade IGB NIC Driver

Upgrade IGB Driver to Fix Packet Loss Problems

The early versions of igb NIC/LAN driver were buggy, if your version look like this:

# ethtool -i eth1
driver: igb
version: 5.0.5-k

Any version under v5.2.15 is buggy and a simple ping test to your server will show packet loss issues, usually around 20%.

To upgrade the driver, use the following steps.

1) cd /root
2) wget http://sourceforge.net/projects/e1000/files/igb%20stable/5.2.17/igb-5.2.17.tar.gz
3) tar -xvzf igb-5.2.17.tar.gz
4) cd igb-5.2.17/src/
5) make install
6) rmmod igb; modprobe igb
7) rmmod ixgbe; modprobe igb
8) vi /etc/sysconfig/modules/igb.modules

and set 

modprobe igb

9) Following is the output ::

=========================

root@server [~]# modinfo igb

filename: /lib/modules/2.6.32-504.12.2.el6.x86_64/kernel/drivers/net/igb/igb.ko
version: 5.2.17
license: GPL
description: Intel(R) Gigabit Ethernet Network Driver
author: Intel Corporation, 
srcversion: 420A0DE22C6377FB9C68995
alias: pci:v00008086d000010D6sv*sd*bc*sc*i*
=======\\=================
=======================
root@server [~]# lsmod | grep dca
dca 7101 1 igb
=======================

Let’s see the active version after the upgrade:

# ethtool -i eth1
driver: igb
version: 5.2.17
firmware-version: 1.52, 0x800007ae
bus-info: 0000:01:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

That resolves the issue. No reboot/restart is required.

Email bounces with error DENIED_AUTH_REQUIRED

emailHow to fix DENIED_AUTH_REQUIRED Error

To reduce spam levels and eliminate damage caused by compromised web applications and plugins, it is no longer possible to send from OR receive to email addresses that do not exist.

If you have been using email addresses that do not exist to send emails, form submissions then you will find the emails are no longer sent. The fix is easy, see the steps below.

Sending Outgoing Emails (SMTP)

If you receive this error when sending emails from the server, then you need to ensure that

  • The email address must exist and show here: Plesk > Website & Domains > Mail
  • You are authenticating to the SMTP server correctly in your web application
  • You are using port 587 in your SMTP connection scripts (not port 25)
  • It does not matter if your MX records are externally managed

Receiving / Forwarding Emails Externally

If you receive this error when receiving emails and you are forwarding them externally

  • Are you using a catch-all email address? Don’t do it! Here’s why.
  • Ensure the email exists as either a mailbox, forwarding alias or receiving alias
  • You should be able to see this email in Plesk > Websites & Domains > Mail or as a receiving alias to an address in this list.
  • If this email does not exist, then you must create it

Still not working after fixing the above? Contact the Helpdesk

If you are suddenly receiving this problem then you must ensure the email address you are using (the one experiencing the problem) actually exists in your Plesk panel, as it may have been abused by spammers previously.

If in doubt, do not hesitate to contact the helpdesk after reviewing the above information and supply the following information so that we may assist:

  • Confirm you have waited 15 minutes since making changes in the Plesk panel
  • Explain if the problem is receiving or sending
  • Explain the email address experiencing the problem
  • Confirm that you are using SMTP authentication (if problem is outgoing)
  • Confirm that the email address exists (if problem is incoming)
  • Copy the bounce message into the helpdesk ticket

If you do not supply enough information it will take much longer to help you resolve the problem as we will need to gather this information before being able to help you to resolve the issue.

Emergency Hardware Replacement – MICROLITE12.COM

Scheduled for weekend 27/28 June 2015

We have been unable to satisfactorily bring MICROLITE12 up to the level of reliability that we require as a minimum due to an inherent hardware fault that we have not been able to successfully isolate.

With this in mind, we have decided to replace all of the hardware completely – including the storage units.

During the weekend 27/28 June, we will be migrating all client data from the current hardware (5.77.60.36) to completely new hardware (5.77.60.166).

There will be no downtime for your web sites or email services. We will switch the new server into production only after it has passed our comprehensive data migration and validation testing.

Notice: Please refrain from making significant changes to your web site during this period. The migration of the data will take many hours. We request that you put off any changes until the upgrade is complete to avoid an inconsistent transfer of your site data.

Thank you for your patience,

Colin @ Level III Team

How to Create Password Protected Directories

header_ppp_circle_270x274Protecting Files and Folders in Plesk

If you have directories in a site that only authorised users should see, restrict access to these directories with password protection.

To protect a directory in your site with a password and to specify authorised users:

  1. If you are subscribed to several hosting packages and have access to several webspaces associated with your account, select the required webspace in the Subscription menu at the top of the screen.
  2. Go to the Websites & Domains tab and find the site’s domain name.
  3. Click Password-Protected Directories.
  4. Click Add Protected Directory.
  5. In the Directory name box, specify the path to the directory that you want to protect with a password.

    This can be any directory existing in the site, for example: /private. If the directory that you would like to protect has not yet been created, specify the path and the directory name – Plesk will create it for you.

  6. If you are using a Linux-based account, you can also protect your CGI scripts stored in the cgi-bin directory. To do this, leave ‘/’ in theDirectory name box and select the cgi-bin checkbox.
  7. In the Title of the protected area box, type a resource description or a welcoming message that your users will see when they visit the protected area.
  8. Click OK. The directory you specified will be protected.
  9. To add authorised users, click Add User.
  10. Specify the username and password that will be used for accessing the protected area. The password should be from 5 to 14 symbols in length. Click OK.

To add an authorised user of a protected directory:

  1. Go to the Websites & Domains tab and find the site’s domain name.
  2. Click Password-Protected Directories.
  3. Click on the name of the directory you need.
  4. Click the Add User icon.
  5. Specify the username and password that will be used for accessing the protected area. The password should be from 5 to 14 symbols in length.
  6. Click OK.

To change password for an authorised user of a protected directory:

  1. Go to the Websites & Domains tab and find the site’s domain name.
  2. Click Password-Protected Directories.
  3. Click on the name of the directory you need. A list of authorised users will open.
  4. Click on the user’s name.
  5. Specify the new password and re-type it for confirmation.
  6. Click OK.

To revoke a permission to access the protected directory from a user:

  1. Go to the Websites & Domains tab and find the site’s domain name.
  2. Click Password-Protected Directories.
  3. Click on the name of the directory you need. A list of authorised users will open.
  4. Select a checkbox corresponding to the user’s name.
  5. Click Remove. Confirm the operation and click OK.

To remove password protection and make the resource available to the public:

  1. Go to the Websites & Domains tab and find the site’s domain name.
  2. Click Password-Protected Directories.
  3. Select a checkbox corresponding to the name of the directory from which you want to remove protection.
  4. Click Remove Protection. The protection will be removed and the contents of the directory will be accessible to the public without restrictions.

Watch the Video Tutorial

How to pay by BACS or Online Banking Transfer

icon-billingPay by BACS or Online Banking instead of Stripe

Sending payments from within the UK

Ref: your invoice number (or your account email address if you are making regular payments)
Account Name: UKC LABS LTD
Sort Code: 04-06-05
Account Number: 22154089

If you want to make regular payments or setup a Standing Order, you will find that you need to set the reference to something that does not change monthly and so entering the invoice number will not be possible. In these cases simply use the email address of the account that the invoice was sent to and this will be enough for us to match up the payments.

BACS payments made between Monday and Friday will be processed within 3 working days.

Sending payments from outside the UK

Payment type: SWIFT
Currency: GBP
Account name: UKC LABS LTD
IBAN: GB53 CLRB 0406 0522 1540 89
Swift code: CLRBGB22
Bank Address: 4th Floor, The Featherstone Building, 66 City Road
London
EC1Y 2AL
Ref: your invoice number (or your account email address if you are making regular payments)

Swift payments will be processed within 3 – 5 working days.