Jump to content

Dedicated Server - Timeout was Reached


Demiurgo

Recommended Posts

Hi Everyone,

I host a dedicated server that was working fine till last W10 update.

The machine starts and shutoff automatically every day.

 

Since last W10 update DCS doesn't start and gives me "timeout was reached" message. When I close the window (cliking ok in the message) everything works but it takes a lot to log in.

 

I am getting this in the log when it fails:

2021-02-10 16:23:39.614 ERROR   NET: HTTP request dcs:settings failed with error 28: Timeout was reached
2021-02-10 16:24:09.630 ERROR   NET: HTTP request dcs:login failed with error 28: Timeout was reached
2021-02-10 16:24:09.630 INFO    NET: Login server has timed out.
2021-02-10 16:24:09.803 INFO    DCS: Loading cached auth data...
2021-02-10 16:24:09.804 WARNING DCS: Login failed, offline auth is not available.
2021-02-10 16:24:12.680 INFO    DCS: application shutdown
2021-02-10 16:24:13.709 WARNING EDOBJECTS: lTypeObjectManager::Create() doesn't exist.
2021-02-10 16:24:13.717 INFO    TERRAIN: lSystem::exit()
2021-02-10 16:24:13.717 INFO    TERRAIN: lSystem::CleanScenes()

 

After I click "ok" on the message the log is this:

2021-02-10 16:27:49.063 ERROR   NET: HTTP request dcs:settings failed with error 28: Timeout was reached
2021-02-10 16:27:50.200 INFO    NET: Login success.
2021-02-10 16:27:50.931 INFO    NET: Got auth data.
2021-02-10 16:27:51.254 INFO    DCS: Successfully got authorization data.
2021-02-10 16:27:51.260 INFO    Dispatcher: Loading installed modules...

 

I'd appreciate any help with this.

 

Thank you!

Link to comment
Share on other sites

Hi @Demiurgo. HTTP error 28 means your DCS updater can't access the DCS update servers in due time. Most of the time, this issue is caused by antivirus or firewalls. The weird thing is that your clikc somehow fixes the issue.

 

To understand what's happening, you'll need Wireshark. It allows one to detect rejected network packets. Here's a simple guide to install and use it. Once installed, what you have to do is:

  1. Launch Wireshark and start listening to network packets (you'll see strange lines appearing)
  2. Launch DCS
  3. Wait for the error to happen, and then stop Wireshark listening, then save the result as a network dump file. Zip it and attach it here.

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Hi Flappie,

Thank you for answering.

Here is the file (I hope I did it right).

 

Some notes:

1) This is happening to my server machine and to my gaming machine now (both 100% clean W10 machines with almost nothing installed, not even external Antivirus)

2) Only change done before this happens was to install W10 update (2021-02 Cumulative Update (KB4601319) and 2021-02 .NET update (KB4601050). I don't typically touch these machines at all since I only use W10 for DCS

3) If you check the file I am uploading you'll see that contains IPV6 traffic. Just in case, I shut it down (from network adapter menu) but the problem remains.

4) The file added is not from my server but from my gaming PC. Since it's the same error I assume will be fine. If not, please let me know.

 

Please let me know if you see something relevant.

 

Thank you!

 

Traffic IPV6.zip


Edited by Demiurgo
Link to comment
Share on other sites

Perfect! Open the file in Wireshark, then in the "Filter" field above, paste this "(ip.dst == 91.134.1.104) || (ip.src == 91.134.1.104)" and click "Apply". Now, you will only see what went on between your PC and the DCS update/authent server (91.134.1.104).

 

What I see is:

  1. Your PC tries to contact DCS update/authent server (5.9 seconds after you started recording nework packets). Let's call it t0. It uses internal port 49720.
  2. It doesn't seem to get any answer during 19 seconds, after 3 retries (t0+1s, t0+3s, t0+7s). Same internal port 49720.
  3. A new try is made at t0+19s, this time using internal port 49725, and the DCS update/authent server answers at last (SYN, ACK).
  4. Afterwards, the dialog seems OK.

From what you've told previously, I take it you clicked the "OK" button 19 seconds after DCS was launched. Am I right?

 

If you start over, chances are internal ports will change but the result will identical.

 

I'm currently comparing lines number 15 (first failed try) and number 170 (successful try).

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Here is a comparison between the two packets. Only the content (probably because each packet includes time of connection) and the internal port changed (don't mind the stream index information, it's Wireshark's business).

 

Please try again and see if port 49720 keeps being used at first try. If so, i could be an issue with a blocked port. But internal ports are supposed to be selected randomly,so I don't think it's something of the sort.

 

packets.png

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Flappie, excellent data, thanks!

I've tried some more and here is what I've found:

1) Ports are not so random, 49720 appeared again

2) So far, other ports are working, but 49720 is not

3) i don't have any ports forwarded except 10308 and 5002 for DCS/SRS

4) I could try to forward 49270 and check stability

5) If that's the case, do you have a list of ports so I can forward them all or something like that?

 

thanks!

Link to comment
Share on other sites

When a PC is connecting as a client to a distant server (this is the case here, your DCS is client of the DCS update/authent server), the internal port is randomly chosen most of the time. In Windows, random ports are supposed to range from 49152 to 65535 by default (source).

 

Is port 49720 systematically used during first try? That would be weird... Mine is never the same.

If you're certain the issue comes from port 49720, you can launch this command so Windows don't use it as a random port anymore:

 

netsh int ipv4 set dynamicport tcp start=49721 num=16814

 

It modifies the random ports range to 49721-65535.


Edited by Flappie

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

I know it sounds weird bit I had Wireshark in front of me when the same port appeared. In any case I've noticed that some other ports are failing but some other not.

 

On the other hand I've used some Outgoing Port Testers for those ports and they seem to work so it seems is not my ISP.

 

I wonder if I am the only one with this issue.

 

 

Link to comment
Share on other sites

I understand you only have Windows Defender as an antivirus. Please add these folders as exceptions. Even if it doesn't solve your issue, it's a good thing to do.

  • C:\Users\username\Saved Games\DCS...
  • \DCS World OpenBeta server\

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...