Cannot login with newly created user [SOLVED]

[Styx]

Hi,

My son wanted to play FAF, so I made him create an account (as I do not want him to use mine), but it is impossible to log in with it.
The FAF client get "stuck" at the "Logging in..." status

The interesting things, is that is still works properly with my account, I have no issue to log in. It's just his newly created account that does not go through.

I even uninstalled and reinstalled FAF.

His account username is: some1

I cleared the log before I try to connect with his account, and here is the content of
forever.log

Code: Select all

2015-04-13 08:34:12,357 INFO     faf.main             >>> --------------------------- Application Launch
2015-04-13 08:34:13,036 DEBUG    faf.fa.relayserver   initializing...
2015-04-13 08:34:13,036 INFO     faf.fa.proxies       binding socket 0 on port 12001
2015-04-13 08:34:13,036 INFO     faf.fa.proxies       binding socket 1 on port 12002
2015-04-13 08:34:13,036 INFO     faf.fa.proxies       binding socket 2 on port 12003
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 3 on port 12004
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 4 on port 12005
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 5 on port 12006
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 6 on port 12007
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 7 on port 12008
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 8 on port 12009
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 9 on port 12010
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 10 on port 12011
2015-04-13 08:34:13,046 INFO     faf.secondaryServer.Statistic Instanciating secondary server.
2015-04-13 08:34:13,046 INFO     faf.util             Read common stylesheet: client/client.css
2015-04-13 08:34:13,127 INFO     faf.util             Read common stylesheet: stats/formatters/style.css
2015-04-13 08:34:13,137 INFO     faf.secondaryServer.Tournament Instanciating secondary server.
2015-04-13 08:34:13,137 INFO     faf.util             Read common stylesheet: tournaments/formatters/style.css
2015-04-13 08:34:13,137 DEBUG    faf.vault            Map Vault tab instantiating
2015-04-13 08:34:14,167 DEBUG    faf.modvault         Mod Vault tab instantiating
2015-04-13 08:34:14,207 DEBUG    faf.modvault         getting installed mods. Count: 51
2015-04-13 08:34:14,217 INFO     faf.replays          Replays Widget instantiated.
2015-04-13 08:34:14,217 INFO     faf.tutorials        Tutorials instantiated.
2015-04-13 08:34:14,226 INFO     faf.util             Read common stylesheet: coop/formatters/style.css
2015-04-13 08:34:14,246 INFO     faf.fa.replayserver  listening on address 127.0.0.1:15000
2015-04-13 08:34:14,246 INFO     faf.fa.relayserver   relay listening on address 127.0.0.1:50866
2015-04-13 08:34:14,357 INFO     faf.client           Outgoing JSON Message: {"command": "ask_session"}
2015-04-13 08:34:27,960 INFO     faf.client           Attempting to login as: some1
2015-04-13 08:34:27,960 INFO     faf.client           Outgoing JSON Message: login.
2015-04-13 08:36:02,795 DEBUG    faf.downloader       Searching map preview for: final rush pro4 4v4.v0007

And uid.log

Code: Select all

Operation 0 done : success
Operation 1 done : success
Operation 2 done : success
Operation 3 done : success
Operation 4 done : success
Operation 5 done : success
Operation 6 done : success
Operation 7 done : success
Operation 8 done : success
Operation 9 done : success
encoding done
encryption done


The other logs are empty.

If that can help, here is the stack trace of the faforever.exe process found using process explorer:

Code: Select all

ntoskrnl.exe!memset+0x61a
ntoskrnl.exe!KeWaitForMultipleObjects+0xd52
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xba4
ntoskrnl.exe!PoStartNextPowerIrp+0x1821
ntoskrnl.exe!KiCheckForKernelApcDelivery+0x25
ntoskrnl.exe!KeSetActualBasePriorityThread+0xc6b
win32k.sys!W32pArgumentTable+0x597
ntoskrnl.exe!KeSynchronizeExecution+0x3a23
wow64win.dll+0x3fe2a
wow64win.dll+0x1ae6f
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x2d
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x42a
ntdll.dll!RtlUniform+0x6e6
ntdll.dll!RtlCreateTagHeap+0xa7
ntdll.dll!LdrInitializeThunk+0xe
USER32.dll!gapfnScSendMessage+0x13a
QtCore4.dll!?processEvents@QEventDispatcherWin32@@UAE_NV?$QFlags@W4ProcessEventsFlag@QEventLoop@@@@@Z+0x308
MSVCR90.dll!malloc+0x79
MSVCR90.dll!??2@YAPAXI@Z+0x1f
QtCore4.dll!?postEvent@QCoreApplication@@SAXPAVQObject@@PAVQEvent@@H@Z+0x19d


