Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Headless Clients won't connect #70

Closed
ToasterBR opened this issue Sep 16, 2017 · 2 comments
Closed

Headless Clients won't connect #70

ToasterBR opened this issue Sep 16, 2017 · 2 comments

Comments

@ToasterBR
Copy link

Hi all, hi @Dahlgren

After the #39 , the HC's aren't connecting to the main web server.
After some investigation, I believe the problem is the template (config.tpl) in the node arma server library, responsible to write a server config to the spawned server.

headlessClients[] = {
  <% _.forEach(headlessClients, function(client) { %>
    "<%= client %>",
  <% }) %>
};
localClient[]={
  <% _.forEach(localClient, function(client) { %>
    "<%= client %>",
  <% }) %>
};

Using this way, both headlessClients and localClient would be inserted with a comma in the end, like this:

headlessClients[] = {
  
    "127.0.0.1",
  
};
localClient[]={
  
    "127.0.0.1",
  
};

Also, I inserted battleyeLicense = 1; in the template as some guides recommend you to do it but I don't know if this will be of any difference.

To make this work again, I changed the template to:

headlessClients[] = {<% _.forEach(headlessClients, function(client) { %>"<%= client %>"<% }) %>};
localClient[]={<% _.forEach(localClient, function(client) { %>"<%= client %>"<% }) %>};

After this change, the HCs were able to connect again in the server.

Server is Windows 10, by the way.

Thanks!

@Dahlgren
Copy link
Owner

Dahlgren commented Sep 16, 2017

That's odd, I can use multiple HCs without any issues. Tested on Windows 10. Works fine with and without BattleEye enabled. Do you have any custom parameters or other quirks?

Server
server

HC1
hc

@ToasterBR
Copy link
Author

Well, that's strange...
Tried to undo my modifications and it worked...
I believe this could be a local problem, so I will close this issue :)
Thanks for the help, @Dahlgren!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants