[REOPENED] "Host" option hangs on "Trying Steam connection..."

[Nissy64]

UPDATE 2
After a brief test run of the server and a meal, the server no longer functions, coming to the same "Trying Steam connection..." hang as before. I logged into the router and tried two different methods for forwarding all of the mentioned ports (and then some), and finally DMZ mode for my PC.

While ProjectZomboidServer.BAT no longer prints a message regarding the old port mappings, it now says that no port mappings are present, and then declares that it was successfully able to set them up. The logs present in \Users\user\Zomboid\Logs.zip are presenting with the same issues previously described.

UPDATE [OUTDATED]
After reviewing some other log information from ProjectZomboidServer.BAT, I did a factory reset on my router [due to lost login information] and the server started up immediately.


ORIGINAL POST
I've been running a vanilla PZ multiplayer server for myself and my partner with whom I live. We've been playing for a few days now without issue, but after looking at the patch notes, I believe it was today's update that broke my game.

When starting the server up through the "Host" option, as the title says, it'll hang indefinitely on "Trying Steam conenction..."

I've tried a few of your standard troubleshooting steps, such as

• [backing up and] wiping the server settings and save [under \Users\Zomboid\];
  
• using "ipconfig /renew"; and
  
• restarting my PC.

Looking through the server settings, UPnP is enabled, and the new ports mentioned are populated with their default values.

Searching Google for "project zomboid "trying steam connection"" yields 0 results, so here I am. Does anyone have any ideas?

[Beard]

Can you share your logs.zip file found in C:\Users\YourUserName\Zomboid?
You can use any file sharing website of your choice or a temporary one like tmpsend.com for example.

[Nissy64]

Originally posted by Beard:

Can you share your logs.zip file found in C:\Users\YourUserName\Zomboid?
You can use any file sharing website of your choice or a temporary one like tmpsend.com for example.

https://tmpsend.com/DftAxhN5

[Nissy64]

