[GH-ISSUE #4238] [Bug]: Ark: Survival Evolved should use separate IP for Multihome and EPIC #2667

New issue

Closed

opened 2026-02-27 03:04:33 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 03:04:33 +03:00

Owner

Originally created by @WildPenquin on GitHub (Jun 13, 2023).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4238

User story

The default configuration file should not use same IP for both MultiHome and PublicIPForEpic

Game

Ark: Survival Evolved

Linux distro

Other

Command

command: start

Further information

NOTE! Multihome is really badly documented - please correct me if I've guessed any misinformation here!

It seems that Multihome is used for many instances running on the same computer with many IP addresses (or interfaces). This is typically (always?) a local IP i.e. LAN address. This may sometimes be a public IP address, in case the computer is running directly on a public IP address with no NAT.

The PublicIPForEpic is always a public IP address (and is used for crossplay compatibility only?).

If both options are given, these options should be set separately and to different values. They should never match each other, or may only do so in the case if the server is not behind a NAT, but then setting PublicIPForEpic is superfluous (see Wiki documentation). If Multihome is set to a public IP address, when the server is behind a NAT, the server will fail (it will run but not listen to any connections).

In a nutshell:

Multihome is the listening address of the server (a LAN address or in case of no NAT, a public IP address)
PublicIPForEpic will always be a public IP address, and makes no sense to set if matches Multihome, i.e. is only needed only if behind a NAT (see link 1).

I suggest changing the default configuration file as such:

ip="aaa.bbb.ccc.ddd" # a public IP address - 0.0.0.0 will not work, EPIC clients can not connect!
localip="0.0.0.0" # the listen address, your local IP if behind a NAT - 0.0.0.0 will work for most users
startparameters="${defaultmap}?AltSaveDirectoryName=${altsavedirectoryname}?listen?MultiHome=${localip}?MaxPlayers=${maxplayers}?QueryPort=${queryport}?RCONPort=${rconport}?Port=${port} -automanagedmods -cro    ssplay -PublicIPForEpic=${ip}"

https://ark.fandom.com/wiki/Server_configuration

Relevant log output

No response

Steps to reproduce

Set a public IP address, using the default configuration as a base.
ip="aaa.bbb.ccc.ddd"

The server will run but not listen to any connections.

Originally created by @WildPenquin on GitHub (Jun 13, 2023). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/4238 ### User story The default configuration file should not use same IP for both MultiHome and PublicIPForEpic ### Game Ark: Survival Evolved ### Linux distro Other ### Command command: start ### Further information **NOTE!** Multihome is really badly documented - please correct me if I've guessed any misinformation here! It seems that Multihome is used for many instances running on the same computer with many IP addresses (or interfaces). This is typically (always?) a local IP i.e. LAN address. This may sometimes be a public IP address, in case the computer is running directly on a public IP address with no NAT. The PublicIPForEpic is always a public IP address (and is used for crossplay compatibility only?). If both options are given, these options should be set separately and to different values. They should never match each other, or may **only** do so in the case if the server is not behind a NAT, but then setting PublicIPForEpic is superfluous (see Wiki documentation). If Multihome is set to a public IP address, when the server is behind a NAT, the server will fail (it will run but not listen to any connections). In a nutshell: - Multihome is the listening address of the server (a LAN address or in case of no NAT, a public IP address) - PublicIPForEpic will *always* be a public IP address, and makes no sense to set if matches Multihome, i.e. is only needed only if behind a NAT (see link 1). I suggest changing the default configuration file as such: ``` ip="aaa.bbb.ccc.ddd" # a public IP address - 0.0.0.0 will not work, EPIC clients can not connect! localip="0.0.0.0" # the listen address, your local IP if behind a NAT - 0.0.0.0 will work for most users startparameters="${defaultmap}?AltSaveDirectoryName=${altsavedirectoryname}?listen?MultiHome=${localip}?MaxPlayers=${maxplayers}?QueryPort=${queryport}?RCONPort=${rconport}?Port=${port} -automanagedmods -cro ssplay -PublicIPForEpic=${ip}" ``` 1) https://ark.fandom.com/wiki/Server_configuration ### Relevant log output _No response_ ### Steps to reproduce Set a public IP address, using the default configuration as a base. `ip="aaa.bbb.ccc.ddd"` The server **will** run but not listen to any connections.

kerem

2026-02-27 03:04:33 +03:00

closed this issue
added the
type: bug

info: docs

command: start

game: Ark: Survival Evolved
labels

kerem commented

2026-02-27 03:04:34 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Sep 1, 2023):

PR has been created and the ip address docs have been updated

@dgibbs64 commented on GitHub (Sep 1, 2023): PR has been created and the ip address docs have been updated

kerem commented

2026-02-27 03:04:34 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 16, 2024):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Sep 16, 2024): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.