search

stayintarkov / SIT.Docker

https://hub.docker.com/r/stayintarkov/stayintarkov
MIT License
24 stars 23 forks source link

Players not seeing hosted games in lobby. #18

Closed Pr0xyWash0r closed 3 weeks ago

Pr0xyWash0r commented 2 months ago

Which version you have issues with?

Using the prebuilt on Dockerhub

What is this issue is about?

Players unable to see hosted games in lobby

When does this occur?

In lobby

Are you running the Docker as user or root?

root

How do we replicate the issue?

We are using an OVH Debian 10 instance with docker pre-installed with 4GB of RAM.

Expected behavior (i.e. solution)

Players should be able to see hosted games

Other Comments

Ports appear to be open, test-netconnection returns TCPTestSucceeded:True for ports 6969-6971

when players enter lobby the server logs become flooded with the following message:

[Client Request] \coop\server\getAllForLocation Error: incorrect header check Error: incorrect header check at Zlib.zlibOnError [as onerror] (node:zlib:189:17) at processChunkSync (node:zlib:457:12) at zlibBufferSync (node:zlib:178:12) at Object.inflateSync (node:zlib:809:14) at IncomingMessage. (/snapshot/src/servers/http/AkiHttpListener.ts:69:60) at IncomingMessage.emit (node:events:518:28) at endReadableNT (node:internal/streams/readable:1696:12) at processTicksAndRejections (node:internal/process/task_queues:82:21) Error: incorrect header check Error: incorrect header check at Zlib.zlibOnError [as onerror] (node:zlib:189:17) at processChunkSync (node:zlib:457:12) at zlibBufferSync (node:zlib:178:12) at Object.inflateSync (node:zlib:809:14) at IncomingMessage. (/snapshot/src/servers/http/AkiHttpListener.ts:69:60) at IncomingMessage.emit (node:events:518:28) at endReadableNT (node:internal/streams/readable:1696:12) at processTicksAndRejections (node:internal/process/task_queues:82:21)

Snarklz commented 2 months ago

This is interesting. I just came here to post about a similar issue, but we have not had issues with players being unable to see each other. When we get this header error, it makes it so damage recording is turned off. Players can shoot, and be shot. Animations will play, ammo gets expended, but no health is deducted. The code segment you listed under 'other comments' is exactly the same error report I get. We are using the pre-built docker image, and I am running on Ubuntu 20.04 running as a user.

devbence commented 2 months ago

can you verify your port(s) are open? (6969, 6970, 6971) check here: https://portchecker.io/ or with nmap: nmap -p6969-6971 ip.addr.ess

Pr0xyWash0r commented 2 months ago

can you verify your port(s) are open? (6969, 6970, 6971) check here: https://portchecker.io/ or with nmap: nmap -p6969-6971 ip.addr.ess Screenshot 2024-05-25 103103

Snarklz commented 2 months ago

image

devbence commented 2 months ago

and server is.. 1.6.5 with 1.11 client?

Pr0xyWash0r commented 2 months ago

Server is 1.6.5, but the client is 1.10. SIT.Manager does not appear to have an upgrade showing for me to 1.11

kapdon commented 2 months ago

change image: stayintarkov/stayintarkov to image: stayintarkov/stayintarkov:3.8.0.4 which is the last 1.10 build.

enable the dev build setting flag in SIT Manager if you want to use 1.11 pre-release which is stayintarkov/stayintarkov:latest

SystemFiles commented 2 months ago

Can confirm that using the 3.8.0.4 tag solved this issue for me! It was a version mismatch. The latest points to the pre-release 1.11 as stated above