Master server still down


(ressected) #1

Players are still unable to properly load the game!

This is what people get when they try login to their account:

image

We understand this is an old game, but many people still play every day, including mod work and organized matches twice per week in both EU and NA. The Wolf:ET servers are still maintained and that game was free unlike QW which was originally $80.00 per copy I believe.

People are still making maps for this game and as you are aware is a laborious process.

Please fix this ASAP!!!

This is precisely when it started happening. The message repeats indefinitely.

Server is in NL so that is 10:16:13pm EST

Server log:
2020-01-09 16:16:13 : Dedicated server disconnected (Connection Reset) and is no longer authenticated.
2020-01-09 16:16:15 : Dedicated server signed in and is authenticated.
2020-01-09 16:16:16 : Dedicated server disconnected (Connection Reset) and is no longer authenticated.
2020-01-09 16:16:30 : Dedicated server signed in and is authenticated.

What it looks like client side.

log file ‘demonware.log’ opened on 2020-1-9, 19:44:00
2020-01-09 19:44:02 : bdNet.cpp(63): INFO: Requested port 3074, using port 3074
2020-01-09 19:44:11 : bdAuthService.cpp(887): INFO: Task completed successfully
2020-01-09 19:44:12 : bdLobbyService.cpp(481): INFO: Connected to MatchMaking Service.
2020-01-09 19:44:12 : bdLobbyService.cpp(211): INFO: Received LSG connection ID:8561024946337782337
2020-01-09 19:44:12 : bdLobbyConnection.cpp(392): INFO: Received ‘connection reset’. Closing connection.
2020-01-09 19:44:12 : bdLobbyService.cpp(487): INFO: Disconnected from MatchMaking Service.
2020-01-09 19:44:12 : bdConnectionStore.cpp(150): INFO: Disconnecting all connections.
2020-01-09 19:44:13 : bdConnectionStore.cpp(131): INFO: Closing all connections.
2020-01-09 19:44:13 : bdConnectionStore.cpp(131): INFO: Closing all connections.

Hope this helps. Thank you.


ETQW Canceled login / Connection reset issue
(REA987) #3

Is that a Demonware issue then? To my best knowledge, Demonware still maintains some legacy Activision titles. I guess it would be nice if the community reaches them to let them know about the issue. Please kindly inform Demonware regarding recent ETQW authentication issues via following e-mails;

Let us keep the game alive. :slight_smile:


(ressected) #4

Additional error messages:

log file 'demonware.log' opened on 2020-1-12, 18:30:33 2020-01-12 18:30:34 : libs/DemonWare/DemonWare-1.80/bdNet/bdNet.cpp(63): INFO: Requested port 3074, using port 3074 2020-01-12 18:32:08 : libs/DemonWare/DemonWare-1.80/bdPlatform/bdPlatformSocket/bdPlatformStreamSocket-unix.cpp(271): WARNING: wait for connect() completion (115 Operation now in progress) 2020-01-12 18:32:08 : libs/DemonWare/DemonWare-1.80/bdLobby/bdAuthService.cpp(887): INFO: Task completed successfully 2020-01-12 18:32:08 : libs/DemonWare/DemonWare-1.80/bdPlatform/bdPlatformSocket/bdPlatformStreamSocket-unix.cpp(271): WARNING: wait for connect() completion (115 Operation now in progress) 2020-01-12 18:32:08 : libs/DemonWare/DemonWare-1.80/bdLobby/bdLobbyService.cpp(481): INFO: Connected to MatchMaking Service. 2020-01-12 18:32:08 : libs/DemonWare/DemonWare-1.80/bdLobby/bdLobbyService.cpp(211): INFO: Received LSG connection ID:15656968550655860607 2020-01-12 18:32:08 : libs/DemonWare/DemonWare-1.80/bdLobby/bdLobbyService.cpp(195): INFO: Received LSG error: 500 2020-01-12 18:32:08 : libs/DemonWare/DemonWare-1.80/bdLobby/bdLobbyConnection.cpp(407): WARNING: net error. status : -1


(TAW_OldWolf) #5

Wake up SD !!
The game is still alive and there are people who wants to play !!


(REA987) #6

To provide some more input;

When I incorrectly enter password of my online account, I receive Incorrect Password error. But when I enter it correct, then I receive current Cancelled error. So, authentication server is still online to some extend as it properly checks login details but it fails to login as it seems.


(TAW_OldWolf) #7

First time this problem occured was back in July 2012, then there where some minor issues with authentication(master server in 2016 and latest one in March 2018.

The problems where fixed in a couple of weeks.
Let’s hope that this issue also will be fixed asap.

Maybe someone could have look on what happened then ??