Jump to content


VlexoFree Notice

Interviews will be open every Friday starting at 12am PDT and lasting for 24 hours.

Eli L

Member Since 20 Feb 2007
Offline Last Active Today, 03:12 PM
*****

Topics I've Started

VlexoFree is upgrading to a better server!

24 April 2012 - 10:13 PM

Today is a big day because today I have purchased a new server for VlexoFree!

This comes with mostly good news, but also some mildly not-so-good news.

First, the GOOD news:

The new server that was bought is more up-to-date, faster, and all around better then our current one.

Heres the gist of what we're changing to:
  • CPU:  Q9550 --> Core i5-2500
  • RAM: 8GB DDR2 --> 16GB DDR3
  • OS: CentOS 5.x --> CentOS 6.x

Now the BAD news:

I've noticed that some things on the server are going unused such as PostgreSQL. So on the new server I will not be installing it. This may apply to other small things too as I go through them.

When will the move happen?

I don't have a date set. It all depends how long it will take me to configure the server and test everything to make sure it all works without issue.

If any of you would like to help out and be the first ones on the server, just post in this thread saying you're interested and I'll transfer your account over when things are setup. This will allow me to check for any issues the server may have.

Oh yeah, the new server is called Tesla. :D

Downtime report - December 8th

08 December 2011 - 12:09 PM

So if any of you noticed, on the 7th and the 8th there was a total of about 4 hours of downtime.

I sent a ticket to our datacenter but for some reason they are not wanting to respond as to why the downtime happened; but from what I see, from the server stats during the time the server was inaccessible, the server was running perfectly fine. This means that the downtime was most likely an issue with something in the datacenter where this server is at and not a problem with the actual server.

So, hopefully they dont let this happen again we can all keep enjoying our websites!


Sorry for any inconvenience this may have caused to VlexoFree members.

-Eli

Reminder: Make backups!

16 October 2011 - 09:48 PM

This is just a friendly reminder to all VlexoFree members to make sure you’re making frequent backups of your website.

We do not keep backups of any members’ accounts off the server so, to minimize the chances of your website or files being lost, please remember to frequently generate a full backup of your account then download that backup and store it on your computer (or anywhere else you would like that is not on this server).

To do this just follow these steps:

  • Login to cPanel and go to the “Files” Box
  • Click on the “Backup Wizard” image then click on “Backup”
  • Do a “Full Backup”.
  • Wait for the backup to complete
  • Once the backup is done, download the backup to your computer.
Once you have downloaded the backup to your computer I would recommend you delete the backup file on your VlexoFree account to free up space on your account so you dont go over your space quota.

View the blog article

Important announcement about Co.CC domains

07 July 2011 - 12:33 AM

Two days ago Google decided to remove all Co.CC domains from its listing. This means that if you have a Co.CC domain then your site will no longer show up in Google. This is due to there being a significant numbers of spam sites thats use a co.cc domain.

So, VlexoFree will no longer be suggesting users use Co.CC domain and instead we will start recommending our second option Cz.cc.

If you want to change your domain to a Cz.cc domain then go to their website and create a domain then you can request a domain change in our support forums.

Edit: Cz.cc are also blocked by google. Please use http://dot.tk  now

Downtime (June 17th)

18 June 2011 - 01:06 AM

This post is regarding the downtime early yesterday.

There was about 6hrs of downtime yesterday starting a little after 3am PST. The downtime was caused by a fork bomb which used up all the server's memory and crashed it.

Unfortunately I had to be at work at 3am for 8 hours so I was unable to bring the server back up.

I'm working on preventing this from happening again as downtime is not something I want to see here very often (or at all).

I'm sorry for any inconvenience this has caused.