We will update everyone of any further changes. Thanks for your patience.

UPDATE: FSCK has finished on server and server is back online. Sorry about the inconvenience caused by this.

Due to rather unfortunate circumstances, our server ip has been changed/moved  to new block and due to no or rather miss communication of such an event to us,  by our provider we are stuck waiting for cpanel license to be activated (happening around noon tomorrow Central Time) and than will have to wait for DNS to propagate and get the nameservers working for the new ip block we are now on.

Sorry about any inconvenience caused due to this unwanted and unplanned interruption.

UPDATE: New Ip’s have been assigned and sites ip’s migrated to new ip’s. On your end you will not need to change anything, but if you are using ftp client and are connection using old ip, please use the ip 204.124.182.189 instead, does not effect those using domain name for ftp hostname.

Server appears to be down, trying to get in touch with our provider but have not heard anything back from them yet, so will wait and see what seems to be the issue time at this late hour of the day.

Hoping it to be online soon.

Regards

There has been an issue with billing however, so please make sure after you make your payment, to check and see if your Invoice gets marked as paid, and there is no outstanding +ve balance. If outstanding balance is in -ve say -3.14 that means you have those fund available to you and will be applied next month or in event you forget to pay your invoice.

On the other hand please try to use Glype Proxy script, personally have found it to have an edge over the older php proxy scripts, will try to bring out some free templates for the same in coming weeks.So keep checking and where feasible referring our Php Proxy Hosting site to others.

Thanks

Our upstream network provider has informed us of scheduled network maintenance that will be taking place Sunday, September 28th, 2008 with a 6AM-8AM EST window. This will involve the replacement of core switches/routers and distribution switches.

This maintenance will be service affecting, however, we expect the overall network downtime to be 15-30 minutes, during the 2-hour maintenance window…as equipment, cabling, and routes are changed. There will also be momentary periods of higher than normal latency while circuits are re-routed, BGP updated/reloaded, and cabling switched, during the 2-hour maintenance window. Proper planning, configuration, and testing has been completed in advance of this maintenance period, in order to minimize as much as possible the overall time that will be service affecting.

We thank you for your patience and understanding with this necessary maintenance, as well as for your continued business!

Currently datacenter is experiencing an outage, hence server appears to be down. Will update as we get more words as to what actually happened, and eta on fix of the problem.

Time is 2.02 Am Here.

Regards

We are currently investivating with help of Cpanel support team to figure out the recent apacahe crash after we optimized and upgraded it, it might take some time to get it running again depending on the root of the issue. Nothing else have changed, cpanel and your control panel should be working fine. Data is safe too, just apache/httpd is not coming back online.

Will update this if something new comes up.

Here are the few things / updates performed by the administrator.

1) Reinstalled and configured SIM.
2) Apache update to 2.2.9 with PHP 5.2.6 as fcgi, Eaccelerator, mod_security, suhosin, Zend optimizer, curl and other options.
At this time, suhosin is in simulation mode.
3) Installed and configured CSF/LFD.
4) Disabled mailman, POP, IMAP and other unused services
5) Installed WHM theme 7 Dana. You can switch back to the default theme, if you don’t like it… I just like the collapsable menu, lol.
6) Ran a search for php shell scripts : the good news is that it returned nothing
7) Installed vnstat and added a web interface (WHM >> Server Status)
Updated logwatch
9) Optimized sysctl.conf
10) Hardened host.conf
11) Fixed logrotate bug
12) Secure /dev/shm
13) Added some useful scripts from PWS to WHM >> Server Status
14) Configured Background Process Killer
15) PHP.ini tweakings
16) Disabled anonymous FTP

As you guys have noticed today server is again down, this time same reason of nullrouting the ip, but this time burst.net acted in an unprofessional manner not notifying us or our provider volumedrive that they had done that, resulting in almost entire day now of downtime. We are working to get this issue resolved, and hoping to move to new location within a week’s time, either will stick with current provider (they are opening new facility in NY) or just get a new provider itself, so we do not have to worry about Burst.net and its unprofessionalism.

Sorry for the issue, but sorries don’t really cut it all the time, if only i had any control over how Burst.net should be run this would not be happening at all. Still awaiting reasons as to why null routing took place in the first place.

Change is inevitable ! Unless they can reimburse us or can provide a professional explanation !!

Yesterday we got an email from abuse department saying phishing (or as i say fishing)  activities were taking place from one the domain hosted. Replied within few minutes of getting the email, providing the datacenter with culprits ip, and asked for steps to take to resolve the issue. And thanks to no reply for over close to 18 hrs, cognent null routed our server ip. Hence you might not be able to access your sites right now. Had only our provider acted swiftly to an abuse report this could have been prevented.

We are looking to get new ip assigned to server asap, and making sure the original ip is cleared given back to the server. New ip is currently assigned to ns2.proxyorama.info , so your sites should work normally after its assigned.

Note: These are the consequences/results/conditions beyond our control as we cannot monitor how your proxy sites get used.

We will be back shortly (hoping it wont take ages to assign new ip to the server)

Feel free to download and place it in your public_html folder, where your proxy main index file is located. Ips listed there are in and around from ASIAN continent.

Unzip and upload the .htaccess file. DOWNLOAD FILE :Note: There is a file embedded within this post, please visit this post to download the file.