Debugging Minecraft server connections on Windows

The attached Powershell script debugMinecraft.ps1 will let you debug connections made on Windows PCs.  It will run the connectd.exe daemon in console mode, which shows you all of the debugging output.

In order to use this script, you'll need to open an Administrator Command Prompt.  Once there, navigate to the folder where you downloaded the debugMinecraft.ps1 script, e.g.

cd \users\you\Downloads

 

Server side debugging

This article describes monitoring incoming connections to your Minecraft server over a remoteit Connection.  To debug the client side, please see: Debugging Minecraft client connections on Windows.

Turn off all remoteit Connections

If you wish to debug the server side (incoming) connection, then make sure that you turn off any active Connections to other devices.

Using the remoteit Desktop application

Open the Desktop application and go to the "Connections" tab.

mceclip3.png

 

Click on all blue "Disconnect" buttons and wait until all Connect buttons are green.

 

mceclip0.png

 

mceclip1.png

 

Using the remoteit CLI

Run the following command to check the current state of your Connections. 

remoteit status

mceclip0.png

If any of them show "connected" in the Status column, then run the following command for those UIDs.

remoteit connection modify --uid <UID> --enable false --retry false

 For example,

C:\ProgramData\remoteit>remoteit connection modify --id 80:00:00:00:00:00:00:00 --enable false --retry false
∘ MODIFY in progress ...
✓ Disabling connection
✓ NEXT-ACTION: run 'sudo remoteit status' for status

C:\ProgramData\remoteit>

Confirm that no Connections are active using the remoteit CLI as shown below.  The "Status" column should indicate "Offline" for all Connections.

remoteit status

 

mceclip2.png

 

Confirm that the remoteit Service for Minecraft Server is running

Make sure that your Minecraft Server remoteit Service is active.

Using the remoteit Desktop application

In the Desktop app, select the "Devices" tab and then click on your PC's Device Name.

mceclip4.png

In this case, the Minecraft Server was turned off.  Click on the Service name to edit the setting. 

 

mceclip5.png

 

Make sure that "Service Disabled" is not selected.

 

mceclip6.png

 

Using the remoteit CLI

Run the following command to check the current state of your Services. 

remoteit status

mceclip1.png

If you Minecraft Service is offline, then run the following command using its UID.

remoteit modify --uid <UID> --enable true --type 41

 For example,

C:\ProgramData\remoteit>remoteit modify --id 80:00:00:00:01:09:44:8D --enable true --type 41
∘ MODIFY in progress ...
✓ Changing service '80:00:00:00:01:09:44:8D' ENABLE flag to 'true'
✓ Changing service type '41' to '41'
✓ NEXT-ACTION: run 'sudo remoteit status' for status

C:\ProgramData\remoteit>

Confirm that the Status of your Minecraft Service is "connected" as shown below.

remoteit status

mceclip2.png

 

 

Run the debugMinecraft.ps1 script

At the Administrator Command Prompt, run Powershell.

powershell

 

C:\ProgramData\remoteit>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\ProgramData\remoteit>

Run debugMinecraft.ps1.

.\debugMinecraft.ps1

 

Sample output is shown below.

PS C:\ProgramData\remoteit> .\debugMinecraft.ps1
Server connection found.
Minecraft Server Service UID is: 80:00:00:00:01:09:44:8D
∘ MODIFY in progress ...
✓ Changing service '80:00:00:00:01:09:44:8D' ENABLE flag to 'false'
✓ Changing service type '41' to '41'
✓ NEXT-ACTION: run 'sudo remoteit status' for status
Connectd built Dec 3 2020 at 20:59:16 Now Starting Up
Version 4.10.1607057839 - (c)2020 remot3.it, Inc. All Rights Reserved
Built with NATPMP BCASTER RESOLVE BIGBUF BACKTRACE NATIVE_MALLOC
MIGWIN64 Version
setting web config port to dest_server_port 80
primary local ip = 192.168.1.190
Config Data is not encrypted
Using server on port 5959
Using device uid = 80:00:00:00:01:09:44:8d
Using Server Channel Port 5980
primary local ip = 192.168.1.190
local IP address found 192.168.1.190
Secret Provided (hash de:96)
initialize TCP target 127.0.0.1 port 25565
NAT PMP router found
Used NATPMP to map port 49504
Attach to remot3.it Service...
56024> Remot3it Registration Code Provided (checkhash de:96)

Command Processor now active.
!!status 1 seconds since startup
!!status 1 seconds since startup lc=1 tc=0
!!throughput txBps=0 rxBps=0 pl=0 it=0
!!status - bound to UDP port 49504
56034> sending req auth to 69.64.90.20:5959

56035> Status redirect to 52.42.122.172:5963

56035> sending req auth to 52.42.122.172:5963

56073> sending req auth to 52.42.122.172:5963

56073> NAT type selected at 3 with natmap 2

!!status - server connection changed to state 4 - time 6 <56073>
!!status - Connected to server is 52.42.122.172:5963
!!status - server connection changed to state 5 - time 6 <56073>
!!status - Connected to server is 52.42.122.172:5963
!!status 7 seconds since startup lc=27 tc=0
!!throughput txBps=18 rxBps=18 pl=0 it=0
!!status 13 seconds since startup lc=30 tc=0
!!throughput txBps=0 rxBps=0 pl=0 it=0
!!status 19 seconds since startup lc=30 tc=0
!!throughput txBps=0 rxBps=0 pl=0 it=0
!!status 25 seconds since startup lc=30 tc=0

!!throughput txBps=9 rxBps=4 pl=0 it=0
!!status 31 seconds since startup lc=30 tc=0
!!throughput txBps=0 rxBps=0 pl=0 it=0

This will keep running until you hit control-C to stop it.

You will be able to see incoming connections and tunnels as they are created.

Was this article helpful?
0 out of 0 found this helpful