Unable To Reach Server

[jpcapone]

Describe the Bug A clear and concise description of what the bug is.

Your Runtime Command or Docker Compose File

version: '3'
services:
    satisfactory-server:
        container_name: 'satisfactory-server'
        hostname: 'satisfactory-server'
        image: 'wolveix/satisfactory-server:latest'
        ports:
            - '7777:7777/udp'
            - '15000:15000/udp'
            - '15777:15777/udp'
        volumes:
            - '/var/lib/docker/volumes/satisfactory/config:/config'
        environment:
            - MAXPLAYERS=4
            - PGID=1000
            - PUID=1000
            - ROOTLESS=false
            - STEAMBETA=false
        restart: unless-stopped
        deploy:
          resources:
            limits:
              memory: 6G
            reservations:
              memory: 4G

System Specs (please complete the following information): If you're on Linux, just paste the following block as a single command, and paste the output here.

===== START ISSUE REPORT =====
OS:  Linux craftmines 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun  7 15:25:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
CPU: QEMU Virtual CPU version 2.5+
BIOS pc-i440fx-7.2  CPU @ 2.0GHz
RAM: 18GB/24GB
HDD: 97GB/192GB (54% used)
===== END ISSUE REPORT =====

Additional Context I want to point out that i am using 15777 as the port as its the default port listed. The server indicates that its listening on port 777 but when i use it: I dont get the option to create game.

the logs below are from a fresh docker deployment and the first connection to it.

https://pastebin.ai/8f0cfjidz5

I am using the latest client version from Steam. Also, I do not have any port forwarding on the firewall as i am assuming its not necessary for an internal connection?

Any suggestions would be appreciated!!!

[wolveix]

Hello! 15777 is the correct port to use. I can't see the logs you sent, as it results in a 403 error. Please upload your logs directly to GitHub.

Additionally, this could be due to your CPU model. I can see that you're using QEMU; Satisfactory doesn't play nice with known-virtualized CPU identifiers. Pass it through as a non-generic CPU, and it may fix your issue.

[jpcapone]

Wow, changing the CPU mode in TrueNAS did the trick, thanks!!! Also, the character limit inhibited me from loading the logs directly to GitHub - FYI....

[wolveix]

Hah, yeah it's a surprising issue! There is a check in the container to look for generic virtualized CPU names, but yours is different to the one we check for.

For logs, I meant physically uploading the log file, not copy and pasting it into the issue :) Glad the issue is sorted nonetheless!

[jpcapone]

For logs, I meant physically uploading the log file, not copy and pasting it into the issue :) Glad the issue is sorted nonetheless! Oh cool! I didn't know that was an option. I am sure I'll have another issue where that will come in handy! Thanks for you help and thanks for sharing!