Whitelist didn't work anymore - Hotfix 29.06.2020

Until now my Server run with a Whitelist and did work perfectly. After the Patch by Joining the Server a warning WIndow appears that this Server run on Whitlist. So long so good. The whitelist.txt is still on the same place with the same content. Did the place that theyre file to be chanced withut documentation? Did the patch destroyd the whitelist system completly?

Serverlog from the moment of the login:

[2020.06.29-11.18.14:736][118]LogNet: NotifyAcceptingConnection accepted from: ■■■.■■■.■■■.■■■:50211
[2020.06.29-11.18.14:736][118]LogHandshake: SendConnectChallenge. Timestamp: 586.631287, Cookie: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2020.06.29-11.18.14:793][119]LogNet: NotifyAcceptingConnection accepted from: ■■■.■■■.■■■.■■■:50211
[2020.06.29-11.18.14:793][119]LogNet: Server accepting post-challenge connection from: ■■■.■■■.■■■.■■■:50211
[2020.06.29-11.18.14:795][119]PacketHandlerLog: Loaded PacketHandler component: Engine.EngineHandlerComponentFactory (StatelessConnectHandlerComponent)
[2020.06.29-11.18.14:795][119]LogNet: NotifyAcceptedConnection: Name: ConanSandbox, TimeStamp: 06/29/20 13:18:14, [UNetConnection] RemoteAddr: ■■■.■■■.■■■.■■■:50211, Name: IpConnection_2, Driver: GameNetDriver IpNetDriver_0, IsServer: YES, PC: NULL, Owner: NULL
[2020.06.29-11.18.14:795][119]LogNet: AddClientConnection: Added client connection: [UNetConnection] RemoteAddr: ■■■.■■■.■■■.■■■:50211, Name: IpConnection_2, Driver: GameNetDriver IpNetDriver_0, IsServer: YES, PC: NULL, Owner: NULL
[2020.06.29-11.18.14:795][119]LogNet: NotifyAcceptingChannel Control 0 server World /Game/Maps/ConanSandbox/ConanSandbox.ConanSandbox: Accepted
[2020.06.29-11.18.14:796][119]LogNet: Remote platform little endian=1
[2020.06.29-11.18.14:796][119]LogNet: This platform little endian=1
[2020.06.29-11.18.14:861][121]LogNet: Login request: /Game/Maps/Startup?Password=?Ping=34?Name=■■■%xxxx?dw_user_id=xxxxxxxxxxxxxx?mod_list=xxxxxxxxxxxxxxxx?IdentityToken_Data=xxxxxxxx?IdentityToken_IV=xxxxxxxxxx?FLSPlayerIds_TitleID=xxxxxxxxxxx?FLSPlayerIds_MasterID=xxxxxxxx userId: xxxxxxxxxxxxx
[2020.06.29-11.18.14:868][121]LogDreamworld:Display: PreLogin: xxxxxxxxxx
[2020.06.29-11.18.14:868][121]ConanSandbox:Display: User xxxxxxxxxxxx logged in from unknown country
[2020.06.29-11.18.14:868][121]LogNet: PreLogin failure: Unknown EFailureDetails. No details.
[2020.06.29-11.18.14:927][123]LogNet: UChannel::ReceivedSequencedBunch: Bunch.bClose == true. ChIndex == 0. Calling ConditionalCleanUp.
[2020.06.29-11.18.14:927][123]LogNet: UChannel::CleanUp: ChIndex == 0. Closing connection. [UChannel] ChIndex: 0, Closing: 0 [UNetConnection] RemoteAddr: ■■■.■■■.■■■.■■■:50211, Name: IpConnection_2, Driver: GameNetDriver IpNetDriver_0, IsServer: YES, PC: NULL, Owner: NULL
[2020.06.29-11.18.14:929][123]LogNet: UNetConnection::Close: [UNetConnection] RemoteAddr: ■■■.■■■.■■■.■■■:50211, Name: IpConnection_2, Driver: GameNetDriver IpNetDriver_0, IsServer: YES, PC: NULL, Owner: NULL, Channels: 1, Time: 2020.06.29-11.18.14
[2020.06.29-11.18.14:929][123]LogNet: UChannel::Close: Sending CloseBunch. ChIndex == 0. Name: [UChannel] ChIndex: 0, Closing: 0 [UNetConnection] RemoteAddr: ■■■.■■■.■■■.■■■:50211, Name: IpConnection_2, Driver: GameNetDriver IpNetDriver_0, IsServer: YES, PC: NULL, Owner: NULL
[2020.06.29-11.18.15:406][136]LogFuncomLiveServices:Display: VerifyIdentity Completed: PlayFabId - [xxxxxxxxxxxx] PlatformId - [xxxxxxxxxxxxxxxxx].
[2020.06.29-11.18.15:408][136]ConanSandbox:Error: [AConanGameMode::OnValidateResponseReceived] No corresponding Connections could be found for User Id ‘[xxxxxxxxxxxx]’

1 Like

Hey there,

Our team is aware of this issue and looking into it at this moment.
Apologies for the frustration and thanks for the feedback.

u want a feedback?

R O L L B A C K

1 Like

It is pretty easy to see why Whitelisting is no longer working with Steam IDs.

It is in the Log:
LogOnline:Warning: STEAM: Steam API disabled!

For some reason the developers thought it would be a good idea to disable the Steam API to verify Whitelist IDs.

this message is already since the big patch in the log

A decent amount of time has elapsed regarding this matter. Are there any updates we can get on how the devs are going to address this problem? Thank you.

Hey @Trexcapades

We hotfixed this issue last night. Whitelist should now be working correctly.

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.