Agent cannot connect: Connection Error [000001BC7F24AA48, 5, [-1]]...

[stephannn]

Hi,

maybe someone can help me with this not very specific agent error:

[2025-09-29 11:02:01 AM] [168572E0999089DE] ..\microstack\ILibParsers.c:10994 (0,0) Connecting to: wss://myServer.contoso.com:9888/agent.ashx
[2025-09-29 11:02:01 AM] [168572E0999089DE] ..\microstack\ILibParsers.c:10994 (0,0) Control Channel Disconnected [-1]...
[2025-09-29 11:02:01 AM] [168572E0999089DE] ..\meshcore\agentcore.c:3746 (0,0) Connection Error [000001BC7F24AA48, 5, [-1]]...
[2025-09-29 11:02:01 AM] [168572E0999089DE] ..\microstack\ILibParsers.c:10994 (0,0) PLATFORM_TYPE: 10
[2025-09-29 11:02:01 AM] [168572E0999089DE] ..\microstack\ILibParsers.c:10994 (0,0) Running as Service: 0
[2025-09-29 11:02:01 AM] [168572E0999089DE] ..\meshcore\agentcore.c:4323 (0,0) Attempting to connect to Server...
[2025-09-29 11:02:01 AM] [168572E0999089DE] ..\meshcore\agentcore.c:4326 (0,0) Attempting to connect to Server...

This is the one I get from my client after enabling logging:

controlChannelDebug=1
logUpdate=1

I can do a Test-NetConnection successfully:

Test-NetConnection myServer.contoso.com -port 9888

ComputerName     : myServer.contoso.com
RemoteAddress    : 10.201.2.39
RemotePort       : 9888
InterfaceAlias   : Ethernet0
SourceAddress    : 10.185.181.135
TcpTestSucceeded : True

My Server Config:

"settings": {
    "cert": "myServer.contoso.com",
    "_WANonly": true,
    "_LANonly": true,
    "sessionKey": "DSPIAZusdfPZuV7lN",
    "port": 443,
    "_aliasPort": 443,
	  "agentPort": 888,
    "AgentAliasPort": 9888,
    "AgentPong": 300,
    "agentPortTls": true,
    "_TLSOffload": false,
    "trustedCert": true,
    "SelfUpdate": false,
    "AgentTimeStampServer": false,
    "AllowFraming": "",

I must say, it never worked. Before I was doing some tests locally with podman. Now I moved it to a real server and also requested for the website a certicfiate. The agent itself is still self-signed. The client I am using is still the same and also the port is was using before in my test.

[si458]

so this to me shows thats the remote machine isnt talking to meshcentral and isnt even connecting
so forget security and certificates etc, you have a firewall issue or something blocking access,
just because powershell says its open doesnt mean its actually open it could be blocked upstream somewhere
for example i can do a port scan on my mobile phone using 4G and ALL tcp ports show as OPEN when overdally thats not the case
so first thing to check is the agent runs on port 888 but is telling the world/remote device to connect to it on port 9888
so first of check your firewall isnt blocking port 9888
also check if your port forwarding that port 9888 is forwarded to port 888
second thing so check is mesherrors.txt inside meshcentral-data for any errors
then you need to check the meshcentral start up logs
this varies depending on HOW you set it up, docker, use docker logs
npm, try systemctl status meshcentral.service (if you used --install)
if run manually check the output when you run it manually

[stephannn]

Stupid me, I forgot about the Docker port mapping. Thanks for the hint.

I thought you were going on vacation?

[si458]

6th-13th oct (1st week of october depending on if u define today/2moz as first week of october altho its still septermber haha