We have resolved the issue that caused the downtime of WadioMedia and Warez-Shop. We’re sorry for the inconvenience.
We have resolved the issue that caused the downtime of WadioMedia and Warez-Shop. We’re sorry for the inconvenience.
This blog is the official information center of the Warez-BB.org community. You can find here all latest news about the technical issues the site may face, especially in case
of downtime.
Main server IP: 178.63.152.101
Image server IP: 178.162.176.108
We’re about to embark on a massive server migration to move away from our old static-files server to our new server. This means that avatars, images, IRC, Support Centre, this very blog and Wadio will be moving to another server shortly. We anticipate that very little downtime will be caused or no downtime at all, depending on the service in question.
Avatars and images on our main site will have zero downtime, while the rest of the services will have downtime.
Unfortunately, a mix up with the server order has occurred and this means that we will be forced to migrate everything to another server before finally moving to the intended server. This means that we will have two server moves instead of one.
We’re currently working on fixing the bugs caused by our upgrade to PHP 5.3.3.
We’re sorry for the inconvenience.
We’ve noticed that there is lag on our site again, we’ve moved to fix this already.
We were down for 3 hours due to an unexpected server crash. We have rebooted the server and our site is now operational again.
We’re sorry for the inconvenience.
Turns out the lag issue runs deeper than originally thought, and we have had our poor Server Admins turn the source code upside down to find out what is wrong.
We’re still working day-to-day on this issue and hope to have it fully fixed soon.
We believe we have fixed the lag issues that have been affecting us for the last 2 days.
The site is down at the moment because we want to reboot the server. In order to do this, we must gracefully shut down our services before the reboot. This may take up to 20min.
Although the problem continues to persist and annoy, the dreaded 503 errors are now gone.
You will continue to notice lag though.
We know that our users have started to receive the 503 error. We know where the problem is and we’re planning on rectifying it soon.
We’ve noticed that our front-end web server has started to lag today. We will be rebooting our server now to freshen things up.