Page 1 of 3

General "Epic Masterserver is down!" thread.

Posted: Sun Sep 24, 2017 4:42 pm
by Darkelarious
WHAAAaaaa :wtf:

The Epic Games masterserver is offline/doesn't work anymore!
Spoiler
PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC PANIC

Code: Select all

[2017-09-23 17:13:34]	[applet-rx]	found 634 addresses at 199.255.40.174 for ut.
[2017-09-23 18:13:34]	[applet-rx]	found 637 addresses at 199.255.40.174 for ut.
[2017-09-23 19:13:34]	[applet-rx]	found 630 addresses at 199.255.40.174 for ut.
[2017-09-23 20:13:34]	[applet-rx]	found 634 addresses at 199.255.40.174 for ut.
[2017-09-23 21:13:34]	[applet-rx]	found 633 addresses at 199.255.40.174 for ut.
[2017-09-23 22:13:34]	[applet-rx]	found 633 addresses at 199.255.40.174 for ut.
[2017-09-23 23:13:34]	[applet-rx]	found 628 addresses at 199.255.40.174 for ut.
darkelarious@m5a-333networks:/mnt/deimos/web/333networks/log$ cat MasterServer-2017-week39.log | grep 199.255.40.174
[2017-09-24 00:13:34]	[applet-rx]	found 631 addresses at 199.255.40.174 for ut.
[2017-09-24 01:13:34]	[applet-rx]	found 637 addresses at 199.255.40.174 for ut.
[2017-09-24 02:13:34]	[applet-rx]	found 636 addresses at 199.255.40.174 for ut.
[2017-09-24 03:13:34]	[applet-rx]	found 640 addresses at 199.255.40.174 for ut.
[2017-09-24 04:13:34]	[applet-rx]	found 640 addresses at 199.255.40.174 for ut.
[2017-09-24 05:13:32]	[refused]	on 199.255.40.174:28900.
[2017-09-24 06:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 07:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 08:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 09:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 10:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 11:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 12:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 13:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 14:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 15:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 16:13:22]	[refused]	on 199.255.40.174:28900.
[2017-09-24 17:13:22]	[refused]	on 199.255.40.174:28900.
Above: the number of servers found at Epic's masterserver and the failures today.
Now we all got that off our chests, I would like to share my observation that the Epic Games masterserver stopped accepting connections earlier today, at 0500h GMT.
This comes as no surprise.
This happened last year (and picture below)
This happened the year before
And now it happened this year.

What happens next? If empirical data is reliable, the masterserver should be online shortly and accepting connections again soon as in the figure below.

Image

In the meanwhile, consider migrating to one of the 333networks masterservers.

Psst! We have a new version coming soon!

Re: General "Epic Masterserver is down!" thread.

Posted: Sun Sep 24, 2017 7:31 pm
by Chamberly
Sounds like they are doing some kind of yearly reset?

Re: General "Epic Masterserver is down!" thread.

Posted: Sun Sep 24, 2017 8:00 pm
by Terraniux
I'm sorry if I sound stupid, my first time doing this: but this code:

Code: Select all

Game Client Configuration

As player, you can configure your game in the following way: find your configuration file, usually called "GameName.ini", where GameName is often the title of the game. It is often located in the "System" directory of the program files of the game. Then, find and add/alter the following lines.
[UBrowserAll]
ListFactories[0]=UBrowser.UBrowserGSpyFact,MasterServerAddress=master.333networks.com,MasterServerTCPPort=28900,Region=0,GameName=ut
ListFactories[1]=UBrowser.UBrowserGSpyFact,MasterServerAddress=master.noccer.de,MasterServerTCPPort=28900,Region=0,GameName=ut
ListFactories[2]=UBrowser.UBrowserGSpyFact,MasterServerAddress=master.errorist.tk,MasterServerTCPPort=28900,Region=0,GameName=ut
ListFactories[3]=UBrowser.UBrowserGSpyFact,MasterServerAddress=utmaster.epicgames.com,MasterServerTCPPort=28900,Region=0,GameName=ut
bFallbackFactories=False

