MeshCentral: Desktop connection to M1 MacBook not working
Description I’ve installed the MacOS Agent and restarted the device. The device does not show up on the web interface of the server until I run the agent setup again. Now if I want to connect to the desktop of the device I get the message from MacOS on the device that the agent needs permission to record the screen. I’ve set the permissions and for screen recording and the whole drive. Now if I want to connect I only see the desktop and the menu bar. But I don’t see the bar with the applications and can’t remote controll the device. Also tried uninstalling and reinstalling the agent. On a different device with MacOS 11.7.5 Big Sur everything works just fine.
To Reproduce Steps to reproduce the behavior:
- Install MacOS Agent on device
- Restart device
- You wont see the device on the admin web page
- Run the MacOS setup again
- Now you see the device on the web page
- Connect to the desktop of the device
- On the device you see the window which asks for permissions for screen recording
- Grant the permissions
- Try to connect again
- You only see the desktop and the menu bar but can’t remote control the device
Expected behavior I install the agent on my MacOS device and restart it. After the device booted up and I get to the log in screen, the device should be visible on the web page and I should be able to connect to the desktop of the device and remote control it.
Screenshots Permissions screen which says that you need to grant permissions for audio and screen recording:
Screen you get when you connect to the desktop of the MacOS device:
Server Software (please complete the following information):
- OS: Rocky Linux 9.1
- Virtualization: None
- Network: WAN, reverse proxy
- Version: 1.1.4
- Node: 16.18.1
Client Device (please complete the following information):
- Device: MacBook Air 2020 M1 processor
- OS: MacOS Ventura 13.3
- Network: WAN
- Browser: Firefox 111.0.1 and Safari 16.4
Remote Device (please complete the following information):
I don’t use a remote device.
- Device: [e.g. Laptop]
- OS: [e.g. Windows 10 21H2]
- Network: [e.g. Local to Meshcentral, Remote over WAN]
- Current Core Version (if known): [HINT: Go to a device then
console
Tab then typeinfo
]
Additional context Some Information in the config.jason has been change do to anonymizing my domain and other private Information. The config.jason file, the server and services in general are working perfectly fine with different windows devices and a MacOS Big Sur 11.7.5 iMac.
Your config.json file
{
"$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json",
"__comment1__": "This is a simple configuration file, all values and sections that start with underscore (_) are ignored. Edit a section and remove the _ in front of the name. Refer to the user's guide for details.",
"__comment2__": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.",
"settings": {
"MongoDb": "mongodb://127.00.1:27017/meshcentral",
"cert": "subdomain.domain.net",
"_WANonly": true,
"_LANonly": true,
"_sessionKey": "MyReallySecretPassword1",
"port": 443,
"aliasPort": 443,
"redirPort": 80,
"redirAliasPort": 80
},
"domains": {
"": {
"_title": "MyServer",
"agentFileInfo": {
"icon": "wireshark_icon.ico",
"filedescription": "XXX",
"_fileversion": "2.0.0.1",
"internalname": "XXX",
"legalcopyright": "XXX",
"originalfilename": "XXX",
"productname": "MC_Agent",
"productversion": "v2.0.0.1"
},
"_agentCustomization": {
"_displayname": "Firma",
"_description": "Test",
"_companyName": "Firma",
"_serviceName": "Firmenagent",
"_fileName": "companyagent"
},
"_title2": "Servername",
"_minify": true,
"_newAccounts": true,
"_userNameIsEmail": true
}
},
"_letsencrypt": {
"__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.",
"email": "myemail@mydomain.com",
"names": "myserver.mydomain.com",
"production": false
}
}
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 1
- Comments: 18 (1 by maintainers)
As promised :
Install MeshCentral Client on ARM based OSX Sonoma :
The video : https://youtu.be/A71gioGHLWo
The steps :
Download the “Apple OSX Universal” client.
Open the terminal of your target machine’s and type :
chmod +x "path to meshagent"
And then sudo your
sudo "path to meshagent"
You should get a warning pop up saying “meshagent” cannot be openned because the developer can not be identified :
Go in Security Settings and click on “Allow anyway” :
Run again :
sudo "path to meshagent"
Then :
sudo "path to meshagent" -install
sudo "path to meshagent" -update
Edit the file mesgagent.plist in the folder /Library/LaunchAgents :
Try to access the desktop of your target from meshcentral. You’ll first be facing an empty desktop. On your target, you’ll see a pop up saying “meshagent” would like to record this computer’s screen and audio.
Open system settings and allow it. Then disconnect from your target.
Open system settings and allow it as well.
Reboot your target. MeshAgent should start, and your target should be fully accessible. You can hide the notifications related to the agent in Notification’s settings.
@theoroborus yes the bug is basically
launchdaemons
andlaunchagents
CANNOT have the same name in newer OSX versions, so the fix is to simple change the Label of yourmeshagent.plist
inLaunchAgents
tomeshagent-launchagent
and then restart your mac!hey gang, just looking at all the mac issues now as somebody kindly donated an M1 to fix bugs! has anybody found a way to actually get the remote control working on M1 12.7.2 ? ive tried the mpkg and the binarys and they just dont wanna work? if i can find a way to get it working i can look into why it needs to be done that way
When downloading the agent, did you use the “Apple macOS” agent or the “Linux/BSD/macOS installation program”? It works if you choose the later for “Apple OSX Universal”. If you customized your agent, you need to change the file name back to “meshagent”. Make it executable and run the installer.
Now your Mac should show up in your meshcentral server.
Same exact issue - Ventura endpoints. Linux server. Symptoms and observations match exactly.