Me and Vilayers misadventures

[Erstad (DayZ) 0]

So about a moth ago, I bought a Vilayer server for my clan. I have come to regret this many times since.

- Problem #1 - Day #1 - Uptime in seconds: 0

So, the first time I was going to try the server (one day after buying it), it did not work at all. I couldn't even log into the ACP Control Panel. After waiting for answer on my support ticket for over a day, I was told that the name I had chosen for the server broke the server. I was told that it would be up in an hour. I decided to wait until the next day to fire it up. Here comes problem #2.

- Problem #2 - Day #2 - Uptime in seconds: 0

So, I woke up the next day to fire the server up. Logged into the ACP Control Panel, and was greeted by Server Status: UNKNOWN. After waiting for 2 days, trying to install mods/updates to no avail, I submitted yet another ticket. While waiting for my ticket, I logged into Vilayers teamspeak, hoping to get some help there. After 3 - 4 hours, someone finally came along and told me that they had major problems with servers because they were moving them all to new machines (or something like that). The answer I got from my ticket confirmed this, and I was also given a month of free servertime. "Good!", I thought.

- Problem #3 - Day #4 - Uptime in seconds: 0

By now, I really believed that my server would be up. I logged into ACP, and my hopes rose further; Server Status now said STOPPED. I installed mods and updates, and fired up the server.

Server Status changed to RUNNING.

The problem was that I was unable to find it in DayZ Commander, and in Remote Connect. So, I opened up the ACP, refreshed it, and wouldn't you know? Server Status had changed back to STOPPED."Well fuck", I though. So, I sent in yet another ticket and logged into their TeamSpeak once again. After waiting for 4 more hours, someone from Vilayer came online and said they would help me out. After 30 minutes, I got an answer on my ticket, saying that my server needed to be installed again, and that it would take an hour or so. I was satisfied, and went to bed.

18 hours later, I logged in to the ACP again.

- Problem #4 - Day #5 - Uptime in seconds: 0

Guess what was waiting for me in the ACP? A big red Server Status: UNKNOWN. Yeah, that's right, I was back to the first problem again.

So I submitted yet another ticket, and got my ass back on TeamSpeak. After more hours of waiting, I got help. The server install had failed again, and needed to be restarted. This this time it actually worked! I was so happy, playing with my friends, killing zombies and all that. But the problems did not stop there.

- Problem # 5 - Day #17 - Uptime in days: 11

So, after 11 days of glorious uptime, I decided to update the server and install a new map. That was a mistake.

You see, while I was doing that, Vilayer was installing a new update, and for some reason, they thought that giving their customers a heads-up was a bed idea.

So my server broke again, and went down. This time it was up and running in 4 - 5 hours. I installed new maps, and played for a while. Some hours later I decided that it was time for a reset of the server, because I got the chance to test Gotcha Anti-Hack (great tool, btw). I sent in a ticket, and after 2 hours someone from Vilayer started the installation. I went to bed.

- Problem #6 - Day #18 - Uptime in days: 11 and 1/2

When I woke up, I tried to log into ACP. Well, that was apparently not acceptable. Now, my username and password was all of the sudden incorrect, and after trying to retrieve password, it was clear that my account no longer existed. So, I submitted yet another ticket and got on TeamSpeak. More waiting. WHOOPWHOOP!!!

This time, someone actually answered my ticket before anyone on TeamSpeak helped me. The server re-install had failed yet again, and had been restarted. And since this takes an hour, I decided to share this with you all.

Has anyone else experienced something like this? I mean, this can't be right... Ok, I did get one month free, but still...

And to anyone who are considering Vilayer as host; do it at your own risk.

* Note that the timeline and uptime may not be 100% correct.