Install Varnish on Magneto, apache, Ngix Plesk Server and optimize for speed.

Parts of this project are done so please read carefully. Due to the complexity of this project. Only admins who have successfully set up Varnish in a plesk ngix environment should apply. Showing proofs of working sites to be tested on isvarnishworking.com. The header i believe should should ngix and varnish. Scope of work You will be working on citrix xenserver virtual machine. Starting. 1) You will need to connect to me via teamviewer and check the config on the fail2ban script running on the citrix xenserver. This is based on centos. This script is running, but i dont think its blocking ips in Iptables. The server is scanned so i need it working. 2) I need the fail2ban config checked on the centos machine, SSH is off you cant access it without xencenter. You are welcome to turn on SSH, but please turn it off at the end of the project. 3) You will need to check the fail2ban script. I dont think its running and blocking IPS from scans as it should. 4) There is a telnet script or app running please remove it. Varnish Stuff. The centos 6.2 runs varnish and Plesk 11 so is using apache and ngix. One day i had the wonderful idea to add varnish even thou we have jack shit load. as i thought it would be well worth it for the faster page loading for SEO. After spending several days googling and fucking about it seems it must run like this Ngix port 80 Varnish port 6081 Apache 7080 However this makes little sense to me as i thought varnish would run on part 80 and be the first port of call for loading a webpage. Ngix will handle all SSL as varnish cant do that. Apache will be a failover for varnish and ngix. If apache goes down apparantly varnish can serve pages from cache. But this is all prob obvious shit to you. We installed varnish 2.1 on the server as it can be done via yum, but really id like 3.0 this needs to be compiled because its for debian or some non sense. It will perform better and have more features. For the domains [login to view URL] [login to view URL] is working But if you do the server ip and the port http://5.39.11.144:6081/ its the plesk default domain or master whatever, only this is a extra ip for SSL and this domain runs on a seperate ip for plesk, it seems pretty fucked up to me and im worried about it. The other domain also [login to view URL] [login to view URL] [login to view URL] reports all ok for 2wheel4, but autokicker needs some settings changed. [login to view URL] has no content or index page so it wont report anything Turpentine for magneto is installed for 2wheel4 and [login to view URL] when applying settings please see the screenshot APPENDIX A , both sites create the same error. We did alot of fucking about before this to get other shits working. Overall the shits not working and i want it to be rapido and work the best it can. The final domain is [login to view URL] same ip as autokicker which shares the same ip as the plesk and is the main ip for the centos machine [login to view URL] will server files outsite to places like ebay css and images mostly. I heard varnish can help here. .... The final domains will be [login to view URL] which will also runs its own ip and run magneto and [login to view URL] which will serve data outside the same as [login to view URL] [login to view URL] has been set up with turpintine ready installed on its own ip. It needs setting up for always uses the www. extension. [login to view URL] will take seconds to setup I am happy for you to work from your pc on SSH aslong as you can turn SSH back on. Which should be easy i think root login is disabled.