Ylianst / MeshAgent

MeshAgent used along with MeshCentral to remotely manage computers. Many variations of the background management agent are included as binaries in the MeshCentral project.
https://meshcentral.com
231 stars 90 forks source link

desktop tab only available after remote user logs in #260

Open luciandf opened 3 weeks ago

luciandf commented 3 weeks ago

Hello all,

Not sure if this is the intended usage or not but I can see the desktop tab in the remote client, only after remote user login. Is it possible to enable the desktop tab before a user logs in so that a remote user can perform the login and work remotely?

si458 commented 3 weeks ago

What os/version is the remote device? What meshcentral are u running? As the remote tab should always be visible if windows and mac If its linux it will only display if it detects X11 and u aren't using wayland

luciandf commented 3 weeks ago

the remote client is rocky linux 9.4 and I am running plasma X11 (I have selected that at login screen). Not sure what else to set so that wayland is not involved.

The mesh central server is run under docker from here:

https://github.com/Typhonragewind/meshcentral-docker

si458 commented 3 weeks ago

yes changing the selector on the login screen only changes the session when you login not the actually login screen itself

you need to fully disable the wayland https://github.com/Ylianst/MeshAgent?tab=readme-ov-file#special-note-about-kvm-support-on-linux or if you dont want to fully disable wayland, you need to change the login screen to use X11 by default

also try the offical docker image ghcr.io/ylianst/meshcentral:latest

luciandf commented 3 weeks ago

I will try the official docker image too. At the moment my docker compose file is:

version: '3'
services:
    mongodb:
        container_name: meshcentral_db
        restart: always
        image: mongo:latest
        expose:
            - 27017
        volumes:
            - '/home/meshcentral/database:/data/db'
    meshcentral:
        restart: always
        container_name: meshcentral
        depends_on:
            - 'mongodb'
        image: typhonragewind/meshcentral:mongodb-latest
        ports:
            - 8086:443 #MeshCentral will moan and try everything not to use port 80, but you can also use it if you so desire, just change the config.json according to your needs
        environment:
            - PUID=1007
            - PGID=1007
            - HOSTNAME=https://remote.lucianfilip.com     #your hostname
            - REVERSE_PROXY=192.168.1.252     #set to your reverse proxy IP if you want to put meshcentral behind a reverse proxy
            - REVERSE_PROXY_TLS_PORT=443
            - IFRAME=false #set to true if you wish to enable iframe support
            - ALLOW_NEW_ACCOUNTS=false    #set to false if you want disable self-service creation of new accounts besides the first (admin)
            - WEBRTC=true  #set to true to enable WebRTC - per documentation it is not officially released with meshcentral, but is solid enough to work with. Use with caution
            - NODE_ENV=production
        volumes:
            - '/home/meshcentral/.meshcentral/data:/opt/meshcentral/meshcentral-data'
            - '/home/meshcentral/.meshcentral/user_files:/opt/meshcentral/meshcentral-files'
            - '/home/meshcentral/.meshcentral/backups:/opt/meshcentral/meshcentral-backups'

Will it work if I just change to the official image and redeploy?

I also have another question regarding the WebVNC connection. I have installed tiger vnc server on the client machine and set it up. But I cannot get a connection when I try webvnc. is there a guide on how to setup webvnc with meshcentral?

si458 commented 3 weeks ago

yes it should work as a drop in replacement, in theory our image is a replicate of theres, just a few extra changes, plus we can fix bugs/etc when people discover things 👍

as for VNC it should be enabled out the box, u use the web-vnc and make sure the vnc is running on 0.0.0.0 or 127.0.0.1 also ideally use just passwords not user/pass methods, but it does work as i use this method with my mac

luciandf commented 3 weeks ago

u use the web-vnc and make sure the vnc is running on 0.0.0.0 or 127.0.0.1

where do I make sure vnc is running there? on the client machine?

si458 commented 3 weeks ago

where do I make sure vnc is running there? on the client machine?

yes on your client machine

luciandf commented 3 weeks ago

i can't seem to get it to work. I can see the desktop from the desktop tab but I can't get a connection win webvnc.