Page MenuHomeFeedback Tracker

Some .bikey file combinations prevent dedicated server from loading
Assigned, WishlistPublic

Description

I have a dedicated server that I rent - on it I run a bunch of different mods and have a lot of key combinations. It seems that some particular .bikey key combinations, when placed in the \keys folder of the server, prevent it from loading.

When you attempt to connect to the server (even if the mods the keys are for aren't loaded) it hangs before you ever get to choose a mission or anything. By trial and error I discovered the keys that were causing the issue (see attached .zip files). {F25311} {F25312} {F25313}

Details

Legacy ID
3717381473
Severity
None
Resolution
Open
Reproducibility
Always
Category
Server
Steps To Reproduce
  1. Setup a dedicated server
  2. Add the keys from 'working.zip' to the '\keys' folder of the server.
  3. Connect to the server with no mods enabled (only the keys need to be there)
  4. Start the server and notice you get to the map/mission select screen.
  5. Stop the server.
  6. Place the key from 'broken.zip' into the '\keys' folder alongside the existing keys. Keep the same (empty) mod set.
  7. Start the server to the server and notice when you connect it hangs before the map/mission select screen.

Event Timeline

Anton edited Steps To Reproduce. (Show Details)Dec 25 2014, 4:52 AM
Anton edited Additional Information. (Show Details)
Anton set Category to Server.
Anton set Reproducibility to Always.
Anton set Severity to None.
Anton set Resolution to Open.
Anton set Legacy ID to 3717381473.May 7 2016, 8:01 PM
Anton edited a custom field.
Anton added a subscriber: Anton.May 7 2016, 8:01 PM
Anton added a comment.Dec 25 2014, 4:55 AM

Ignore the 'keys.zip. It's from a messed up upload. Follow instructions in description.

Anton added a comment.Dec 25 2014, 4:57 AM

It seems that the number of dashes (- or _ characters) in the mods have an effect. I'm unable to generate a local key like 'Ares_1_5_0.bikey' or 'Ares-1-5-0.bikey' that avoids the issue. Using 'Ares150.bikey' seems to work tho.

We had a report of something to this effect happening with our rksla3.bikey file as well:

http://forums.bistudio.com/showthread.php?178555-RKSL-Attachments-Pack-1&p=2866462&viewfull=1#post2866462

Can't really work out what's causing it, or why it effects this key on their server (so far they're the only group who have mentioned this problem with our key).

Anton added a comment.Jan 28 2015, 8:56 PM

It seems like the '-' theory is busted, I found some more keys that don't work in combination with the newly renamed .bikey file (without the dashes in the name). It has to be something internal to the game since the keys work fine in isolation. For some reason it seems to happen more often with map packs that we try.

I'm not sure if it has something to do with the way the key is generated or something. No matter what, there's an issue in the game where some key combinations hang the server.

Anton added a comment.Jan 28 2015, 8:58 PM

BTW the only workaround I have at the moment is to continue to generate different keys until I get one that works with the mod combination that was having an issue, and then re-release with the mod signed with that new key.

Jonpas added a comment.Feb 2 2015, 6:55 PM

From what I can see it's random or at least there is are visible reproduction steps, here is what I was doing past 2 days trying to figure things out.

First, key "CCIP_v0.3a" was conflicting with key "jns_skycranes", removing either of them fixed the issue. Renaming second to "jnsSkycranes" for example fixed the issue, but renaming first to dash or underscore instead of a dot did NOT fix it while renaming it to exclude the dot (03 together) fixed it.

(Arma 3 Tools also doesn't support a dot in the key's name, I've already reported that to the mod's author.)

Second, after I resolved above, I made another random key "missing_units_usec" which conflicted with "jns_skycranes" as well, removing either fixed it yet again. Then renaming first one to "missingUnits_usec" or "missing_units-units" fixed it as well, while renaming it to "missing_units" or "missing_units-usec" or "missing-units_usec" or "missing-units-usec" did NOT fix it.
Renaming second to "jnsSkycranes" or even "jns_sycranes" (without 'k') fixed the issue as well.

'renaming' in all above context means creating a new key, as renaming it plainly doesn't change anything at all. That leads me to a conclusion that the key's name somehow gets corrupted in the actual encryption of the key or whatever it does, so it's not referencing itself correctly or something along the lines.

Jonpas added a comment.Feb 3 2015, 6:11 PM

@LondonLand

It's not the same, but it's related. Since my old bikey "jns_skycranes" bugged out with just one other key (that I could find), but the key was created by previous Arma 3 Tools (stable), the new one with dev-branch and new one "jnsSkycranes" works.

Jonpas added a comment.Mar 8 2015, 5:50 PM

More time showed another interesting thing. With a bunch of mods and keys all worked, removing "randomslap.bikey" broke it again. Yes, *removing* it, this is not making any sense anymore...

Removing ANY other key next to that one made it work again.

RRMule added a subscriber: RRMule.May 7 2016, 8:01 PM

I also experience this issue when hosting a non-dedicated server for coop play. Any time I click on 'next' when internet game is selected it will crash arma before mission select screen comes up. Removing mods at random will cause it to eventually work.

There is no way through log files that I know of that would allow me to determine which bikey files cause the issue specifically.

The issue its a bit deeper than keys, sometimes changing loaded addon or even addon load order can result on the server soft-lock the same way.

But its really hard to probide a repo for it because the combinations that cause it seems to be totally random

Looks like they made some changes in Dev Branch 1.46 regarding this. Is this still a problem there?
Re: Fixed: Server issue when using a larger list of BIKEY signature files
Source: http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog&p=2939180&viewfull=1#post2939180

this issue should be resolved in Arma 3 DEV 1.45 and Arma RC 3 1.46 and A2: OA 1.63 beta

This should probably be resolved as fixed and closed.