Troubleshooting

PowerShell Error/Debug
If you are getting a PowerShell error (red text in PowerShell) and the script is continuing not giving you a chance to read the error. You can use the debug setting. It will take any and all PowerShell related errors and write the to a separate ssm-Error-*.log file in the log folder. Some errors are natural due to some SSM checks. although, if you are having a specific issue you can start here. if you haven't got any useful information from SSM or the default SSM log.

wiki

---

Note: Query not working(PS7)

I noticed an intermittent issue with the query command on PowerShell 7. You may need to close the PS7 terminal and re-run the command to show output. This happens with the Portable Version NodeJS and PowerShell 7. Recommend NodeJS 12 LTS system/program installer for PowerShell 7

PowerShell 5 seems to operate better and more consistently.

---

Note: Query not working (PS5) Run ssm query command as a test. if everything seems correct and does not work.
you may try setting $useprivate to 'on' and test again.
# Use private IP for Query and mcrcon
$global:Useprivate = "on"

Check if npm and gamedig can be executed from powershell. If using nodejs system installer. check by just running npm and gamdig from ps. if installed the portable version of nodejs. changed directory in powershell to nodejs folder in ssm and try to dot forward slash npm and gamedig

---

Note: Moving Server Folder

If you need to move the server folder to another location. Check Variables-*.ps1 in server folder. This will contain Vars for Executable location, Log location, and other Variables specifying serverfiles content. Update the Variables Paths with the new location.

---

Server Query or steam Master not working

This server will operate in LAN mode only
If the server displays this error in server console.

Initializing Steam libraries for secure Internet server
*********************************************************
*********************************************************
* Unable to load Steam support library.*
* Unable to load Steam support library.*
* This server will operate in LAN mode only.*
* This server will operate in LAN mode only.*
*********************************************************
*********************************************************

check the root folder of the server and look for these files

steamclient.dll
steamclient64.dll
tier0_s.dll
tier0_s64.dll
vstdlib_s.dll
vstdlib_s64.dll

if you don't see these files, can try to copy them from another steam server.

Also, another note with these dll's. I just found that they also need to be in the same folder as server exe. if the exe is in another folder copy from root to the folder with the server exe. you can use my get-procportbind function to verify the steam query port comes up after that.

---

Finding used Ports on Process/Server

I have a function in core_functions.ps1 name "Get-ProcPortBind". You can find the running process for your server with Get-Process, Find the Process for the server. Then, use Get-ProcProtBind $ProcessName to show Network Ports the process/server is using. It will help troubleshooting in find what ports need to Port Forwarded/Open. Keep in Mind some Traffic is outgoing only and may not need to be allowed incoming.

---