Can't get Satisfactory dedicated server to monitor through Kuma

nafeasonto commented 1 year ago

⚠️ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡️ Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem

I have a Satisfactory dedicated server running on one of my VM's. This program is great, and got many of the monitors to work but for some reason can't do Satisfactory.

It's not under the Gamedig list, but I tried it with steam. My web apikey is in the setting. But I am not sure this is going to work because it's a dedicated server that runs on a host machine, and not the steam servers themselves, or through steam.

Is there some way around this? The game runs on port 15777, which is the query port.

🐻 Uptime-Kuma Version

Version: 1.20.2

💻 Operating System and Arch

Debian 11

🌐 Browser

Chrome

🐋 Docker Version

Latest

🟩 NodeJS Version

No response

401U commented 1 year ago

According to gamedig/node-gamedig#260 and https://questions.satisfactorygame.com/post/61834537831c852052359e9c, Satisfactory have no api for us to monitor now.

nafeasonto commented 1 year ago

I have fixed this.

peterchen19 commented 1 year ago

I have fixed this.

How? same "Problem" here

NicoHag commented 1 year ago

I'd like to know how as well. I've tried pinging the Game Query Port, trying to make it ping the specific docker (with no luck).

CommanderStorm commented 1 year ago

See https://github.com/gamedig/node-gamedig/issues/260#issuecomment-1471434900

louislam / uptime-kuma