UKC You can use iptables pre-routing to route from one port to another.
For example, the following command will enable mail users to use port 26 or port 25 for SMTP request. All port 26 requests will be routed to port 25.
# iptables -t nat -A PREROUTING -p tcp -d 192.168.167.2 --dport 26 -j DNAT --to 192.168.167.2:25
Now your clients can use port 26 or port 25 without any problems.
WordPress is an excellent application used the world over. This unfortunately makes it also a target for hackers. There are some very simple steps you can take, completely non-technical, that can help secure your WordPress blog.
1. First things first. Eliminate all known vulnerabilities. Now.
Update your WordPress installation to the latest version. This is the absolute most important and most effective first step. Do it now.
2. Don’t make your WordPress blog so easy to target
Install WordPress in a folder rather than document root, this makes it slightly more difficult for large scale hackers to find your system files. There are so many root installations of WordPress to keep hackers busy that the effort returned finding sub folders is not usually worth it.
3. Do not delete the admin account. Yes, you read it correctly.
So we need to secure admin, do this by creating a new administrative user, then downgrade the admin account to subscriber. This will make it impossible for a hacker to administrate your site using admin. By not deleting the admin account the hacker is kept busy trying to guess the password and the focus is away from the ‘real’ administrator account.
4. Control failed login attempts.
Lock the account after a number of failed attempts. This will render dictionary attacks on your account pointless for the hackers. Use a plugin such as Login LockDown to control failed log in attempts.
5. Implement easy eveyday plugin security
Use some WordPress security plugins such as Stealth login, AskApache password protect and WP security scan.
6. If they get in – don’t let them take you out
Take regular backups. Should a hacker gain access at least you don’t permanently lose your site. You will be able to restore, tighten up and continue. Don’t let them take you out!
7. Honestly, this is the step that is most often ignored
Have an absolutely ridiculously difficult to guess password. Have some numbers, uppercase and lowercase letters and maybe a punctuation mark or two. They’ll never guess it – maybe not even with a quantum computer.
Re: Set up a cron job in Plesk, Plesk crontab, Create a PHP cron job in Plesk
Setting up a cron task or scheduled job within Plesk is a piece of cake – once you know how.
First, find your way in to the Plesk Control Panel and hit the “Scheduled Tasks” button, then “Schedule New Task”. The example below will show a working task executing a PHP file named cronjob.php located in /httpdocs (your document root) at 01:00 every morning of every day:
The form looks pretty straight forward however there are some points to note.
If you have problems, check your asterisks are in the right places and that you cron PHP file is in the right location. Compare the schedule task dialogue boxes carefully and you won’t have any problems.
The process of transferring files from your personal computer to your web hosting account is referred to as “uploading” or “publishing”. We support FTP (File Transfer Protocol) for the uploading of your web site files.
If the application you used to design your site does not have an integrated FTP Client (unlike FrontPage, Dreamweaver or Serif Webplus) then you will need to download and install an FTP Client to perform the upload.
We recommend FileZilla FTP, this application is easy to use, a recognised industry standard and also completely free!
If you do not already have FileZilla then it’s time to download and install it from the official FileZilla download page. Select the appropriate version for your system and install by double-clicking on the file you just downloaded and follow the instructions. The install process should take less than a minute.
Before we can use FileZilla to connect to your web space, you will need to have at hand your Hosting Settings Email, this contains your FTP account settings. Please be sure you have the following information:
If your domain name is parked, and you have not purchased a web hosting package upgrade then you must leave this tutorial at this point and purchase a hosting package for your domain name. Parked domains do not have FTP services.
You will also need to know the directory that your web site is stored on your local computer. For the purpose of this tutorial, my site is stored in C:\My Documents\mywebsite. My site consists of “index.html” (my home page) and the directory that contains the GIF\JPG files is named “images”. We will upload both the index file and the images directory.
Important: It is easy to make a mistake here. Be careful when entering your FTP password as you cannot see the characters you are typing as they are masked by FileZilla. Make sure there are at least the same number of masked characters as there are in your password, a common error here is to copy+paste the password from the Hosting Settings email together with invisible whitespace characters – this makes it impossible to connect until you fix the password.
Congratulations! You have successfully setup your FileZilla profile and uploaded your website!
Ok, so there was a problem. Here we will address the most common problems.
The most common problem of all is concerning an incorrect username or password. To correct the error your must ensure that your username and password are correct. The connection log might show something like this:
Response: 220 ProFTPD FTP Server ready.
Command: USER admin67890
Response: 331 Password required for admin67890
Command: PASS ******
Response: 530 Login incorrect.
Error: Critical error
Error: Could not connect to server
This error indicates that your FTP hostname, eg. server.microlite24.com is incorrect. This is almost always due to a typing error although sometimes a local DNS error (on your PC or at your ISP) can cause this problem:
Status: Resolving address of server.microle24.com
Status: Connection attempt failed with “EAI_NONAME – Neither nodename nor servname provided, or not known”.
Error: Could not connect to server
Status: Waiting to retry…
This problem does not have an error message. In fact, your site appears to upload fine but yet when you try to view your site through the browser, you still get the default “holding page”. This problem can be cause by several rasons:
For all other problems you will need to contact the Helpdesk and submit a ticket. To assist the technical support team, copy+paste the FTP error log into your ticket, this will enable them to resolve your problem in the shortest time.
Re: Mail being bounced even though Mailbox exists, bounce message
“Hi. This is the qmail-send program at server.mailserver.com.
I’m afraid I wasn’t able to deliver your message to the following addresses.
This is a permanent error; I’ve given up. Sorry it didn’t work out.”
Take a look in the mail log file:
tail -1500 /usr/local/psa/var/log/maillog
You see errors such as this:
Unable to stat entry '/usr/local/psa/handlers/info'
To resolve you need to remove and rebuil all mail handlers as follows:
1. Stop the mail service
# /usr/local/psa/admin/sbin/mailmng --stop-service
OR
# service qmail stop
2. Backup old handlers in a temporary directory
# mkdir /usr/local/temp
# cp -a /usr/local/psa/handlers/before-* /usr/local/temp/
# cp -a /usr/local/psa/handlers/info /usr/local/temp/
3. Remove the handlers
# rm -rf /usr/local/psa/handlers/before-*/*
# rm -rf /usr/local/psa/handlers/info/*
4. Recreate handlers using mchk utility
# /usr/local/psa/admin/sbin/mchk --with-spam
5. Start mail service:
# /usr/local/psa/admin/sbin/mailmng --start-service
OR
service qmail start
This may take a little time however it will resolve all errors.