Stuck at Mesh Central not ready yet

[Aghiad90]

Server Info (please complete the following information):

OS: Ubuntu 20.04
Browser: Chrome
RMM Version (as shown in top left of web UI): Fresh install (Latest Version)

Installation Method:

Standard

Describe the bug
Fresh install stuck at Mesh Central not ready yet

Screenshots

Additional context
I searched and most of case they said not enough ram . my server has 16gb of ram and 500gb of storage

Any idea what i could try ?

[dinger1986]

Can you open another connection to the machine and run htop and check usage?

[Aghiad90]

@wh1te909 @silversword411
i still could not open the ssh as it's little bit complicated based on our network setup.
but i doubled the RAM to be 32gb and this is the real time monitor and the usage looks normal

i do not think this is a resources issue ? any idea about what i can do
Thanks

[dinger1986]

Doesn't really help, it doesn't show what processes are running etc.

You will need ssh to get into it or another way.

Mesh central could be installed from their website and that would give you another way in

[Aghiad90]

@dinger1986 Alright i will work on ssh and see how it goes. in meantime could you please send me the instruction link to install the Mesh central ?

[silversword411]

There's no instructions for the mesh install that's part of TRMM...just read the install.sh and replicate commands.

Default mesh install which is not TRMM managed is here: https://ylianst.github.io/MeshCentral/install/

[dinger1986]

You can use the public mesh server to get temporary access (working round your lack of ssh) here https://meshcentral.com/login

Setup an account and install on your trmm server.

This is not supported by us and only a suggestion how to use a different way to access your server.

[silversword411]

Since things are already borked, starting a new vm and just running install.sh again is probably easiest.

Log it, so if it goes sideways we'll have a better understanding of why: https://docs.tacticalrmm.com/troubleshooting/#problems-after-new-server-install

[Aghiad90]

Hello , @dinger1986 @silversword411 .
i did create new VM , fresh ubuntu 20.0.4 , fresh install and it did same i got access to ssh now please check the following screenshot

[silversword411]

Do you have weird network equipment/filters/IDS that is between your VM and internet that could be causing issues? That looked like a proxymox VM, so local hardware? What is doing NAT for you? Are there proxies? You should join Discord, and chat, we'll probably be asking for a logged install and/or access to your system to check. https://docs.tacticalrmm.com/troubleshooting/#problems-after-new-server-install (lots of security info in the log so don't share without checking)

Since others aren't reporting this issue, I'm pretty sure it's something specific to your environment that's non-standard

[Aghiad90]

@silversword411 i will join discord.
we have the proxmox vm behind a mikrotik router not sure if that will help but we did review the logs and monitor it we could not see anything wrong

Regards ,

[Aghiad90]

@silversword411 New update , i did create another VM with debian 11 and it worked no problem.
not sure what was the issue with ubuntu !

[rpchamberland]

@silversword411

I am experiencing the same issue with trying to install version 0.14.5 on Debian 11.

Installed Debian (11.4.0 amd64) in non-graphical mode.
2 virtual processors and 8 GB or RAM for test environment.
Installed SSH Server (can be done as part of the install or afterwards).
update apt
Snapshot the system on a Hyper-V server.

https://docs.tacticalrmm.com/install_server/
Created tactical user per installation instructions.
Logged in via SSH as the tactical user and continued the installation process per the instructions above.

Sticks at "Mesh Central not ready yet,,,"
Ran htop and there are no signs of resource issues.
Let it sit for 24 hours, no change.

Started fresh with new os and the process above and same results.
Let sit overnight, no change.

Performed again with logging enabled (bash -x install.sh 2>&1 | tee install.log) actually worked, but I didn't get an MFA screen capture and had to manually enter the key.

But that did finally work and I am able to use the system as far as I can tell. Other than using the install.sh with log collection enabled, I did everything else the same.

Posted to help with anyone else experiencing the issues and perhaps the dev team to be aware of potential issues.

[lifeoflejf]

I had the same issue - it turns out that I was using an old iso of ubuntu, and npm for some reason didn't install. Once I used a new iso (of the same ubuntu version?) it worked.

[CTNBurt]

I have the same problem, whether it is UBUNTU or DEBIAN, and then I opened the port 1024 and passed it smoothly, I hope it can help you.

[dinger1986]

1024 shouldn't need opened