But I believe the program is actually waiting for an answer from the server.

[Legion Darrath]

I think this might be related to the one account per computer issue to deal with smurfs. Sheeo can probably explain it better.

[Sheeo]

Hi,

My son wanted to play FAF, so I made him create an account (as I do not want him to use mine), but it is impossible to log in with it.
The FAF client get "stuck" at the "Logging in..." status

The interesting things, is that is still works properly with my account, I have no issue to log in. It's just his newly created account that does not go through.

I even uninstalled and reinstalled FAF.

His account username is: some1

I cleared the log before I try to connect with his account, and here is the content of
forever.log

Code: Select all

2015-04-13 08:34:12,357 INFO     faf.main             >>> --------------------------- Application Launch
2015-04-13 08:34:13,036 DEBUG    faf.fa.relayserver   initializing...
2015-04-13 08:34:13,036 INFO     faf.fa.proxies       binding socket 0 on port 12001
2015-04-13 08:34:13,036 INFO     faf.fa.proxies       binding socket 1 on port 12002
2015-04-13 08:34:13,036 INFO     faf.fa.proxies       binding socket 2 on port 12003
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 3 on port 12004
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 4 on port 12005
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 5 on port 12006
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 6 on port 12007
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 7 on port 12008
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 8 on port 12009
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 9 on port 12010
2015-04-13 08:34:13,046 INFO     faf.fa.proxies       binding socket 10 on port 12011
2015-04-13 08:34:13,046 INFO     faf.secondaryServer.Statistic Instanciating secondary server.
2015-04-13 08:34:13,046 INFO     faf.util             Read common stylesheet: client/client.css
2015-04-13 08:34:13,127 INFO     faf.util             Read common stylesheet: stats/formatters/style.css
2015-04-13 08:34:13,137 INFO     faf.secondaryServer.Tournament Instanciating secondary server.
2015-04-13 08:34:13,137 INFO     faf.util             Read common stylesheet: tournaments/formatters/style.css
2015-04-13 08:34:13,137 DEBUG    faf.vault            Map Vault tab instantiating
2015-04-13 08:34:14,167 DEBUG    faf.modvault         Mod Vault tab instantiating
2015-04-13 08:34:14,207 DEBUG    faf.modvault         getting installed mods. Count: 51
2015-04-13 08:34:14,217 INFO     faf.replays          Replays Widget instantiated.
2015-04-13 08:34:14,217 INFO     faf.tutorials        Tutorials instantiated.
2015-04-13 08:34:14,226 INFO     faf.util             Read common stylesheet: coop/formatters/style.css
2015-04-13 08:34:14,246 INFO     faf.fa.replayserver  listening on address 127.0.0.1:15000
2015-04-13 08:34:14,246 INFO     faf.fa.relayserver   relay listening on address 127.0.0.1:50866
2015-04-13 08:34:14,357 INFO     faf.client           Outgoing JSON Message: {"command": "ask_session"}
2015-04-13 08:34:27,960 INFO     faf.client           Attempting to login as: some1
2015-04-13 08:34:27,960 INFO     faf.client           Outgoing JSON Message: login.
2015-04-13 08:36:02,795 DEBUG    faf.downloader       Searching map preview for: final rush pro4 4v4.v0007

And uid.log

Code: Select all

Operation 0 done : success
Operation 1 done : success
Operation 2 done : success
Operation 3 done : success
Operation 4 done : success
Operation 5 done : success
Operation 6 done : success
Operation 7 done : success
Operation 8 done : success
Operation 9 done : success
encoding done
encryption done


The other logs are empty.

If that can help, here is the stack trace of the faforever.exe process found using process explorer:

Code: Select all

ntoskrnl.exe!memset+0x61a
ntoskrnl.exe!KeWaitForMultipleObjects+0xd52
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PoStartNextPowerIrp+0xba4
ntoskrnl.exe!PoStartNextPowerIrp+0x1821
ntoskrnl.exe!KiCheckForKernelApcDelivery+0x25
ntoskrnl.exe!KeSetActualBasePriorityThread+0xc6b
win32k.sys!W32pArgumentTable+0x597
ntoskrnl.exe!KeSynchronizeExecution+0x3a23
wow64win.dll+0x3fe2a
wow64win.dll+0x1ae6f
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x2d
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x42a
ntdll.dll!RtlUniform+0x6e6
ntdll.dll!RtlCreateTagHeap+0xa7
ntdll.dll!LdrInitializeThunk+0xe
USER32.dll!gapfnScSendMessage+0x13a
QtCore4.dll!?processEvents@QEventDispatcherWin32@@UAE_NV?$QFlags@W4ProcessEventsFlag@QEventLoop@@@@@Z+0x308
MSVCR90.dll!malloc+0x79
MSVCR90.dll!??2@YAPAXI@Z+0x1f
QtCore4.dll!?postEvent@QCoreApplication@@SAXPAVQObject@@PAVQEvent@@H@Z+0x19d