[UBrowser.UBrowserMainClientWindow]
bKeepMasterServer=True
Do I replace the old lines or add these lines? 'Alter' isn't entirely clear to me.

Thanks for efforts to be a good network.

Re: General "Epic Masterserver is down!" thread.

Posted: Sun Sep 24, 2017 8:56 pm
by OjitroC
Terraniux wrote: Do I replace the old lines or add these lines? 'Alter' isn't entirely clear to me.
Replace your current ListFactories, bFallBackFactories and bKeepMasterServer lines with those lines.

Re: General "Epic Masterserver is down!" thread.

Posted: Mon Sep 25, 2017 6:35 pm
by Darkelarious
Terraniux wrote: Do I replace the old lines or add these lines? 'Alter' isn't entirely clear to me.
Thanks, documentation updated to reflect that. See below the code/example. Please let me know if this is more helpful, or how I should describe it instead.

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 1:37 pm
by Darkelarious
Update:
The Epic masterserver still appears offline. This did not happen in the years before. Either Epic did not get to solving it yet, or there are more serious problems than we originally anticipated. Does anybody have more information about this?

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 2:21 pm
by nogardilaref
You can contact Flak directly through PM here: https://www.epicgames.com/unrealtournament/forums/
In the previous years, it was always upon contacting her that Epic got the master server fixed, she's cool. :mrgreen:

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 2:28 pm
by RocketJedi
master server is working fine for me.

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 2:30 pm
by Aldebaran
I have problems too with the server browser when using MasterServerAddress=utmaster.epicgames.com + MasterServerTCPPort=28900. Then the connection failed.

Server uplinks with MasterServerAddress=utmaster.epicgames.com + MasterServerPort=27900 seems to work fine.

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 3:44 pm
by sektor2111
Aldebaran wrote:Server uplinks with MasterServerAddress=utmaster.epicgames.com + MasterServerPort=27900 seems to work fine.
Not relevant. You can upload a false heart-beat even to Google, because address is alive that doesn't mean it do works properly. An address bound makes no sense unless you will want to do some test VIA some Explorer to see "wookie" message or some "\secure\blabla\" - that's the response not the ping or "bound to".
At this moment "noccer" seems in outage as well for me... it's not "wookie-ing" me back.

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 4:27 pm
by Aldebaran
I can see my server while using other query server than from Epicgames (although Epicgames is used for uplink). But perhaps you are right and the query server has a cached list or similiar and does not show only actual servers.

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 5:49 pm
by Darkelarious
For me, the TCP connection on utmaster.epicgames.com 28900 is (still) refused. This implies that there is no masterserver on that port receiving my request to open a connection.
Qwerty wrote:master server is working fine for me.
Could you please elaborate on what is working for you? If you have utmaster.epicgames.com AND one of the 333networks masterservers in your entries, it is that 333networks masterserver entry that responds with the list while utmaster.epicgames.com still times out.
sektor2111 wrote:At this moment "noccer" seems in outage as well for me... it's not "wookie-ing" me back.
Correct, noccer's masterserver is down. I had contact with noccer and he elaborated on personal issues. Dr.Flay may post more about that at some point in a different thread.
nogardilaref wrote:You can contact Flak directly through PM here: https://www.epicgames.com/unrealtournament/forums/
In the previous years, it was always upon contacting her that Epic got the master server fixed, she's cool. :mrgreen:
Is there somebody who already did? I think there's no point in 30 people contacting her about the same thing at the same time. Still, given the time that it has been offline and the amount of questions/complaints on IRC, forums and discord, I assume that Epic is aware of it by now. Let's see how this goes.

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 9:10 pm
by RocketJedi
I stand corrected.

I forgot about the list factories. here is my setup that is working.

Code: Select all

ServerActors=IpServer.UdpServerUplink MasterServerAddress=unreal.epicgames.com MasterServerPort=27900
ServerActors=IpServer.UdpServerUplink MasterServerAddress=master0.gamespy.com MasterServerPort=27900
ServerActors=IpServer.UdpServerUplink MasterServerAddress=master.mplayer.com MasterServerPort=27900

