UT4: default configuration uses retired Epic online services
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- bash, linux, shell
- Domain
- cli, devops, game-dev, infrastructure
Research direction
Start with the utserver installation instructions and compare its generated configuration with the referenced ut99/Default.ini, especially the ServerActors entries. Reproduce the start command and inspect whether the logged Epic service hostname failures are caused by configuration or connectivity; done means the server initializes and registers on master servers.
Written by the indexing model from the issue text.
Description
User story
As a user who is willing to setup Unreal Tournament server for multiple people I would like to have it working.
Game
Unreal Tournament
Linux distro
Ubuntu 24.04
Command
command: start
Further information
Apparently, the current (2025-08-30) default setup of Unreal Tournament game server (utserver), does not have the proper list of master servers. So the game server can not initialize.
As far as I understand, this file (or its parts, "ServerActors"): https://github.com/GameServerManagers/Game-Server-Configs/blob/main/ut99/Default.ini should be used. However, I was not able to find how to properly adjust the existing configs. Could you please help with finding out what I am missing?
Relevant log output
[2025.08.30-09.44.54:316][302]LogHTTP:Warning: Retry 2 on https://ut-public-service-prod10.ol.epicgames.com/ut/api/cloudstorage/system
[2025.08.30-09.44.54:316][302]LogHTTP:Warning: Retry 2 on https://ut-public-service-prod10.ol.epicgames.com/ut/api/matchmaking/session
[2025.08.30-09.44.54:349][304]LogHTTP:Warning: 0x736366867d80: request failed, libcurl error: 6 (Couldn't resolve host name)
[2025.08.30-09.44.54:349][304]LogHTTP:Warning: 0x73634fa12f80: request failed, libcurl error: 6 (Couldn't resolve host name)
[2025.08.30-09.44.54:367][305]LogHTTP:Warning: Lockout of 5.000000s on https://ut-public-service-prod10.ol.epicgames.com/ut/api/cloudstorage/system
[2025.08.30-09.44.54:367][305]LogHTTP:Warning: Lockout of 5.000000s on https://ut-public-service-prod10.ol.epicgames.com/ut/api/matchmaking/session
[2025.08.30-09.45.19:477][797]LogHTTP:Warning: Retry exhausted on https://ut-public-service-prod10.ol.epicgames.com/ut/api/cloudstorage/system
[2025.08.30-09.45.19:477][797]LogOnline:Warning: MCP: Invalid response. CorrId=UE4-0218AA722F080B1E002C01B639C3DA18 code=0 errorcode=ConnectionFailure errormessage=Connection to the server failed. errorraw=ConnectionFailure
[2025.08.30-09.45.19:477][797]LogOnline:Warning: MCP: EnumerateFiles request failed. Connection to the server failed.
[2025.08.30-09.45.19:477][797]LogHTTP:Warning: Retry exhausted on https://ut-public-service-prod10.ol.epicgames.com/ut/api/matchmaking/session
[2025.08.30-09.45.19:477][797]LogOnline:Warning: MCP: CreateSession request failed. Invalid response. CorrId=UE4-05EFF76D31080B1E002C00AA39DE4BA8 code=0 errorcode=ConnectionFailure errormessage=Connection to the server failed. errorraw=ConnectionFailure
[2025.08.30-09.45.19:527][800]LogOnline:Warning: Async task 'FOnlineAsyncTaskMcpCreateSession bWasSuccessful: 0 Session: Game' failed in 30.756137 seconds
Steps to reproduce
- Install
utserverfollowing instructions on https://linuxgsm.com/servers/utserver/ - Start it with
./utserver startcommand.
- Dominant language
- Shell
- Stars
- 4.9k
- Forks
- 866
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 100
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
GameServerManagers/LinuxGSM#5241 ·
Maintainers usually reply within 1 day
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
GameServerManagers/LinuxGSM#5240 ·
Maintainers usually reply within 1 day
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
GameServerManagers/LinuxGSM#5238 ·
Maintainers usually reply within 1 day
-
engine: null game: Teamspeak 3
Difficulty 3/5 Half a day Newbie friendliness 66/100
GameServerManagers/LinuxGSM#5237 ·
Maintainers usually reply within 1 day
All issues in GameServerManagers/LinuxGSM
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100