ersan

Should be fixed if you were hosted in London. If its another DC send us an e-mail. Yes try changing datacenters if you can, it may be port redirection bug in ArmA2

Thanks, will test/add this later today for sure. You're missing the point, we physically CANNOT HOST THE MAP - our private hive software DOES NOT SUPPORT IT and we DO NOT HAVE PERMISSION from the map author to host the map. I can't be much clearer. I know it's a shitty situation and I'm sorry.

I'm not happy about it either guys - I liked the dayzland version better too but the authors have managed to piss enough people off (ayan, josh, lee, etc.) that it's not going to get any support from the community any more. The people at dayzland.eu were very adamant that no commercial hosting company (like us) should be allowed to host it and bliss dropped support for it so we literally cannot support it even if we wanted to (which I do). I had fully intended to host both versions until bliss removed dayzland.eu support, then we were forced to switch. I'm probably going to update the script restrictions today so it doesn't kick people for trying to refuel when they aren't near a gas station - the option really shouldn't even be there if they aren't near one.. dumb. You can read more about the map features here: http://development.dayztaviana.com/wiki/Features And here's a list of vehicles: http://development.dayztaviana.com/wiki/EnabledVehicles

Okay updated to DayZTaviana 1.7.4.4 (dayztaviana.com version) - vehicles were reset as previously indicated. Old backup files were invalidated because they are not compatible with the new map. Looks like one of our London nodes went offline, checking into it. EDIT: It was back up in about 10 minutes.

Just finished answering all of the e-mails, you should have your password now. In a couple hours hopefully. Seconds, leave the id blank it will automatically be assigned.

Yeah, not sure... I'll get to the bottom of it soon.

All server/mission files are compiled --with-messaging, and enabling kill messages in your control panel will compile with --with-killmsgs (except for lingor which kill messages do not work with and thus the option is unavailable). The issue is either bliss or individual server configuration. I know there was a problem with the mission file that was blocking global chat messages (like kill messages and messaging) that was supposed to be fixed with this commit https://github.com/ayan4m1/DayZ-Private/commit/70ac776e549e785797185773da675278b816308d and then shortly thereafter there was a problem with compiling multiple mission file changes that was supposed to be fixed with this commit https://github.com/ayan4m1/DayZ-Private/commit/fc4adf6aa78dc9c463346065b8a4ffb1772a92cc but some maps seem to still have problems. I haven't had time to do further testing so I don't know exactly where the problem is yet. When I do I will submit a bug report to bliss.

Things are starting to return to normal after the hacking incident earlier in the week, sorry about the late responses on e-mails but we'll be answering all of them today. We added new servers at every location except Salt Lake City (which will be available wednesday or thursday due to hardware shortage) so there should be availability everywhere except SLC. We also added a new location: San Jose, California and setup a test server in Singapore San Jose Test Server Hive: DayZ.ST Hive IP: 50.23.115.101:2302 Singapore Test Server Hive: DayZ.ST Hive IP: 216.185.103.153:2302 Also we will be transitioning to dayztaviana.com's version of Taviana later today. Unfortunately the vehicles and spawns are too different between the versions so we cannot keep them when transitioning, player data *should* be transferrable unless we give further notice. If you are an advanced user you can have a go at re-mapping the vehicles yourself, just make a backup of your database now. Sorry we've been behind on e-mails since all of the hacker problems earlier in the week, we've just caught up on security audits and fixing all of the servers and we are going to clear out the inbox now, this isn't how we normally operate and we should be getting things back to normal soon - our apologies. This is an old bug that was introduced in an ArmA2 beta, you need to change your ports to fix it - you can do this by switching to another location and back again. Any players that had your server saved in favorites will need to update their favorites. We do not support manual payments. If you want to reinstate your subscription send an e-mail to admin@dayz.st with your username and subscription ID. You will have to sign up for a new subscription using the same username on the day that your subscription expires after we respond to your e-mail. Database passwords were changed yesterday, check your control panel for the new password. We have no choice but to support dayztaviana.com's version and drop support for dayzland.eu - bliss no longer supports dayzland.eu and our servers use bliss. We have to switch if we want to continue receiving bliss updates. I did my very best to try and re-map the dayzland.eu vehicles to the dayztaviana.com version but it's just not possible - there are way too many differences. Very sorry about how long it's taking to get FTP, this hacker business earlier in the week has put a hold on any new features while we continue our security audits and catch up on support e-mails. DayZCommander is no longer linked to Vilayer other than the referral link for servers (which we are still negotiating about, it may stay as is) - we now host all of the files and provide all bandwidth for DayZCommander, Vilayer does not any more. I talked to Josh and I think it's fairly likely that dayzcommander will stop supporting dayzland.eu Taviana in the near future. FTP doesn't pose a security problem as much as a logistics problem. We have a very different way of hosting servers that is cloud-based (config, mission, server, etc. files are generated on the fly and downloaded anytime a server is restarted, that is how we can provide managed servers on such a large scale). If we provide FTP access there are many files you won't be able to edit with it, including mission.pbo, server.pbo, arma2.cfg, profile file (edit tracers, map icon, nameplates, crosshairs, etc.), server.cfg (which will never be available because that is where max players and other important settings are held), and DayZ/map pbo's (which will also likely not be editable). The only useful things you can do with it right now are edit battleye script detection files, download logs more reliably, and add additional pbo's to be loaded using the @bliss directory. If we released FTP without any access to those files I assume people will be mad - anytime someone requests FTP access it is usually to make changes to the server pbo or mission files, so we have to come up with an alternative way to edit those files - that's what is taking so long.

