accelerator | Linuxaria

Flareget a great download manager for Linux

May 182013

flareGet is a full featured, advanced, multi-threaded, multi-segment download manager and accelerator for Linux, It allows user to pause, resume or monitor the download speed.

The application is free to use on it’s lite version, but not open-source,there is also a pro version that cost around 20$ that can be bought directly from the official website.
It supports all 32 and 64 bit Debian and RPM based Linux Distributions. The supported Linux Distributions include Ubuntu, Fedora, Mandriva, OpenSuse, LinuxMint, ArchLinux and many more.

How to log the correct Ip having Varnish and Nginx

Articles 1 Response »

Jan 302013

When you run a webserver behind a reverse proxy or HTTP accelerator such as Varnish, the webserver access logs will display the IP of the proxy (generally 127.0.0.1) instead of the end user’s IP.
This is a problem when you have a software like webalizer, awstats or similar log file analysis program, because you lose one of the most important information: “Who is the requestor of a page ?”, also having all the access coming from the same IP (127.0.0.1) you lose information such as “what’s the browsing pattern of visitors ?” “Is someone trying to do something Nasty ?”

In this small how-to I’ll show how to put this information back on your Nginx log files in 2 different ways.

How to put Varnish in front of your Webserver without doing any change.

Articles, Guides 12 Responses »

Apr 302012

Varnish is an open source “web accelerator” which you can use to speed up your website.

It can cache certain static elements, such as images or javascript but you can also use it for other purposes such as Load balancing or some additional security, in general most of the people want to try it and test their website to see if it’s really so amazing (IMO yes, but test it yourself).

The traditional guides will tell you to move your webserver to another port, perhaps 81,8080 or just bind to localhost, configure Varnish to listen to port 80 and use the web server as backend, the server where Varnish will forward requests not found in his cache.

This is the “normal” configuration and it works fine, but sometimes you just want to make a quick Test or perhaps you are using a Control Panel, such as Cpanel, Kloxo or ISPConfig and in my experience change the standard listening ports of Apache is not a decision to be taken lightly with these tools.

So in a VPS (with Kloxo) I’ve used a different approach: iptables.
Continue reading »