starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #2941] ARK Server - Epic Games - Unable to connect to server (With latest patch) #2102

New issue

Closed

opened 2026-02-27 03:00:52 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 03:00:52 +03:00

Owner

Originally created by @PrivateGiles on GitHub (Jun 30, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2941

User Story

As a user, I want to be able to allow Epic games members connect to my dedicated server so that steam and epic members can play together. A new update has been released from ARK which adds in a new argument so you can specify the IP address. My server has been updated with the latest SteamCMD patch which was released, however the when the users try to connect to the server it just errors out.

Basic info

Distro: [Ubuntu 18.04]
Game: [ARK: Survival Evolved]
Command: [Server as a whole]
LinuxGSM version: [Latest Release]

Further Information

With the latest patch, I've defined the the following within my arkserver.cfg:

# Default start process based on enabling Epic Games to play on the dedicated server
## Server Start Command | https://docs.linuxgsm.com/configuration/start-parameters#additional-parameters
fn_parms(){
parms="${defaultmap}?AltSaveDirectoryName=${defaultmap}?listen?MultiHome=${ip}?MaxPlayers=${maxplayers}?QueryPort=${queryport}?RCONPort=${rconport}?Port=${port} -automanagedmods -crossplay -PublicIPForEpic=51.132.224.27"
}

However when someone from epic games tries to connect to the server it looks as if it's going to connect then takes them back to the front page of ark. When they go back in and try and re-connect to the server the error message is: "Connection Failed: Unknown Error"

To Reproduce

Steps to reproduce the behaviour:

Add the parameters to the config file
try to connect to ark dedicated server via epic games
See error

Expected behaviour

User is able to connect due to the parameter being set

Originally created by @PrivateGiles on GitHub (Jun 30, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2941 ## User Story As a user, I want to be able to allow Epic games members connect to my dedicated server so that steam and epic members can play together. A new update has been released from ARK which adds in a new argument so you can specify the IP address. My server has been updated with the latest SteamCMD patch which was released, however the when the users try to connect to the server it just errors out. ## Basic info * **Distro:** [Ubuntu 18.04] * **Game:** [ARK: Survival Evolved] * **Command:** [Server as a whole] * **LinuxGSM version:** [Latest Release] ## Further Information With the latest patch, I've defined the the following within my arkserver.cfg: ``` # Default start process based on enabling Epic Games to play on the dedicated server ## Server Start Command | https://docs.linuxgsm.com/configuration/start-parameters#additional-parameters fn_parms(){ parms="${defaultmap}?AltSaveDirectoryName=${defaultmap}?listen?MultiHome=${ip}?MaxPlayers=${maxplayers}?QueryPort=${queryport}?RCONPort=${rconport}?Port=${port} -automanagedmods -crossplay -PublicIPForEpic=51.132.224.27" } ``` However when someone from epic games tries to connect to the server it looks as if it's going to connect then takes them back to the front page of ark. When they go back in and try and re-connect to the server the error message is: "Connection Failed: Unknown Error" ## To Reproduce Steps to reproduce the behaviour: 1. Add the parameters to the config file 2. try to connect to ark dedicated server via epic games 3. See error ## Expected behaviour User is able to connect due to the parameter being set

kerem

2026-02-27 03:00:52 +03:00

closed this issue
added the
type: feature
label

kerem commented

2026-02-27 03:00:53 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Jun 30, 2020):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.59. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Jun 30, 2020): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.59. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 03:00:53 +03:00

Author

Owner

@Fr1tzl1 commented on GitHub (Jul 2, 2020):

Have you Mods installet on your Server?

@Fr1tzl1 commented on GitHub (Jul 2, 2020): Have you Mods installet on your Server?

kerem commented

2026-02-27 03:00:53 +03:00

Author

Owner

@PrivateGiles commented on GitHub (Jul 3, 2020):

No mods are installed on the server

On Thu, 2 Jul 2020, 15:43 Fr1tzl1, notifications@github.com wrote:

Have you Mods installet on your Server?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GameServerManagers/LinuxGSM/issues/2941#issuecomment-653048028,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANONR3IVZUAXXV3NHDFEPD3RZSMJVANCNFSM4OMHFW5A
.

@PrivateGiles commented on GitHub (Jul 3, 2020): Hi No mods are installed on the server On Thu, 2 Jul 2020, 15:43 Fr1tzl1, <notifications@github.com> wrote: > Have you Mods installet on your Server? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/GameServerManagers/LinuxGSM/issues/2941#issuecomment-653048028>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ANONR3IVZUAXXV3NHDFEPD3RZSMJVANCNFSM4OMHFW5A> > . >

kerem commented

2026-02-27 03:00:53 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 19, 2021):

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 (Jul 19, 2021): 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.