Toumal Posted March 25 Posted March 25 I have the issue that I can start my dedicated server, but after a few hours I get this: 2025-03-07 11:39:40.691 ERROR ASYNCNET (Main): Server registration failed with code 401 This happens 2-3 hours after the server was started. I googled this error and found recommendations to unlink the steam account. I never linked my steam account so that can't be it. I used to be able to host with no issue. I am aware of this thread: but I don't know if these issues are related because I am perfectly able to start my server, it's just that I get kicked out after some time. Is there anything I can/should do?
Actium Posted March 25 Posted March 25 Are you using a separate server account? AFAIK, no more than 3~5 server instances are allowed to run on the same account. The error codes given in the DCS log are HTTP response status codes, with 401 meaning Unauthorized. I'd be curious about the communication with the master server when that error happens. If you'd like to dig into it, you'd have to resort to sth. like sslsplit to intercept the communication between your dedicated server and the ED master server.
HC_Official Posted March 26 Posted March 26 The master server falls over a lot more than it ever should and this is the result No more pre-orders Click here for tutorials for using Virpil Hardware and Software Click here for Virpil Flight equipment dimensions and pictures. .
Toumal Posted March 26 Author Posted March 26 10 hours ago, Actium said: Are you using a separate server account? AFAIK, no more than 3~5 server instances are allowed to run on the same account. The error codes given in the DCS log are HTTP response status codes, with 401 meaning Unauthorized. I'd be curious about the communication with the master server when that error happens. If you'd like to dig into it, you'd have to resort to sth. like sslsplit to intercept the communication between your dedicated server and the ED master server. This is the only server I run, "Caucasus Dynamic Conflict". 14 minutes ago, HC_Official said: The master server falls over a lot more than it ever should and this is the result If that's the case then this must affect everyone, no?
HC_Official Posted March 26 Posted March 26 (edited) when hosting a server your server needs to send a ping to the master server every minute or two IF you server fails to do this, the reasons could be , master server is not working correctly, or for some reason you cannot make a connection to master server then your server stops trying to ping the master server and master server removes your server from the list of MP servers only way to fix this to to stop and restart your DCS dedicated server it is a poor design, dcs dedicated server should keep trying to ping master server and there should be a better grace period before de-listing a server DCS clients do not need to do this, thats why it effects DCS server hosters worse Edited March 26 by HC_Official No more pre-orders Click here for tutorials for using Virpil Hardware and Software Click here for Virpil Flight equipment dimensions and pictures. .
Actium Posted March 29 Posted March 29 @Toumal Short of resorting to sslplit, having a look at the communication with the master server may shed some light on the communication with the master server. I ran the tcpdump for the last couple of days to see whether anything stands out (run as root, adjust eth0 as necessary): tcpdump -ni eth0 "host 185.195.197.4" Already found out the master server took a nap for half an hour shortly after midnight UTC. That resulted in symptoms very similar to what you describe. Maybe worth a shot to run tcpdump and compare its output and the dcs.log to what I posted here. 1
Recommended Posts