fixed Server registration temporarily failed with code 500. Will try again later.

[Amarok_73]

Hello,

We have problem with our dedicated servers. They starting but do not appear in the server browser. The server list in the WebGUI on the DCS web page looks as on the attached screen, and the number in the server name periodically changes. Looking into the log file I can see, there is the three messages that appears continuously:
"2023-07-02 07:27:55.603 INFO    ASYNCNET (Main): Registering HTTP control interface as 77.237.8.35:8089 (port is forwarded by UPNP)
2023-07-02 07:27:55.603 INFO    ASYNCNET (Main): Registering server as 77.237.8.35:10309 (port is assumed to be open)
2023-07-02 07:27:56.195 ERROR   ASYNCNET (Main): Server registration temporarily failed with code 500. Will try again later."
The port numbers are ok, specific for each of the servers.
Local Web GUI works ok, and shows propper servers configuration and it is possible to connect to the servers providing the IP and port.

What can be the reason of this issue?

 

Edited July 2, 2023 by Amarok_73

[goldleader]

I am having the same issue on 2 Instances on the Same Box, People can connect to SRS but DCS Server is not showing in the Master Server List

[Jakko]

I've had this problem for several hours.

[Amarok_73]

@Wags@Flappie @BIGNEWYGentlemen, is it anything You can confirm that is on the ED side?

Edited July 2, 2023 by Amarok_73

[HC_Official]

ED's master server is falling over more often than a one legged man in an bottom kicking contest lately sadly

[Flappie]

Hi. Some well known servers are missing from the list, indeed. 4YA servers are absent, for instance.

Please first try to fix the issue on your side. Since error 500 is often caused by a difference in time between DCS auth servers and DCS clients/servers, you must ensure your server is synchronised, set to summer time, and with the correct time zone.

Also, please attach your server's log.

[Amarok_73]

@Flappie I did as You told, check the date and time settings, they're correct, so here's the log from one of the serversdcs.log

[Flappie]

Sorry, I may seem to ignore the real problem here, but since I cannot monitor DCS auth servers, I try to understand the problem from the client/dedi server perspective.

[Amarok_73]

7 minutes ago, Flappie said:

Sorry, I may seem to ignore the real problem here

No worries Flappie, I don't think anybody assumes that.

[Maverick87Shaka]

Same problem here, our instances after reboot doesn't appear anymore in the multiplayer server list

[HC_Official]

woo hoo, was pointed out years ago that a system with a single point of failure was  a BAD IDEA ... and yet here we all are

null

[Flappie]

@Amarok_73 I checked your ports and they are reachable.

I'll get in touch with ED tech support right away.

[HC_Official]

23 minutes ago, Flappie said:

Hi. Some well known servers are missing from the list, indeed. 4YA servers are absent, for instance.

Please first try to fix the issue on your side. Since error 500 is often caused by a difference in time between DCS auth servers and DCS clients/servers, you must ensure your server is synchronised, set to summer time, and with the correct time zone.

Also, please attach your server's log.

either literally dozens of peoples server clocks went out of whack all at exactly the same time 

................ or more likely ED master server has crapped itself ............ again

Edited July 2, 2023 by HC_Official

[Sly870]

Same on GS servers. Time and all that in sync

[Maverick87Shaka]

I just made a quick test from a complete new server machine spawned in Azure, with a different account that I use on my usual servers/instances, and I still have the same error.

EDIT:
Just to exclude it was something like a Fail2Ban implemented on ED servers to avoid too many request
EDIT2:
Connect by IP still work as workaround for squadron activity/co-op.

 

Edited July 2, 2023 by Maverick87Shaka

[Amarok_73]

It seems the situation is back under control.

[Flappie]

That's what I'm reading here and there, yes.

[Maverick87Shaka]

I can confirm, all my instances are back online. looks like happens around 08:33 UTC