search

fugasjunior / arma-server-manager

A web administration tool for managing Arma 3, Arma Reforger and DayZ dedicated servers
GNU General Public License v3.0
50 stars 10 forks source link

Headless clients not connecting #131

Open domagojhack opened 1 month ago

domagojhack commented 1 month ago

Is there some more info on how to setup headless using UI. I started 3 headless clients but I cannot see them in my mission. The mission has three headless client slots.

The docs only says

Headless clients When running Arma 3 servers, you can launch or stop preconfigured headless clients with a single click.

There is no info about configuring them.

I see them in the process view however they are not showing on my server. And they are forcing only 127.0.0.1 IP to connect although I have entered my own IP in the config file

The headless client does not have an issue if I start the vanilla server without mods. Running script generated by the manager for headless clients with mods client can not detect mods in symlinks. Therefore I deduce that it is not compatible to connect to moded server.

fugasjunior commented 1 month ago

Hi, I suppose you're using Docker setup. Please correct me if I am wrong.

And they are forcing only 127.0.0.1 IP to connect although I have entered my own IP in the config file

Could you please clarify? Headless servers are meant to connect to the localhost at the same port as the server, so IP 127.0.0.1 is correct. Where did you specify your own IP?

Running script generated by the manager for headless clients with mods client can not detect mods in symlinks.

This is likely because you're running them outside the Docker container which uses different file structure. You can try to exec into the container (docker exec -it <container_name> /bin/bash), navigate to the Arma 3 server directory there (cd /home/steam/armaservermanager/servers/ARMA3) and execute the script generated by the manager there.

Also, please try to find ARMA3_<serverID>_HC 1.log log file in the logs directory (which is next to mods and servers directory). It could contain some useful information for why it cannot connect when started from the manager.

domagojhack commented 1 month ago

Hi, I suppose you're using Docker setup. Please correct me if I am wrong.

Yes.

Could you please clarify? Headless servers are meant to connect to the localhost at the same port as the server, so IP 127.0.0.1 is correct. Where did you specify your own IP?

Currently, it is set up to default (correct value).

image

This is likely because you're running them outside the Docker container which uses different file structure. You can try to exec into the container (docker exec -it /bin/bash), navigate to the Arma 3 server directory there (cd /home/steam/armaservermanager/servers/ARMA3) and execute the script generated by the manager there.

Headless clients log end with cryptic error messages: image

So yeah modless headless is connecting without issues on our vanilla server but when we load up our modpack headless clients fail to connect.