But I believe the program is actually waiting for an answer from the server.

Hey Styx,

We currently don't allow multiple accounts on the same computer, for the purpose of preventing smurfs.

A way to work around this is to verify both accounts with steam (In the client, goto Options -> Settings -> Link account to steam), though it requires having two steam accounts with the game.


Sorry for the inconvenience, we're discussing other measures for smurf prevention still. I hope you can work this out until then.

[Styx]

A way to work around this is to verify both accounts with steam (In the client, goto Options -> Settings -> Link account to steam), though it requires having two steam accounts with the game.

Well I could link to our steam accounts, but we do not have the game on steam (I have the original retail box).

There has to be another way. Do you want to verify on Skype or another voice chat service in order to get confirmation that we are 2 different physical persons?

[Sheeo]

A way to work around this is to verify both accounts with steam (In the client, goto Options -> Settings -> Link account to steam), though it requires having two steam accounts with the game.

Well I could link to our steam accounts, but we do not have the game on steam (I have the original retail box).

There has to be another way. Do you want to verify on Skype or another voice chat service in order to get confirmation that we are 2 different physical persons?

It's not about trusting that you are two different persons, unfortunately -- at the minute our technical setup enforces this requirement, and I'm unable to make a special exemption for any account. We have talked about adding such a thing for a long time though, so I'll see if I can push it into our next server update.

[Styx]

That would be nice. I understand that we want to prevent smurfs from creating multiple accounts and polluting the community, but maybe a more targeted approach would work too: by default, you can have multiple accounts on the same computer. But if you get identified as a smurf by the community, then one of your account gets flagged as a smurf and you cannot use the others (same way it works as it does now, but just for designated accounts).

BTW, I double checked, and I do have Supreme commander + FA on my Steam account (I probably was able to add it using the serial # from the retail box), but my son does not.
If I do family sharing on Steam and share the game with him, will that work once I link our FAF accounts to our Steam accounts ?

[ckitching]

If I do family sharing on Steam and share the game with him, will that work once I link our FAF accounts to our Steam accounts ?

Almost certainly: The system isn't that clever.

There are a bunch of problems here:
- The smurf-detector doesn't *tell* you that you can't login because you tripped it, it just spins forever.
- The fact you can work around it by linking with steam makes the smurf detector entirely ineffective anyway.
- You can just spoof your UID to confuse the smurf detector.
- Smurfing clearly still happens, so the smurf detector *isn't working*. We have a ban database full of manually-detected smurfs it failed to stop. It's not doing its job, but it is causing silly problems like this.

In my opinion, we should kill this inherited failed experiment before it kills any more of our new users. Playing against a smurf is a bad experience for a new player. Not being able to play at all is much worse.

[Ze_PilOt]

- The smurf-detector doesn't *tell* you that you can't login because you tripped it, it just spins forever.

That's a bug introduced when Sheeo took over. It wasn't the case before (it was even linking to the steamlink page)

- The fact you can work around it by linking with steam makes the smurf detector entirely ineffective anyway.

No. It check the games owned in your game list, I'm quite sure that it does not return family sharing games. Either way, easily detectable with the steamAPI.

- You can just spoof your UID to confuse the smurf detector.

Not everyone can do it. Actually, only a few can.

- Smurfing clearly still happens, so the smurf detector *isn't working*. We have a ban database full of manually-detected smurfs it failed to stop. It's not doing its job, but it is causing silly problems like this.

It is working for most of the users who try to smurf. It doesn't for some "smarter" guys that are banned manually, but remove it and you will have 1000x more manual bans to place than now. That was the case before the UID was introduced.

In my opinion, we should kill this inherited failed experiment before it kills any more of our new users.

Or instead you could fix it (or revert it to what it was when it was working?). After all, this "failed experiment" is working for 3 years now.

[Exotic_Retard]

if you have access to 3 computers with faf you can swap 2 non-steam-linked accounts as you like iirc.

probably the most common way of smurfing imo - its definitely the easiest.

[Ze_PilOt]

if you have access to 3 computers with faf you can swap 2 non-steam-linked accounts as you like iirc.

probably the most common way of smurfing imo - its definitely the easiest.

But it's still limiting the numbers of accounts to 3. Try to remove it entirely and check the average number of accounts / unique player in 3 months...