ServerBuddies Support Blog

Here is the steps to install the Cisco VPN client application on linux based servers. We have found several customers use their cisco router to manage their VPN Network, therefore by following this simple steps you should be able to install and configure your linux server as a VPN client.

- Download vpnclient-linux-4.8.00.0490-k9.tar.gz from ServerBuddies file server:

- Uncompress the application:

You will see a new folder created called “vpnclient” ‘cd’ into it and run the installation script

Answer the following questions:

Directory where binaries will be installed?
[/usr/local/bin]

Automatically start the VPN service at boot time?
[yes]

Directory containing linux kernel source code?
You will need to search where your kernel source code is, 90% of the cases will be on /lib/modules/`uname -r`
For this example we will use:

/lib/modules/2.6.9-67.0.22.EL/source

####
If you cant find your kernel source files, it’s probably you dont have it, you will need to download the kernel-devel package:

Note: Double check you are downloading the right kernel version that you currently use by typing:

####

To Start you vpnclient type:

Keep in mind that Cisco VPN profiles are both compatible in Linux or Windows so if you have already a Windows myprofile.pcf cisco vpn client profile you can move it to /etc/opt/cisco-vpnclient/Profiles/myprofile.cf for use it on your linux server later.

To start the VPN connection using your current profile just type:

This cisco vpnclient version should be able to run on latest kernel version, but if you run into problems installing your Cisco VPN Client feel free to contact our Tech Support Staff.

* ServerBuddies Team.

Tags: cisco vpn, linux, vpnclient

Getting Started

1.

 First, install OpenSSH on two UNIX machines, hurly and burly. This works best using DSA keys and SSH2 by default as far as I can tell. All the other HOWTOs I’ve seen seem to deal with RSA keys and SSH1, and the instructions not surprisingly fail to work with SSH2.

2.

On each machine type ssh somemachine.example.com and make a connection with your regular password. This will create a .ssh dir in your home directory with the proper perms.

3.

On your primary machine where you want your secret keys to live (let’s say hurly), type

This will prompt you for a secret passphrase. If this is your primary identity key, make sure to use a good passphrase. If this works right you will get two files called id_dsa and id_dsa.pub in your .ssh dir. Note: it is possible to just press the enter key when prompted for a passphrase, which will make a key with no passphrase. This is a Bad Idea ™ for an identity key, so don’t do it! See below for uses of keys without passphrases.

4.

Copy the id_dsa.pub file to the other host’s .ssh dir with the name authorized_keys2.

5.

Now burly is ready to accept your ssh key. How to tell it which keys to use? The ssh-add command will do it. For a test, type

This will start the ssh-agent, add your default identity(prompting you for your passphrase), and spawn a bash shell. From this new shell you should be able to:

6.

This should let you in without typing a password or passphrase. Hooray! You can ssh and scp all you want from this bash shell and not have to type any password or passphrase.

Tags: set up ssh keys

The release of Parallels Plesk Control Panel 8.6 continues Parallels initiative of enabling integration
of all types of web hosting software. This new version of the software further integrates the Parallels
Plesk Control Panel with Parallels Virtuozzo Containers, 3rd party, and other web applications as well
as continuing to deliver innovative ease of use, the highest levels of stability and performance, security
and unmatched value. With over 20 new features and capabilities, Parallels Plesk remains the true
leader in multi-platform control panels. 

1. Parallels Plesk Billing Bundle

2. Changing DNS zone SOA serial number format

3. Improved DNS zone update

4. Permission for clients to select a target DB server

5. Categories in Application Vault

6. DomainKeys support

7. 4PSA VoipNow integration

8. Database users prefix

9. Import/Export Database Backup

10. New Plesk events

11. Ability to block domain creation in foreign DNS zone

12. Extended branding options

13. Application Packaging Standard (APS) CGI support

14. ProFTPd 1.3.1 Update

15. Horde 3.1.7 Update

16. SPAW 2.0 Update

17. DotNetNuke 4.8.2 Update 

18. openSuSE 10.3 Support 

19. Fedora 8 Support

20. Parallels Plesk Sitebuilder 4.2 Support

21. Simple DNS Plus 5.0 Support

22. ColdFusion 8 Support

23. SmarterMail 5 Support 

24. CommuniGate Pro 5.2 Support

25. MailEnable 3.14 Support

26. Merak 9.2.1 Support

27. Parallels Plesk Billing (formerly ModernBill) integration

* ServerBuddies recommends Plesk!

Tags: plesk, plesk 8.6.0

This is a common error when we issue a “php -v” over command line or when we browse a phpinfo.php on a site.

To quickly fix this problem you will need to recompile your ffmpeg-php again.

How we fix this?

1)

remove/comment the call to av_free_static()

save.

2)

rebuild ffmpeg-php and place the new ffmpeg.so on your extension directory.

Should be fixed.

Tags: av_free_static, ffmpeg, ffmpeg.so, undefined symbol

On the last few months, we have seen a lot of customers trying to setup his own Video Sharing site (ex: youtube clone) with no luck, the implementation it’s not that hard to setup your linux server to allow video streaming. There are a lot of youtube sites around that may do this, what you only need is to setup your linux system to work with the requirements. Due this we have made this HOW TO FFMPEG post so customers and non-customers would do this by their end.

Requirements:

FFMPEG
FFMPEG-PHP
Mplayer
Mencoder
flv2tool (RUBY ON RAILS REQUIRED)
LAME MP3 Encoder
Libogg
Libvorbis

—————————–

1) We download all the necessary packages.

2) in order to install all the packages, we extract all of them.

3) We create a codecs directory so we can use it as default codec dir later. Then we copy the mplayer codecs to the new directory.

4) We create a temporary TMP dir in order to safe compile everything.

5) We start compiling & installing packages

a) For LAME:

b) For LIBOGG:

c) For LIBVORBIS:

d) For FLVTOOL2:

e) For MPlayer:

f) For FFMPEG:

Some necessary linking,

e) For FFMPEG-PHP:

Finally, we include the ffmpeg-php module to our php.ini

Restart apache:

DONE!

Your installation is finish, now you need to check if the video streamin is working correctly on your website.

Keep in mind that most of the sites have different video rate conversion, this does not mean the installation is wrong, you will need to look on the PHP code of your video streaming site to see if its using ffmpeg and mencoder command line properly.

Tags: ffmpeg, ffmpeg-php, libmp3lame, mencoder, mplayer