Debugging Minecraft client 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

Client side debugging

This article describes monitoring outgoing connections to a remote Minecraft server over a remoteit connection.  To debug the server side, please see: Debugging Minecraft server connections on Windows.

On the client side, you need to make sure that:

  • Any remoteit Service connecting to a local Minecraft Server should be disabled temporarily.
  • Make sure that only the Connection to the target Minecraft Server is active.

Disable any local Minecraft Service

On the Devices tab, select the local Device to show the locally configured Services.  Make sure that the one connecting to your local Minecraft Server (if any) is "Offline".



Make sure that the Connection to the remote Minecraft Service is active.

In this example, "Connectd-device-225" is the remote PC which is hosting the Minecraft Server.


Confirm that no other connections are active

Select the Connections tab.


If any Connections besides the intended one to the remote Minecraft Server are "Connected" (they show a blue "Disconnect" button), then click on "Disconnect" and wait until the button turns green again.




Run the debugMinecraft.ps1 script

At the Administrator Command Prompt, run Powershell.



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

Run debugMinecraft.ps1.



Sample output is shown below.

PS C:\ProgramData\remoteit> .\debugMinecraft.ps1
Client connection found.
Minecraft Client Service UID is: 80:00:00:00:01:09:5D:E3
∘ MODIFY in progress ...
✓ Disabling connection
✓ NEXT-ACTION: run 'sudo remoteit status' for status
connectd.exe -s -mfg 33280 -ptf 5 -p ZmF1bHRsaW5lMTk4OUB5YWhvby5jb20= 5F6F76FBC8DA34E92C11667F2088E64B59392CF4 80:00:00:00:01:09:5D:E3 T33002 2 35 0 0
Connectd built Dec 3 2020 at 20:59:16 Now Starting Up
Version 4.10.1607057839 - (c)2020, Inc. All Rights Reserved
MIGWIN64 Version
restrict address =
setting web config port to dest_server_port 80
primary local ip =
Using server on port 5959
Using device uid = 00:00:00:00:00:00:00:00
Using Server Channel Port 5980
User connecting to 80:00:00:00:00:00:5d:e3
primary local ip =
local IP address found
initialize TCP target port 80
generate our own UID= f3:0d:69:49:6b:60:15:c1
NAT PMP router found
Used NATPMP to map port 33002
Attach to Service...
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 33002
05016> req auth to id

05016> sending req auth to

05016> Status redirect to

05016> req auth to id

05016> sending req auth to

05017> NAT type selected at 3 with natmap 2

!!status - server connection changed to state 4 - time 2 <05017>
!!status - Connected to server is
!!status - server connection changed to state 5 - time 2 <05017>
!!status - Connected to server is
!!request to connect from ID or device owned by <05018>
!!status peer connectd version is 4.10
!!status Peer Session max packet upsized to 1258
!!status peer connectd version is 4.10
!!status Peer Session max packet upsized to 1258
!!connected local=1 to peer ip= at time 5 <05044>
Starting Proxy on TCP port 33002 on index 1.
Proxy started.
!!status 7 seconds since startup lc=29 tc=0
!!throughput txBps=127 rxBps=130 pl=0 it=0
!!status 13 seconds since startup lc=31 tc=0

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

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