Agent error connectex

[iarellano24]

Hi, i have an error with agent when i install it on windows 10.

Server Info (please complete the following information):

• OS: Ubuntu 20.04
• Browser: ALL
• RMM Version (as shown in top left of web UI): 0.11.3

Installation Method:

• [*] Standard
• Docker

Agent Info (please complete the following information):

• Agent version (as shown in the 'Summary' tab of the agent from web UI): None
• Agent OS: [e.g. Win 10 v2004, Server 2012 R2]: WIN 10

Describe the bug
I downloaded the agent from the platform frontend, but I can't install the app on any device. I followed the instructions in the official documentation without making any mistakes in DNS and domains or opening ports.

Screenshots
CMD:

ERROR:

[dinger1986]

Please fill in some information about the issue you are having although most likely this is a support issue so might be better on GitHub discussions or #support on discord

[iarellano24]

Please fill in some information about the issue you are having although most likely this is a support issue so might be better on GitHub discussions or #support on discord

Sorry now is ok.

[dinger1986]

can you try these commands

https://wh1te909.github.io/tacticalrmm/troubleshooting/#testing-network-connectivity-between-agent-and-server

[iarellano24]

Ok, i try.
only port 4222 throws me an error.

server:

[dinger1986]

Ok and if you ping that dns address do you get a reply?

[wh1te909]

please also paste the output of this command:

sudo systemctl status nats.service

[iarellano24]

Ok and if you ping that dns address do you get a reply?
Ping works.

[iarellano24]

sudo systemctl status nats.service

[dinger1986]

Have you opened port 4222?

[dinger1986]

Are you using custom ssl?

[iarellano24]

Have you opened port 4222?

Yest. Its open.

Are you using custom ssl?

Nop, it was a clean install. but after installation, all links show an ssl error anyway.

[dinger1986]

Ok so it's not working then.

Did you verify the TXT record? It looks like it failed.

[iarellano24]

Ok so it's not working then.

Did you verify the TXT record? It looks like it failed.

Yes. We add the txt record and it works.

Thanks a @wh1te909 in this thread, we know that the nats.service is stopped, so we understand that the problem may be there. We already restarted the nats.service but the problem persists. So what can we do?

We try solve this with docs, but when we try get output using this line

nats-server -DVV -c /rmm/api/tacticalrmm/nats-rmm.conf

we have this result:

[wh1te909]

rms.above.cl is that your subdomain or root domain?

[dinger1986]

Nats doesn't work without a genuine SSL certificate and yours doesn't appear to have installed properly.

[dinger1986]

If you click on the ssl error and show the cert details that would be helpful

[silversword411]

Looks like you're using cloudflare, you know you can't proxy nats right?

https://wh1te909.github.io/tacticalrmm/troubleshooting/#using-cloudflare-dns

[dinger1986]

Looks like you're using cloudflare, you know you can't proxy nats right?

https://wh1te909.github.io/tacticalrmm/troubleshooting/#using-cloudflare-dns

But SSL isn't working anyway, maybe it's proxied so should be using cloudflare SSL

[silversword411]

From public looks ok. Must be something else going on in the network from their screenshots

[dinger1986]

The url is api.rms.above.cl for api

[iarellano24]

@silversword411 @dinger1986 @wh1te909
Ok, the ssl issue was fixed.
The error occurs because the "Nginx Full" ports were not enabled in the execution of the script, for this reason it was not possible to verify the SSL configuration, however, the nats.service problem continues.

@silversword411 the cloudflare configuration is the same as in the documentation.

[dinger1986]

So is your api record? api.rms.above.cl?

[silversword411]

The error occurs because the "Nginx Full" ports were not enabled in the execution of the script, for this reason it was not possible to verify the SSL configuration, however, the nats.service problem continues.

Sounds like you're running a proxy. You should discuss in the discord #unsupported channel
https://discord.gg/bHcCxEfCnV

[silversword411]

Looks like LE certs are in nginx, just not loaded in nats

update --force run to make sure certs are everywhere?

[dinger1986]

What's the folder under /etc/letsencrypt/live? I'm guessing it's not /etc/letsencrypt/live/rms.above.cl?

[silversword411]

Post if there are issues still, I think you may have found your problem