ListFactories[0]=UBrowser.UBrowserGSpyFact,MasterServerAddress=master.333networks.com,MasterServerTCPPort=28900,Region=0,GameName=ut
ListFactories[1]=UBrowser.UBrowserGSpyFact,MasterServerAddress=master.noccer.de,MasterServerTCPPort=28900,Region=0,GameName=ut
ListFactories[2]=UBrowser.UBrowserGSpyFact,MasterServerAddress=utmaster.epicgames.com,MasterServerTCPPort=28900,Region=0,GameName=ut

Re: General "Epic Masterserver is down!" thread.

Posted: Tue Sep 26, 2017 9:41 pm
by sektor2111
Good luck with your GameSpy. Clearly you don't get how to test a MasterServer.

You are browsing 333Networks if that quote is from client, and client doesn't do any heart-beat, it's just browsing Masters.

If quote is from servers I have doubts about how visible is that server :lol: .
Epic is/was in failure a lot of times, GameSpy is dead for years, and that "master.mplayer" for me was not that operational for a while so I deleted it years ago...
As a note, I have removed all "serveractors" lines from client because... client is not a server so "serveractors" definition have no meaning in a client, and I did the same with ServerPackages - these have no purpose for client.

Re: General "Epic Masterserver is down!" thread.

Posted: Wed Sep 27, 2017 12:31 am
by MrLoathsome
Something has indeed changed this week.

My UBrowerAll lines:

Code: Select all

[UBrowserAll]
ListFactories[0]=UBrowser.UBrowserGSpyFact,MasterServerAddress=master.333networks.com,MasterServerTCPPort=28900,Region=0,GameName=ut
ListFactories[1]=UBrowser.UBrowserGSpyFact,MasterServerAddress=gsm.qtracker.com,MasterServerTCPPort=28900,Region=0,GameName=ut
ListFactories[2]=UBrowser.UBrowserGSpyFact,MasterServerAddress=utmaster.epicgames.com,MasterServerTCPPort=28900,Region=0,GameName=ut
bHidden=False
bFallbackFactories=False
Relevant log file lines after checking for available servers:

Code: Select all

Log: Resolving master.333networks.com...
Log: Resolving gsm.qtracker.com...
Log: Resolving utmaster.epicgames.com...
Log: Resolved master.333networks.com (84.83.176.234)
ScriptLog: UBrowserGSpyLink: Master Server is master.333networks.com:28900
Log: Resolved gsm.qtracker.com (65.112.87.186)
ScriptLog: UBrowserGSpyLink: Master Server is gsm.qtracker.com:28900
Log: Resolved utmaster.epicgames.com (199.255.40.174)
ScriptLog: UBrowserGSpyLink: Master Server is utmaster.epicgames.com:28900
ScriptLog: UBrowserGSpyLink: Couldn't connect to master server.
Log: CheckConnectionAttempt: Error while checking socket status.
As sektor2111 pointed out, although the utmaster.epicgames.com master is replying to the initial ping
it is NOT working properly as a master server atm.

I have 2 suggestions for those still having issues.

1. Change the order of your lines so that the utmaster.epicgames.com is the last one in the list.
2. Check to make sure value bKeepMasterServer is set to True in the [UBrowser.UBrowserMainClientWindow] section.

*A couple days ago, when my client was not finding any servers, something very odd I had not seen before was happening.
The epicgames master server was clearing out all my list factories, and putting back just the epicgames server AND
the old, dead, master0.gamespy.com. It did this several times, until I set the bKeepMasterServer=True.
Now it seems fine and located 614 servers.

Note, for 17 years, as far as I know, that bKeepMasterServer value has been set to False in all my client UT.ini files, with no problems.
Why it is suddenly relevant is a mystery to me.

Also, none of my servers have shown any errors on the console/log when resolving all 3 of the above and binding the ports.
No change was needed to any of their ini files.