In T192327#2816742, @Geez wrote:

Hello priglmeier.
Please make sure to send the report when the crash pops up so our team has all the info directly in the crash stash.
Thank you.

AGAIN, this is not a port forwarding issue @Geez
Port 2001 is set and port forwarded.

Port 2001 UDP has been open and port forwarded since the Reforger Server was installed.
You are looking at old logs where my ISP changed my IP.

@Geez please provide a fix for this. Many others are reporting the same issue on various other forums.

Yes, I tried that. IT seems to work for a while longer, but then has the same issue/bug.

We need a fix for this bug.
I have a game and a dedicated server that is unusable due to this issue.

Any updates?

I re-ran the same client connection test. Same error on the client around Tue, Nov 19, 12:30-40 PM
New server logs attached with Normal logging.
Then I stopped the server afterwards.

Which log level do you recommend then? Normal?

Alright. My bad. I will attach the server logs

Server logs attached

Current client logs, 7-zipped.

Client side logs show the same error and not much else for the above 2 examples:

Client connection test 2 - Try a direct connection

OK. I think there has been some more confusion here, but I will clarify. :)

This is only partially correct.

Alright. The issue remains the same though. In both configurations either the WAN or LAN clients con't connect as expected.
Let's focus on Example 1 since you reported this should work properly.

@Geez This issue is NOT caused by "A server ping exceeding 999 milliseconds when hosting a LAN is a normal occurrence. This is because the server is not accessible from the internet and we cannot accurately assess ping times using private IP addresses."

FYI
I can work with you on any configuration changes on the server or network that you may need to test OR to create additional logging info, etc.