Reliable Penguin - Blog

WordPress URL Rewrites On Plesk 10 Windows

admin — Sat, 19 May 2012 11:30:23 +0000

We needed to get URL rewrites working on a Plesk 10 Windows server for a client wanting friendly URLs in WordPress. Turned out to be pretty easy …. 1. Make sure the Microsoft IIS URL Rewrite 2 extension is installed. You can find it here: http://www.iis.net/download/URLRewrite 2. Create a web.config file in the folder where [...]

Howto: Change Default Index On Plesk 10 for Windows

admin — Sun, 13 May 2012 17:28:23 +0000

When you request a URL with no file name at the end like: http://www.acme.com/ the web server consults a list of predefined “index” or “default” file names and returns the first matching file. On Plesk 10 for Windows follow these steps to change the default index page list: Login to Plesk Drill-down to the control [...]

Reliable Penguin - Blog

Install PHP SSH2 extension on RHEL 5.6 with EPEL repository

admin — Thu, 10 May 2012 14:15:55 +0000

Here are the steps to install the PHP SSH2 extention on RHEL 5.6 with the EPEL repository. Install packages that may be needed: yum install php-pear php-devel libssh2 libssh2-devel Temporarily allow binary execution in /tmp mount -o remount,exec /tmp Install the extension: pecl install channel://pecl.php.net/ssh2-0.11.3 Restore /tmp restrictions: mount -o remount,noexec /tmp Reload apache: /sbin/service [...]

Reliable Penguin - Blog

Putty SSH Tunnel for RDP

leerb — Sun, 08 Apr 2012 01:14:28 +0000

On occasion I need to use Remote Desktop Protocol (RDP) to access a Windows server that is not directly available on the Internet. For example I might have SSH access to a Linux host on the target network. Or the Windows host has source access controls limiting access to a specific network when I’m traveling. [...]

Reliable Penguin - Blog

WordPress Development Sites

leerb — Fri, 30 Mar 2012 16:01:29 +0000

Had a conversation with a client yesterday about how best to develop a new WordPress stie before the domain name was pointing to the server. This might be the case if you’re building a new site while the domain is still pointing to the old site. If the new site has to be publicly available then [...]

Reliable Penguin - Blog

Plesk 10 Greylist Problems

leerb — Fri, 16 Mar 2012 10:34:15 +0000

Recently on several Plesk 10 servers we’ve had users complain that they could not receive email from various domains. Upon investigation we found that the domains were all hosted on Microsoft’s Exchange email service. The bounce messages received by the sender were from bigfish.com and the source address in the server mail logs was a [...]

Reliable Penguin - Blog

Passive Mode FTP with iptables

leerb — Thu, 08 Mar 2012 10:30:23 +0000

There’s lots of advice on the net about how to setup a server with iptables to allow passive mode FTP. Below is the approach that we’ve found to be most effective. Start by configuring your FTP daemon to use a fixed range of ports. We use 41361 to 65534 which is the IANA registered ephemeral port [...]

Reliable Penguin - Blog

NFS Server On RackSpace Cloud

leerb — Sat, 03 Mar 2012 12:15:44 +0000

Today we’re going to setup an NFS server and client on a pair of RackSpace Cloud Servers. To get started create two cloud servers – one will be the NFS server and the other will be the NFS client. We’ll be using CentOS (RHEL) for our project but you can use the distribution of your [...]

Reliable Penguin - Blog

Non-chrooted Cronjobs In Plesk 10

leerb — Wed, 09 Nov 2011 15:13:05 +0000

Plesk 10 has a bug (feature?) where it inserts this line into the crontab file for each user (including non-chrooted users): SHELL=/usr/local/psa/bin/chrootsh This effectively breaks the jobs, because it makes them try to run in a chroot jail, which won’t work. You can manually remove the lines but Plesk will restore them when the job [...]

Reliable Penguin - Blog

Insert Varnish Cache With NAT Rule

leerb — Tue, 08 Nov 2011 19:50:44 +0000

Here’s a simple nat rule for iptables that will route incoming web traffic to your varnish cache. This allows you to implement varnish without reconfiguring apache. In the varnish config, set the backing do be 127.0.0.1:80. iptables -D PREROUTING -s ! 127.0.0.1 -d 192.168.100.16 \ -p tcp -m tcp --dport 80 -j DNAT \ --to-destination [...]

Reliable Penguin - Blog