Jump to content

Recommended Posts

Posted

00000.155 --- Log file: C:\Users\USERNAME\AppData\Local\Temp\DCS.openbeta\autoupdate_templog.txt
00000.000 === Log opened UTC 2024-09-18 04:01:38
00000.027 INFO : DCS_Updater/2.16.3.18 (Windows NT 10.0.19043; Win64; en-US)
00000.027 INFO : src-id: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
00000.027 INFO : cmdline: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" update
00000.151 STATUS: Initializing...
00000.152 INFO : basedir: C:\Program Files\Eagle Dynamics\DCS World OpenBeta
00000.152 INFO : variant: openbeta
00000.153 INFO : DCS/2.9.7.59263 (x86_64; EN;  WORLD,RAZBAM_AV8BNA,A-10C_2,FA-18C,WWII-ARMOUR,F-5E,POLYCHOPSIM_SA342,RAZBAM_M-2000C,MIG-21BIS,UH-1H,A-10A,SU-25A,F-15C,MIG-29,SU-27,SU-33,KA-50,MARIANAISLANDS_terrain,SYRIA_terrain,PERSIANGULF_terrain,NORMANDY_terrain,NEVADA_terrain,MI-24P,SUPERCARRIER,CA,F-16C,AJS37,DEKA_JF-17,AH-64D,THECHANNEL_terrain,FALKLANDS_terrain,KA-50_3,CAUCASUS_terrain,MOSQUITO-FBMKVI,AERGES_MIRAGE-F1)
00000.153 INFO : branch: openbeta
00000.159 STATUS: Checking for updates...
00130.585 ERROR: www.digitalcombatsimulator.com replied HTTP 502 Bad Gateway
00130.587 STATUS: 502 Bad Gateway
00133.791 === Log closed.

 

Some information is redacted for security and privacy.

Posted
5 hours ago, DmitriKozlowsky said:

00130.585 ERROR: www.digitalcombatsimulator.com replied HTTP 502 Bad Gateway
00130.587 STATUS: 502 Bad Gateway

are you able to restart your network equipment and your computer to get all the DNS flushed and updated? if it still does not work there is either a routing problem somewhere between you and DCS or DCS servers are having an issue.

https://nordvpn.com/blog/502-bad-gateway/

this is for websites but the premise is the same.

  • Server overload. Web servers get overloaded in many different ways. For example, a website may have unusually many visitors or experience a DDoS attack. Then you, as another visitor, can’t access the server and receive the 502 bad gateway message.
  • Backend server issues. Sometimes, the problems are more complicated and are related to the backend configurations of the website. In this case, only the developers can discover what’s wrong and fix the 502 error.
  • Network problems. Some causes are much more straightforward – connectivity issues could be preventing servers from communicating with each other. It can be due to router misconfiguration or something as trivial as a loose physical cable.
  • Security software. Some network problems can be related to security software. A firewall on the gateway server or intrusion detection/prevention systems (IDS/IPS) could suspect malicious activity and interfere with the communication.
  • Configuration errors. If either of the servers has any configuration issues, they fail to communicate, causing a 502 bad gateway error.
  • DNS issues. Misconfigurations sometimes occur in the domain name system (DNS) servers. The gateway server can’t resolve the IP address of the backend server, and your browser shows you the 502 bad gateway error.
  • Temporary glitches. Often, 502 errors occur due to temporary glitches or server hiccups that resolve themselves without intervention.

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

  • Recently Browsing   0 members

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