Login Session Expired

[silverdevil]

43 minutes ago, TOViper said:

Hey folks, I have this problem too:

in your case, we need autoupdate_log.txt found in the folder X:\DCS\

[TOViper]

here we go:

autoupdate_log.txt

autoupdate.cfg

Edited 8 hours ago by TOViper

[silverdevil]

1 hour ago, TOViper said:

here we go:

hello. i do not see any errors in the autoupdate_log. i do notice in your dcs.log that you are opening up dcs.exe from BIN-MT 

X:\DCS\bin-mt\DCS.exe

change your shortcut to 

X:\DCS\bin\DCS.exe or even better "X:\DCS\bin\DCS_updater.exe"

i am not sure this will matter. but it is a test.

[TOViper]

2 minutes ago, silverdevil said:

hello. i do not see any errors in the autoupdate_log. i do notice in your dcs.log that you are opening up dcs.exe from BIN-MT 

X:\DCS\bin-mt\DCS.exe

change your shortcut to 

X:\DCS\bin\DCS.exe or even better "X:\DCS\bin\DCS_updater.exe"

i am not sure this will matter. but it is a test.

wilco

[silverdevil]

Just now, TOViper said:

wilco

i also see you had a pretty long session without error

=== Log opened UTC 2025-09-19 12:51:50
2025-09-19 14:40:12.324 INFO    VISUALIZER (10436): render thread has stopped
=== Log closed.

[TOViper]

Yeah.
It's a nasty issue that comes up from time to time, this time I went to the forum with that.
For a user this error is just a totally unneccessary killer, because it literally stops you being able to play DCS without any reason.

[silverdevil]

2 minutes ago, TOViper said:

It's a nasty issue that comes up from time to time

i have yet to see this error on my system. when the logs indicate an error, it seems to be something on the computer or their ISP. i am sure ED tries to avoid peak hours for updating. but being literally all of the world, what would be the peak time? perhaps it happens to you because of them doing updates? also it could be their servers overburdened.

[TOViper]

Having paid all the modules and then being thrown out of DCS for such an absurd reason is really a bummer.
Why the hack is DCS permanently checking the status of a client by using a i386 computer connected to a 56k modem, standing somewhere in a wet cellar, when the authorization is anyway determined when starting up DCS? I mean, this is simply rediculos in my opinion and ED should really re-think this strategy. I am upset everytime I have a mission opened in the mission editor and then DCS quits without having me saved the mission. 

But anyway silverdevil, thanks for digging into the logs, much appreciated!

Edited 5 hours ago by TOViper

[MAXsenna]

i have yet to see this error on my system. when the logs indicate an error, it seems to be something on the computer or their ISP. i am sure ED tries to avoid peak hours for updating. but being literally all of the world, what would be the peak time? perhaps it happens to you because of them doing updates? also it could be their servers overburdened.

Many users have reported getting kicked out of the game lately. I'm sure you're right it's probably the connection, but still. ED needs better grace periods. One user has to go offline all the time to not get kicked out when he edits missions. That's not how it's supposed to work. And it doesn't happen with other games. Have only happened to me once, when I was logged in the game during a planned maintenance.

@TOViper Several users have complained lately. I'm sure it's the protection system, and suddenly the connection is "broken" for a few seconds, and it doesn't remediate by itself, when the connection is back online.

Sent from my SM-A536B using Tapatalk

[Actium]

5 hours ago, TOViper said:

Hey folks, I have this problem too:

dcs.log 1.71 MB · 4 downloads

Having a look at all occurrences of ASYNCNET on your dcs.log, it appears the session expiration occurred out of the blue by decision of the DCS master server:

2025-09-19 12:51:52.652 INFO    ASYNCNET (4780): Login success.
2025-09-19 12:51:54.241 INFO    ASYNCNET (4780): Got auth data.
2025-09-19 12:51:54.605 INFO    ASYNCNET (Main): ProtocolVersion: 408
2025-09-19 12:51:54.605 INFO    ASYNCNET (Main): Adding LAN search interface 0: 127.0.0.1 "IPv4 Loopback"
2025-09-19 12:51:54.605 INFO    ASYNCNET (Main): Adding LAN search interface 0: 255.255.255.255 "IPv4 Broadcast"
2025-09-19 14:40:01.848 ERROR   ASYNCNET (4780): The session has expired (401). Exiting...

Unless you started another DCS instance with the same account credentials, there's no good reason for the master server to do that. This is not a an issue with a spotty internet connection. If it were, the log would include messages indicating failed connection attempts. Thus, this lies within the hand of ED to figure out via logs from their master server. As BIGNEWY recommended above, do file a support ticket.

[MAXsenna]

17 minutes ago, Actium said:

Thus, this lies within the hand of ED to figure out via logs from their master server.

Totally agree with this. It's just strange that it happens randomly for a handful of users.