Czar66 Posted June 22 Posted June 22 14 minutes ago, Rudel_chw said: Maybe that's why I've never had this issue ... I have the launcher disabled (personal preference) : ...but...but those cool clips, tho. I understand the preference, but the quick graphics setting changes without booting up DCS has been handy in a little while. 1
Rudel_chw Posted June 22 Posted June 22 2 minutes ago, Czar66 said: I understand the preference, but the quick graphics setting changes without booting up DCS has been handy in a little while. hopefully all the additional clues that this thread provides should help ED to pinpoint the problem. 1 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
ex81 Posted June 22 Posted June 22 56 minutes ago, Rudel_chw said: Maybe that's why I've never had this issue ... I have the launcher disabled (personal preference) : Same for me. Never did like the launcher. So I disabled it and never had your problems. Maybe disabeling it and your problem will disappear. What goes up, must come down ! Intel Core i7-8700, 32 GB-RAM, Nvidia GTX 1060, 6 GB GDDR5, 1TB HDD, 1000 GB 970 EVO Plus NVMe M.2 SSD, Windows 10/64, A10-C, VKB Gunfighter IV Ultimate, Persian Golf, F/A-18 Hornet, Tankkiller
Czar66 Posted June 22 Posted June 22 (edited) 7 minutes ago, ex81 said: Same for me. Never did like the launcher. So I disabled it and never had your problems. Maybe disabeling it and your problem will disappear. The problem disappeared after a log out and log in refresh. No need to ditch the launcher from my end. Edited June 22 by Czar66 1
Actium Posted June 22 Posted June 22 3 hours ago, Czar66 said: This fixed my issue. No more 502... so far. The error numbers are HTTP status codes. Error 502 (Bad Gateway) is a server-side error that indicates an issue within ED's network and should be entirely unrelated to your client or your internet connection. 3 hours ago, Rudel_chw said: Maybe that's why I've never had this issue ... I have the launcher disabled (personal preference) I have the launcher disabled and can still trigger the issue. The error is unrelated to the launcher. It also affects the dedicated server, which doesn't include the launcher. 2 hours ago, Rudel_chw said: opefully all the additional clues that this thread provides should help ED to pinpoint the problem. ED are aware. The issue has been reported to the devs, but so far hasn't been addressed. 1
Czar66 Posted June 22 Posted June 22 1 hour ago, Actium said: The error numbers are HTTP status codes. Error 502 (Bad Gateway) is a server-side error that indicates an issue within ED's network and should be entirely unrelated to your client or your internet connection. This is beyond my knowledge, but through several times before resetting the log in through login out I had a 100% rate of receiving the error. Upon logging out and back in, the error went away and I could finish 2 missions later. Their side or not, DCS came back working again.
rob10 Posted June 23 Posted June 23 People, the 502 error today was COMPLETELY unrelated to the issue that this thread is originally discussing. It was a temporary issue that ED fixed. Turning off the launcher didn't fix it, it was a coincidence that ED fixed the issue and it came back up before you tried again. 2
Roughneck Posted June 23 Posted June 23 17 hours ago, Czar66 said: The problem disappeared after a log out and log in refresh. No need to ditch the launcher from my end. I tried this a couple of weeks ago. It worked for a while but then the issue started up again. Maybe do it every time you start up DCS? System: Ryzen 5900X, Asus ROG Dark Hero MB, EVGA 3080 FTW, 64mb DDR4 3600hz Controllers: Winwing Super Libra, Taurus, TO and Combat Panels, MFG Crosswind Pedals Played: Falcon Allied Force, Falcon 4.0, Aces High, all the MS Combat Flight Simulators, Fleet Defender, F15 Strike Eagle (Commodore 64)
Czar66 Posted June 23 Posted June 23 (edited) On 6/23/2025 at 11:20 AM, Roughneck said: I tried this a couple of weeks ago. It worked for a while but then the issue started up again. Maybe do it every time you start up DCS? Just checked. DCS is working fine again without the error on boot while auto login is active. Likely without the Authorization Expired error as well after a while in game. Edit: soon I'll fly again and update this post if the Authorization Expired error doesn't appear in a full dcs session of mine. Edit 2: The error "login expired" and the "Error 502" has not appeared ever since. Edited yesterday at 04:46 PM by Czar66 1
YoYo Posted June 24 Posted June 24 (edited) Today I recived Login Session Expired as well. Ups. Edited June 24 by YoYo 1 Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
tempusmurphy Posted June 27 Posted June 27 (edited) I have just had a couple of instances of this over the past couple of weeks, zero changes to PC or internet service providers, at my end nothing new apart from the last couple of patches to DCS. the last one happened about 12-13 minutes in, just plonked a corsair on the ww2 marianas map and was loading some weapons in the mission editor and sudden freeze and Login expired Edited June 27 by tempusmurphy more info
Actium Posted June 29 Posted June 29 On 6/27/2025 at 9:28 PM, tempusmurphy said: the last one happened about 12-13 minutes in Mind sharing one or more dcs.log file(s) of the expired sessions? Unfortunately, the error popup message is identical for a couple of different causes. If it happened that early after starting the game, I wonder what exactly occurred.
Hempstead Posted Thursday at 07:19 PM Posted Thursday at 07:19 PM It has been giving that "Login Session Expired" and kicking me out recently ever since the new launcher was deployed. Sure, restart will get me a login again. But... Today, it kicked me out when I was actively bombing some T-72s. Hey! WTF!!! I just got in less than 10 minutes ago! That's not a nice end-user experience! Shouldn't it renew my session authentication when I got into the launcher thing? Apparently not! How do you like to get kicked out while in a multi-player mano a mano dog fights? I am sure the other guy will not accept "the excuse" of getting kicked out! That's a potentially ego-dousing bug! Please fix it. 2
Actium Posted Friday at 04:34 AM Posted Friday at 04:34 AM 9 hours ago, Hempstead said: Today, it kicked me out when I was actively bombing some T-72s. Hey! WTF!!! I just got in less than 10 minutes ago! Would you mind sharing a dcs.log for that session? If it kicked you out within 10 minutes of starting the game, there must be more ways this issue is caused than I described here. I doubt you started a second DCS instance while busy bombing those T-72s.
Hempstead Posted Friday at 01:55 PM Posted Friday at 01:55 PM 8 hours ago, Actium said: Would you mind sharing a dcs.log for that session? If it kicked you out within 10 minutes of starting the game, there must be more ways this issue is caused than I described here. I doubt you started a second DCS instance while busy bombing those T-72s. dcs.log
Hempstead Posted Friday at 02:17 PM Posted Friday at 02:17 PM (edited) dcs.log.oldThat was the wrong log file... This is the correct one that it kicked me out. 2025-07-03 19:00:30.957 ERROR ASYNCNET (34508): The session has expired (401). Exiting... Edited Friday at 02:18 PM by Hempstead 2
Actium Posted yesterday at 04:43 PM Posted yesterday at 04:43 PM (edited) @Hempstead Thanks for sharing. I've had a look. These are all occurrences of ASYNCNET within the log file: 2025-07-03 18:48:27.090 INFO ASYNCNET (34508): Login success. 2025-07-03 18:48:29.799 INFO ASYNCNET (34508): Got auth data. 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): ProtocolVersion: 404 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): Adding LAN search interface 0: 127.0.0.1 "IPv4 Loopback" 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): Adding LAN search interface 0: 255.255.255.255 "IPv4 Broadcast" 2025-07-03 19:00:30.957 ERROR ASYNCNET (34508): The session has expired (401). Exiting... So far, I've only observed and been able to reproduce this issue when the client reconnects to the master server after a 30ish minute connection interruption as I've reported here. That would result in many more ASYNCNET error/warning messages like this: 0000-00-00 00:00:00.000 ERROR ASYNCNET (192): HTTP request dcs:checksession failed with error 7: Could not connect to server 0000-00-00 00:00:00.000 WARNING ASYNCNET (192): Session check failed: -7 However, your occurrence of this issue appears to have happened entirely out of the blue without any prior connection issues. Presumably, the master server decided to just expire your session. Based on a previous post from BN, I've had a hunch that changing your IP address while logged in may cause the master server to terminate your session: On 6/5/2025 at 5:24 PM, BIGNEWY said: 401 session expired could be many things, frequent IP changes during a session, account logged into on another device, security / firewall blocking DCS and its connection to the master server I've tried to reproduce this, but changing my public IP address (have the router reconnect) twice for 3 consecutive session checks from 3 different IPs didn't trigger the issue for me. Unfortunately, the master server does not give any reason why it expires your session. Is there anything else on your side that could have caused it? It'd probably be best to open a support ticket, hoping that ED have a server-side master server log with more debug information. Edited yesterday at 04:44 PM by Actium 2
Roughneck Posted 23 hours ago Posted 23 hours ago 6 hours ago, Actium said: @Hempstead Thanks for sharing. I've had a look. These are all occurrences of ASYNCNET within the log file: 2025-07-03 18:48:27.090 INFO ASYNCNET (34508): Login success. 2025-07-03 18:48:29.799 INFO ASYNCNET (34508): Got auth data. 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): ProtocolVersion: 404 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): Adding LAN search interface 0: 127.0.0.1 "IPv4 Loopback" 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): Adding LAN search interface 0: 255.255.255.255 "IPv4 Broadcast" 2025-07-03 19:00:30.957 ERROR ASYNCNET (34508): The session has expired (401). Exiting... So far, I've only observed and been able to reproduce this issue when the client reconnects to the master server after a 30ish minute connection interruption as I've reported here. That would result in many more ASYNCNET error/warning messages like this: 0000-00-00 00:00:00.000 ERROR ASYNCNET (192): HTTP request dcs:checksession failed with error 7: Could not connect to server 0000-00-00 00:00:00.000 WARNING ASYNCNET (192): Session check failed: -7 However, your occurrence of this issue appears to have happened entirely out of the blue without any prior connection issues. Presumably, the master server decided to just expire your session. Based on a previous post from BN, I've had a hunch that changing your IP address while logged in may cause the master server to terminate your session: I've tried to reproduce this, but changing my public IP address (have the router reconnect) twice for 3 consecutive session checks from 3 different IPs didn't trigger the issue for me. Unfortunately, the master server does not give any reason why it expires your session. Is there anything else on your side that could have caused it? It'd probably be best to open a support ticket, hoping that ED have a server-side master server log with more debug information. I've been having this issue off and on for a couple of months now. No chances to my system, and my internet is rock solid. I know BN said it had to be on my end, but I feel like too many of us are having this issue and it started recently for most of us. 1 System: Ryzen 5900X, Asus ROG Dark Hero MB, EVGA 3080 FTW, 64mb DDR4 3600hz Controllers: Winwing Super Libra, Taurus, TO and Combat Panels, MFG Crosswind Pedals Played: Falcon Allied Force, Falcon 4.0, Aces High, all the MS Combat Flight Simulators, Fleet Defender, F15 Strike Eagle (Commodore 64)
Actium Posted 11 hours ago Posted 11 hours ago @Roughneck Have you had a look at your dcs.log for sessions that got terminated? Here's a quick way to grep the relevant ASYNCNET messages from dcs.log via PowerShell: Get-Content "$env:USERPROFILE\Saved Games\DCS.openbeta\Logs\dcs.log" | Select-String ASYNCNET Wondering whether it includes any session check errors/warnings or the The session has expired (401). Exiting... message comes entirely out of the blue. 1
Hempstead Posted 8 hours ago Posted 8 hours ago 22 hours ago, Actium said: @Hempstead Thanks for sharing. I've had a look. These are all occurrences of ASYNCNET within the log file: 2025-07-03 18:48:27.090 INFO ASYNCNET (34508): Login success. 2025-07-03 18:48:29.799 INFO ASYNCNET (34508): Got auth data. 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): ProtocolVersion: 404 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): Adding LAN search interface 0: 127.0.0.1 "IPv4 Loopback" 2025-07-03 18:48:29.854 INFO ASYNCNET (Main): Adding LAN search interface 0: 255.255.255.255 "IPv4 Broadcast" 2025-07-03 19:00:30.957 ERROR ASYNCNET (34508): The session has expired (401). Exiting... So far, I've only observed and been able to reproduce this issue when the client reconnects to the master server after a 30ish minute connection interruption as I've reported here. That would result in many more ASYNCNET error/warning messages like this: 0000-00-00 00:00:00.000 ERROR ASYNCNET (192): HTTP request dcs:checksession failed with error 7: Could not connect to server 0000-00-00 00:00:00.000 WARNING ASYNCNET (192): Session check failed: -7 However, your occurrence of this issue appears to have happened entirely out of the blue without any prior connection issues. Presumably, the master server decided to just expire your session. Based on a previous post from BN, I've had a hunch that changing your IP address while logged in may cause the master server to terminate your session: I've tried to reproduce this, but changing my public IP address (have the router reconnect) twice for 3 consecutive session checks from 3 different IPs didn't trigger the issue for me. Unfortunately, the master server does not give any reason why it expires your session. Is there anything else on your side that could have caused it? It'd probably be best to open a support ticket, hoping that ED have a server-side master server log with more debug information. I have a static IP# assigned to my GamingPC2. And, my egress point IP# is also a static IP# (I pay quite a bit money for it monthly). So, no, there is no IP# change. And this has happened quite a bit before, like when I was in the mission editor, or browsing through my custom mission trying to decide which mission to play, or in Setting pages configuring my settings. It just kicked me out, claiming login expired. The only thing I can think of is DNS server glitch. Say, it tries to contact digitalcombatsimulator.com/.... to validate, but the DNS name could not be resolved for whatever reason... But that is very unlikely too, because once I got kicked out, login in a few seconds works fine means that is not likely to be the cause. 1
Actium Posted 5 hours ago Posted 5 hours ago 2 hours ago, Hempstead said: The only thing I can think of is DNS server glitch. Failure to resolve api.digitalcombatsimulator.com will be logged as ASYNCNET errors/warnings in dcs.log (likely sth. to the tune of error 6: Could not resolve hostname). If your dcs.log does not contain such messages, it's definitely not DNS.
Recommended Posts