@mesmariusz please read #4795, all development has stopped for the moment
Try watching some of his YouTube videos which might help you
@.***
The software generates its own self signed SSL incase you don't have one, and generates certificates which are used for encryption of AMT and other stuff so they shouldn't be deleted on every run!?
Also try reading the news docs which might also help
https://ylianst.github.io/MeshCentral/
On Thu, 26 Jan 2023, 20:22 CompuMatter, @.***> wrote:
Describe the bug I have a wildcard cert on the domain I am using for Meshcentral's login page. However, when I start Meshcentral via node, I see it is generating its own certs. It seems it should be using my cert instead of generating something new.
Though the video does not show this, I have tried inserting the cert in this area:
"settings": { "cert": "desktops.smvirtual.biz",
However Meshcentral still generates a cert on its own.
To Reproduce Steps to reproduce the behavior: Edit the config.json file Insert
"settings": { "cert": "desktops.smvirtual.biz",
Cert is created without regard to my inserting it in the config.json file
Expected behavior I expected it would not need to create its own certs.
Screenshots I have created a video to make the problem more clear:
- https://www.youtube.com/watch?v=XCbnDZjdokw
Server Software (please complete the following information):
- OS: Ubuntu
- Virtualization: None
- Network: WAN and LAN, reverse proxy through NGINX
- Version: latest installed on 202.01.26
- Node: v14.21.2
Additional context Add any other context about the problem here.
Your config.json file
{ "settings": { "Cert": "desktops.smvirtual.biz", "Port": 444, "AliasPort": 443, "RedirPort": 80, "AgentPong": 300, "TlsOffload": "127.0.0.1" }, }
— Reply to this email directly, view it on GitHub https://github.com/Ylianst/MeshCentral/issues/4940, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAF23AQLYSEOR6QQBOK3ZN3WULMHXANCNFSM6AAAAAAUH5SKLQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
You have put the config.json
in the wrong location
It shouldn't be inside the node_modules
It should be inside meshcentral-data
https://ylianst.github.io/MeshCentral/install/install2/
@tahaghafuri can you explain do you close this issue?
beat me too it, im struggling at mo to find time to write the plugin but its on my to-do-list
Try this
Disabling backchannel with #backchannel=0 worked, Though I don't know how or why it works. Maybe it should be disabled by default? More documentation on this would be very helpful.
https://github.com/AlexxIT/WebRTC/issues/386#issuecomment-1399167086 - Already been suggested But maybe @AlexxIT can explain the backchanel option
So, should I stop the Mesh Central service from the service? and run it with CMD Which method is stable? Central mesh service or running with CMD?
Well the service starts in the background when you start your server up Where as Cmd must be run manually everytime u start your server up
Service is best but no logs in a black window for example
Try this
https://github.com/AlexxIT/WebRTC/issues/386#issuecomment-1399156195
I just have for my customwebrtc an entity defined like, camera.xxx. How can I add there the backchannel option ? I don't use the rtsp feed
I'm the same, I use the dahua hacs integration for motion on our dvr unit, and I use the camera. Entity how can we add the backchannel as the webrtc nolonger works now?
That's because u are running 2 instances! You must run either the meshcentral service OR meshcentral via cmd line You can't run both at the same time
tcpview
So it says node.exe is running and using the port So make sure meshcentral isn't running as a service, Restart server, Check if its still running node.exe, If so then you should be able to double click the line and it should show u the process command and what it is, then maybe kill it from task manager
It believes the port is already in use so it moves up one port number and uses that if its available
Also Intel amt is saying the same thing, it's port isn't available as it's in use
Use tcpview from sysinternals and see what's using port 443
Here you go. I did not changed anything from the default.
{ "settings": { "cert": "MY PUBLIC FQDN", "wanonly": true, "_minify": true } }
that seems very short? the sample one shows different https://github.com/Ylianst/MeshCentral/blob/master/sample-config.json
please can you share your config.json
(hide secret stuff obvs)
That's a third party website, so I cannot confirm if docs are correct
This is official docs from @Ylianst and the community
https://ylianst.github.io/MeshCentral/install/install2/#configuring-for-mongodb
I'll have a play later and see if I can find what's wrong
The error is actually happening after the first line
(/home/blaine07/node_modules/mongodb/lib/operations/indexes.js:92:46)
So the error is actually nothing to do with meshcentral but the mongodb module!
What is your config.json?
Yes send a new invite link with the agent and tell them to install the agent which runs as a service in the background which should also help your issue
@sysopdm no matter what i try now, i cant get it to crash again now @Frostfach @mbsouth what is your server setup? what roles are installed? do any of you do something in particular while in your session and then log out for it to crash? e.g open certain files, change settings, updates?
@sysopdm OOOOO i dont know what i did but i got it to crash!?
@sysopdm ive just tried it 'server 2016' on proxmox, no issues here? fresh install with all updates, logged in using the vnc console on proxmox, then connected with meshcentral, signed out and no reboots? even tried logging in from meshcentral then signing out, its just not crashing the server or the agent? what services do you have installed on the server 2016?
When use you RDP it works flawlessly every time, no issues. The problem is when you go to Desktop -> Connect
oh you mean a phyiscal logoff not a virtual one! hmmm will try later with our AD and see what happens, dont want to upset the site in the middle of the day haha
im not seeing this issue at all? run the agent on a server 2016 active directory and i login/logout over RDP every day? have you tried updating to the latest agent release from december 2022? you also dont say what version of meshcentral you are running, please can you try updating to the latest version of it also
have you installed the agent on the server 2019 (background service) or have you run the assistant (asked user to run the exe)?
the assistant runs as the user thats currently logged in, so when you run an exe in server 2019 or server 2016, it will load up the Windows UAC panel to continue, and sadly the UAC isnt visible because its run as admin, so its just times out and returns back to the desktop after 1-2mins
we encounted this with a recent Server 2016 Active directory server, every time we tried to run an exe or anything i would get a prompt on the server to carry on so clicked on it, but with meshcentral its not possible if you run the assistant unless you have the agent installed
to fix this issue you need to enable the admin approval mode then restart the remote device https://www.tenable.com/audits/items/DISA_STIG_MS_Windows_Vista_V6R41_STIG.audit:ce7133f93809be1c8c96636b662fabf7
the docs for meshcentral are here - https://ylianst.github.io/MeshCentral/ the page in question you need is - https://ylianst.github.io/MeshCentral/install/install2/ you can edit that page here - https://github.com/Ylianst/MeshCentral/blob/master/docs/docs/install/install2.md edit the md, test it, then submit a PR and im sure @Ylianst will accept the docs request, you can add a section about backups at the bottom of the page maybe?
you have "WANonly": true
this should be "WANonly": false
give that a shot
@si458 do you need help?
Sorry not had time to look at this, will have a look when I get chance for u
downloadedinstaller.exe -fullinstall
from commandline/pstools/gpo/powershell (would need ./) etc
this is the correct way to do it, however i have noticed the is always a slip second/two of a black window which just shows the installs/registers/starts service, i havent found a way to hide this yet