Try restarting your server (stop/start)? That should be the first thing anyone does if they can't connect to their server. Gametracker does not update servers very frequently and are not a good way to determine whether or not a server is online, so it's likely that your server is up even though gametracker says it isn't. In fact I was able to connect just fine.

No hack this time, just a database glitch - it's fixed now everything should start running again in a minute.

Prolexic has a very good reputation for mitigating floods, and they would be more than capable of handling the floods that we have been receiving. They are just too expensive and the ping problem is concerning.

Been talking to Prolexic and Black Lotus about getting DDoS protection but so far it seems to be too expensive and more worryingly it will affect players' pings. Will keep at it, the other methods I'm looking into should be implemented when the two servers come back up in about 6 hours.

173.192.200.76 and 173.193.202.109 (two of our four Washington DC nodes) are down due to DDoS attack (one went down last night and one early this morning), we have some changes pending that will help the problem - I cannot guarantee that it will be fixed, DDoS attacks are a huge problem for anyone hosting any kind of server and they are very expensive and difficult to stop, in some cases it isn't possible - DayZ hosting has proven to be a magnet for these types of attacks. We also don't have an ETA on when they will be back online other than it will definitely be less than 12 hours. Once they are back the new changes will have been implemented and we'll see how things go. Sorry I don't have more information at the moment :(

Yes I already talked to josh and ayan about supporting it and it will likely be supported soon.

The control panel is back up, anyone who had the same RCon password as their control panel password will see a message with instructions on what to do before they can login to the control panel. I will post more information in a bit. Anyone who had a server with matching RCon/login passwords will now have a scrambled RCon password also, but their server should be up. Everyone's database password has also now been changed - you can get it by logging into the control panel and looking on the left side as always. The compromised database had a list of the username, RCon password, database password, and a salted hash of the password (which is not a big deal). No other sensitive information was in the database. No e-mail addresses or subscription information or real names or anything like that was stored in the database. We very seriously recommend everyone change their RCon password as soon as possible. If you use your RCon password and control panel username as a combination for your login anywhere (DayZ Forums, banking info, etc.) you should change that immediately as well. The RCon password is a plain text value and is not secure, there are likely even ways to reveal it through bugs in the ArmA2 server - do not use an important password for your RCon password ever, anywhere. UPDATE: Actually instead of relying on users to change their RCon password we are just going to scramble them all now. You can login to the control panel and change it, but we strongly recommend you do not use the same one as before.

So it was definitely the person who our host gave our passwords to yesterday - they downloaded files off of one of the servers they had access to and used them to exploit one of our databases. We are attempting to repair the problem now - the backup we had was from last night so anyone who has signed up since then *may* end up with a different port than they had before - and if you moved servers since then you'll still be on the old one. We'll recover, as we always do - I'll have more information soon. Most servers are not offline right now by the way, just the website. Actual dayz server databases are unaffected at the moment so don't worry about players coming back etc.

Another hacking incident, today's recipe: MySQL Injection. Taking the control panel offline until it is sorted. Also 173.192.200.76 and 173.193.202.109 are being DDoS'ed. I just woke up 20 minutes ago, it's 8AM

A Washington DC node (173.193.202.109) is down due to DDoS attack, we are doing our best to mitigate it but it's still ongoing. These attacks are starting to become a real problem - I've never in my life worked with a company that was such a magnet for them... I think I have an idea for a way to make it so that when there is a DDoS attack less servers will be affected by it - I'm going to work on implementing it as soon as possible. When they happen they are very very large floods (over 10gbit sometimes) and they last for several hours. We have access to Cisco Guard and some other enterprise level DDoS mitigation hardware but true DDoS protection for attacks of this size costs thousands and thousands of dollars a month for each server, which is not viable. Right now when a server is DDoS'ed up to 16 dayz servers can be taken offline until the attack subsides - I think I know of a way to get that down to more like 3. Also the targets are ALWAYS Washington DC or Dallas. I think it might be a specific customer that is attracting them but haven't been able to pinpoint it as such, the changes I mentioned above will help narrow it down to see if we can determine a common thread and if there is anything we can do about it. Our company isn't the target it always seems to be some argument between a server admin and a player, usually because they are hacking, said player gets banned and then DDoS'es the server in retaliation. Other servers on the node are just collateral damage.

No we are not, it should be fixed now - sorry.

Bliss is supporting the other version (dayztaviana.com) instead due to drama with the dayzland.eu creators (I think the one causing the most problems is AlexSpain). They want to be able to decide who's allowed to host 'their' map (and have been very vocal about companies like us not being allowed to host it). They've pissed enough people (ayan-bliss lead developer, dotjosh-dayzcommander developer, vilayer/hfb and even us to some extent) that everyone is dropping support for them, so their version of the map will fall into obscurity soon enough I'm sure - there will be barely any servers running it when we switch (we host 35% of all servers running the map). You should still be able to customize the other version, in fact it's probably going to be far more customizable than most maps from what I've been told. I liked and was trying to support the dayzland.eu version because it had a lot of work done to it, tons of vehicle spawnpoints, different player skins, vehicles that were modified specifically for the map, and more. I have not yet tried the dayztaviana.com version but I talk to one of the developers fairly often and they know what they are doing. What I don't know is if there is an easy way to transition between versions, so any changes you have right now may or may not need to be wiped when you switch. (there will be plenty of warning so don't worry about it) - I'm trying to find a way to migrate without resetting databases currently, but some of the vehicles are different between the maps.

OK, just got up and the last Washington DC node is now up, so all servers are online. Thank you very much for being so patient everyone. We're going to switch over to the 1.7.4.4 version soon because bliss dropped support for the dayzland.eu one - and I'm sure DayZCommander will soon as well. Still trying to figure out what the best way to do this is (they have different vehicles, so we will probably temporarily leave support up for dayzland.eu and request that everyone switch, it's going to be a logistical nightmare either way) It will only log movements after it has been selected (is green) - you've got to leave the map open, updates in the database are every few minutes so you probably won't see any movement for a little while.

London node is finally up, there isn't much we can do about the Washington DC node until later today because of the DDoS attack - I'm going to sleep lol

Okay, our host was extremely apologetic and they know they screwed up... - what happened was someone faked host headers for my e-mail address (which is an extremely easy thing to do) and requested a password reset for my account, and they approved it for some inane reason. The user then proceeded to request reloads of all the operating systems on the servers from Windows to Linux - we've spent the better part of the last 10 hours clearing it all up. The datacenter has assured us that this will never happen again they will personally call me if anyone requests account changes. I know this isn't anyone's problem but our own but I figured some transparency was in order. I do not believe we were intentionally targetted for this, I think they were just shotgunning random hostnames/ips that our host has and got lucky with us. We have all but two servers online right now - 173.192.200.76 (Washingon DC-01) is down due to a DDoS attack which we are trying to get resolved by the datacenter, and 37.130.229.228 (London-05) is still being reinstalled, it should be up within the hour. During the reload we took the opportunity to update to ArmA2 beta 99515 - we will be restarting the nodes (with warnings) that weren't affected to update the arma 2 beta now. We answered any support tickets related to the downtime but frankly we are all exhausted after cleaning this up and we will resume normal support hours tomorrow. If you would like to cancel your account for a refund please do not hesitate to contact us at admin@dayz.st

We don't know, it might be dayzland - all we know is the IP that did it originated in Egypt. I honestly believe that we weren't targetted specifically - they were just targeting any customer at our datacenter. In any case we managed to recover the main server and all of the databases. Here are the details: Salt Lake City - All Servers Online Dallas - All Servers Online Amsterdam - All Servers Online Seattle - All Servers Online Singapore - All Servers Online London - All Servers Online Washington DC - All Servers Online I will update this post when new servers are fixed. The rest of the servers we are going to start slowly bringing back online one by one, I'm estimating 6 hours until everything is fully restored (but don't hold me to that) We have disabled the control panel until the mess is completely sorted out.

The backups will be within 30 minutes of when the server went offline.