[NB: I additionally attempted to verify the game's files via Steam, which yielded 0 failed validations.]

I dipped my nose in myself since I was bored and curious, and found some interesting errors:

https://hastebin.com/esubesaduj.yaml

The initial UDP connection attempt uses the public IP, and throws a short error:

[...] > ZNet: CRakNet -> CZombienet: OnFailedConnectionAttempt.
[...] > ZNet: OnFailedConnectionAttempt: reason=ConnectionAttemptFailed.
[...] > ZNet: CZombienet -> CZombienet: DoNextConnect. 

Then it tries to UDP connect to localhost [127.0.0.1]:

[...] > ConnectionManager: [RakNet] "connection-attempt-failed" connection: null.
[...] > ConnectionManager: [disconnect] "17" connection: null.
[...] > ZNet: CRakNet -> CZombienet: OnFailedConnectionAttempt.
[...] > ZNet: OnFailedConnectionAttempt: reason=AlreadyConnected.

And then a Steam connection to the public IP:

[...]  UdpEngine.threadRun> Exception thrown java.nio.BufferUnderflowException at Buffer.nextGetIndex. Message: Exception thrown during decode..
[...]  DebugLogStream.printException> Stack trace:.

And then finally, there's a unique error in all of this:

 ERROR: Missing translation "UI_servers_". 

I'm not sure how much all of this really helps, but it was still a personally-intriguing dive into the logs, something I don't do enough of. Thanks in advance for providing a fantastic game and the support required to go with such an ambitious, impressive piece of software.

[Nissy64]

Bump to reiterate continuation of problem.

[Nissy64]

Originally posted by EnigmaGrey:

Looks like you've disabled UPnP. If your router supports UPnP, you could turn it back on. If not, you'd have to manually portforward ports 16261, 16262, and 8766 manually.

Double check that they're forwarded to the correct address. Though note that some ISPs covertly block a large variety of ports and don't let you forward them, even if their techs or the UI for their router suggests they've been opened. It's an annoying problem. Likewise, since we've added a new port, it's possible router security software, your firewall, or antivirus may block connections because "something" changed.

I'd also recommend turning off the mods until the issue can be resolved, as all it takes is one bad function to break something severely enough that you can't connect.

https://cdn.discordapp.com/attachments/144185451362648064/1027319296579338310/unknown.png

UPnP is, and has always been, enabled on my router. I'll concede that 8766 is different from one of the ports I had opened, but the other two were, and none of this was an issue until the update to the ports was pushed.

On the same network, my partner was able to successfully start a server while I was not able to. And this is with ports being forwarded to my client and not his.

At this point, I've gone full scorched-earth and did a full reset of Windows, but none of your proposed solutions make any sense in the light of what I've already tried, and even what was possible before.

[Nissy64]

Originally posted by EnigmaGrey:

snip

Additionally, I disabled Windows Firewall and had no third-party antivirus running. As far as router security goes, I had already done a full factory reset of the router, which allowed my server to run exactly once and never again.

[Nissy64]

Originally posted by EnigmaGrey:

snip

After a full reset of Windows, not only is the server failing with the same errors in the log, I no longer can do a standard launch of Zomboid. Additionally, no Workshop mods have been installed since the reset, so mods are no longer a confounding factor.

[Nissy64]

FURTHER ISSUES
Now the game is hanging on "Getting server info..." when starting a server with default "servertest" settings. Both of the processes that invoke Windows Firewall's exception allowance window were given both Public and Private Network access.

https://hastebin.com/zohefarolu.yaml

Excerpt from console.txt immediately after closing the game.

[Nissy64]

https://tmpsend.com/545I5gUx
(Note: I joined my partner's local server, a solution we've resorted to due to my server no longer being operational and losing our save in the process of troubleshooting. Any successful connection shown would be to his server.)

https://cdn.discordapp.com/attachments/629981899418238987/1027026891766509708/unknown.png

The ProjectZomboidServer.BAT, when started independently, will print messages regarding mapping for the UPnP ports. The console no longer prints messages about ports being already present and alive for any amount of time, but instead that they're missing entirely, and that it was successful in setting up the mapping like it does here. Attempting to run the server via "Host" doesn't work after this, and it will print every time it's started.

I also mentioned that I attempted to run the server with the default "servertest" settings, which does have UPnP enabled. Since I just reinstalled Windows, I have no third-party antivirus running; Windows Defender is likely active, but my partner has both third-party antivirus and Windows Defender running. I've also previously mentioned disabled Windows Firewall entirely, which had no effect on any of the outputs.

[Nissy64]

I apologize for attempting to fix the error on my own, I was getting impatient because I wanted to make sure I would be able to play the game with my partner after they got off work; I'd seen others receiving replies for issues such as with Gportal, so I took the initiative and followed the chain upward in my own search for the culprit with what I believe to be the standard troubleshooting procedure. I was also under the impression that the more information that can be provided to support, especially when it's a consistently reoccurring, reproducible issue, the better.

Running the .BAT was to get another view of the issue, which it did provide: The console is printing that the functions for UPnP executed successfully. Nothing about the issue made sense, and with the server having worked once after the router factory reset, I thought that it *was* simply just some bug with the router with the change to the port mapping.

But then the issue returned after just the one test run. He had never tried running a server before I asked him to in the troubleshooting procedure. Something I forgot to mention is that when I connect to him via Steam Friends, it tells me that port 16262 is closed. Performance is seemingly unaffected after a few hours of gameplay. The possible existing rule in place might be my manual attempts at forwarding the ports to my client; I tried deleting and reapplying the port forwards (following your guidelines). My PC has the same internal IP as it did before the router reset.

log_4 occurred with the manual port forwarding having been deleted and reapplied;
log_3 occurred with the manual forwarding removed, with Windows Firewall active;
and log_2 and log_1 are both with the manual forwarding removed and Windows Firewall entirely disabled:
https://tmpsend.com/tT5Hax2a

[Nissy64]

I forgot to add:
log_4 presented me with a hang at "Getting server info..."
log_1-3 presented me with the original "Trying Steam connection..."

[Nissy64]

My understanding of troubleshooting procedure is that resetting and revalidating the settings of points of failure further up the pipe is how you identify where an issue lies. And reiterating the consistently reoccurring, reproducible nature of the issue, such investigation would occur naturally.

[Nissy64]

Originally posted by EnigmaGrey:

You really should have just followed a guide if you wanted a dedicated server:

And, with all due respect, you can stow the condescension. I had it working before the update. No guide would be able to account for an issue like this. I really am in disbelief at your nerve.

[The Machine (It/That)]

I'm currently having the same issue. Was hosting 2 nights ago. Nothing has changed.

[The Machine (It/That)]

Originally posted by Heckin' Nis C:

Originally posted by EnigmaGrey:

You really should have just followed a guide if you wanted a dedicated server:

And, with all due respect, you can stow the condescension. I had it working before the update. No guide would be able to account for an issue like this. I really am in disbelief at your nerve.